Feature: opt-in full Bash command visibility in tool output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Problem
When Jcode runs Bash tools, the interactive display can show only a success/failure status or a shortened command summary. That makes it hard to audit what actually ran and to diagnose a failure without opening and manually searching the raw session transcript.
In the current code, the Bash summary truncates commands longer than 60 characters (crates/jcode-app-core/src/agent/tools.rs:107-114).
Proposal
Add an opt-in preference to show the complete Bash command in tool-call rows, with an expand/collapse affordance for long commands.
Acceptance criteria
- A persistent config option enables full Bash command display.
- Long commands can be expanded from the TUI without leaving the session.
- On failure, the complete command and exit status are readily visible or copyable.
- The default compact view remains available.
- Sensitive inline environment assignments and known token formats are redacted before display.
Why this matters
Exact command visibility is important for trust, auditability, and debugging. The transcript should be a fallback, not the only practical way to discover what was executed.
Environment
- Jcode v0.71.1 (
dd8755f7e) - Linux x86_64
- Interactive TUI
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 in crates/jcode-app-core/src/agent/tools.rs:107-114 to trace Bash summary generation, then follow the existing persistent configuration and TUI tool-call row patterns. Done means an opt-in full-command view with expansion, failure visibility, compact default behavior, and redaction of sensitive inline assignments and known token formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100