temporalio / temporalio/temporal
Dev Mode Improvements (Insights from AWS Hackathon)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
I do not like restarting 3 terminals in dev mode. Either there should be an auto workflow/worker restart feature whenever a change is made kind of like npm or uv in python. Also when the workflow and workers are killed and restarted, if they are not done in order, they do not connect sometimes.
Solution Suggestion: kill switch in dev mode UI, and automatic restart of processes specific to dev mode.
Describe alternatives you've considered
Right now I just kill all terminals. Sometimes when they don't connect I have to restart all.
Additional context
Issues were from the hackathon repo https://github.com/temporal-community/temporal-ai-agent/tree/main
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked temporal-ai-agent hackathon repository and locating the dev-mode UI and process startup paths. Define the restart and kill-switch behavior, including the required workflow and worker ordering; done means dev mode can restart processes automatically and reconnect reliably without manually killing three terminals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100