Daemon still runs after CTRL+C
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23.8k
- Forks
- 2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 13
Description
Hi,
really cool tool!
I launched it, connected to my mobile, used it a bit, then I wanted to "close it", so I ctrl+c multiple time in my laptop terminal until the happy command exited, then I continued looking at the app, and tried to create a new session, and to my surprise, it worked (it launched a claude assistant in the previous folder where I had started happy)
this seems a bit weird... when I launch happy in "sync mode" I'm expecting that after ctrl+c, all the processes are closed (for security reasons) and that there's no daemon staying in the background
is that expected? Is there a way to have a full "synchronous" mode without a background daemon?
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 reproducing the happy sync-mode workflow: launch it, connect the mobile app, press CTRL+C, and check whether a session can still be created. Trace the daemon and child-process shutdown path, then verify that CTRL+C closes all related processes and prevents new sessions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100