Jcode crashed back to terminal prompt during tool-heavy workflow session
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Summary
Jcode crashed/exited back to the terminal prompt during an active session.
Time
Approx: 2026-05-15T18:10 UTC
Environment
- OS: macOS arm64
- Jcode: v0.12.1 (f6ce4fd8)
- Working dir:
~/trading-bot
What was happening
I was running a tool-heavy coding session building a paper trading bot. Shortly before the crash, Jcode had been running shell/test/git operations and monitoring commands. It exited back to the terminal prompt unexpectedly.
Expected
Jcode should remain in the TUI/session, or show a recoverable error.
Actual
It dropped back to the terminal prompt.
Diagnostics
Diagnostic bundle generated locally:
/Users/awalker/jcode-crash-diagnostics-20260515T181134Z.tar.gz
I can provide the tarball if needed. It includes redacted recent logs/config/update metadata.
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 with the supplied crash diagnostics bundle and the Jcode TUI/session entry point, then try to reproduce the tool-heavy workflow involving shell, test, git, and monitoring commands on macOS arm64. Done means identifying the crash cause and ensuring the session stays active or reports a recoverable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100