`jcode run` prints streamed reasoning one chunk per line

Open Beginner friendly
#2,134 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@theammir is already working on this.

Since Nov 11, 2026.

  • #2135 by @theammir — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

Start in crates/jcode-app-core/src/agent/turn_loops.rs at run_turn and follow the StreamEvent::ThinkingDelta handling. Compare it with the text delta output path, which the issue says already wraps correctly. Update the reasoning output so one block uses a single prefix and continuous text; done when streamed reasoning wraps at the terminal width in plain jcode run and the line-based REPL.

Written by the indexing model from the issue text.

Description

autonomous: likely bug type: bug

Curious - what was the idea behind bare jcode run anyway? It could maybe use some love to become a more parseable plain-text alternative to running a full TUI, but I'm not sure where to start - right now it looks more like a debug output of a run, rather than something an output of which can be easily read or shared.

What happens

In plain jcode run output (and the line-based REPL), streamed reasoning is
printed one provider delta per line, each with its own 💭 prefix. Deltas are
usually only a few words, so reasoning shows up as a narrow column no matter
how wide the terminal is. Same behavior inside and outside tmux.

💭 I'm starting the
💭  investigation now
💭 , ke
💭 eping to read-only work

Expected

Reasoning for one block is printed as continuous text after a single prefix,
and the terminal wraps it at its real width.

Cause

run_turn in crates/jcode-app-core/src/agent/turn_loops.rs handles
StreamEvent::ThinkingDelta with terminal_println!("💭 {}", thinking_text),
so every delta gets a prefix and a newline. Text deltas already use
terminal_print! and wrap correctly.

Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
21h 27m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 1jehuang/jcode

All issues in 1jehuang/jcode

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.