MoonshotAI / MoonshotAI/kimi-code
kimi web: Bad DX and Unix CLI convention violation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
kimi web MUST stay in the foreground.
Daemonizing should require an explicit
--daemon/--detach/-d flag or some other flag, not be the default.
Modern Unix CLI convention is that the user (or a service manager), not the command itself, decides when a process runs in the background.
This is so bad accually need to be fixed ASAP before v1 and its so annoying.
maybe you're vibe coding the kimi-code but at least respect the unix philosophy!!
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
Locate the kimi web CLI entry point and reproduce its current default process behavior. Trace how the existing daemonization is selected, then verify that the command remains in the foreground by default and that backgrounding requires an explicit documented flag such as --daemon, --detach, or -d.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100