Show more details about executed bash commands
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Right now, when jcode (v0.77.1) runs a bash command, the output line is very minimal. It shows only something like:
✓ bash · Check git status · 491 tok
This makes it hard to understand what exactly was executed, especially when debugging or reviewing the agent's actions. We see a brief description, but not the actual command, its working directory, exit code, execution time, or output.
What I'd like to see
- The full command that was run (not just a summary description)
- The working directory where it was executed
- The exit code (e.g., [exit 0] or [exit 1])
- The execution time (e.g., took 120ms)
- The stdout/stderr output (truncated if too long, or shown in a collapsible section)
Example of improved output
Instead of just:
✓ bash · Check git status · 491 tok
we would see something like:
✓ bash [exit 0] · /home/user/project · git status · 491 tok · 120ms
Output: On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
Alternative
If inline clutter is a concern, a --verbose flag or a settings option could be added to enable this extra information. But having it on by default would be more user-friendly for most use cases.
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
No file or test is named. Start by tracing where jcode executes bash commands and renders lines like “✓ bash · Check git status”; determine how command, working directory, status, timing, and output are available. Done means the display provides the requested details, with truncation or a verbose/settings option if inline output is too cluttered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100