CommandCodeAI / CommandCodeAI/command-code
Can't type a new prompt after 2-3 prompts
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
I'm noticing that in this new release - after 2-3 prompts, I'm not able to type my prompt anymore and the only way I can deal with it - close the tab of terminal and start a new session.
I'm running cmd 0.33.1 on Mac OS X 26.2
Expected Behavior
N/A
Actual Behavior
N/A
Steps to reproduce the issue
Seems like a memory leak or something - it just fails to respond..
Command Code Version
0.33.1
Operating System
macOS
Terminal/IDE
ghostty
Shell
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
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 failure in Command Code 0.33.1 on macOS 26.2 using Ghostty, sending two or three prompts and checking when terminal input stops responding. Done means the interactive prompt remains usable across repeated prompts, with the failure narrowed beyond the current memory-leak suspicion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100