feat(agent): preamble before multi-step tasks for a readable chat - #317
Conversation
The prompt told the model "Use tools to act, not to narrate", which also suppressed the brief upfront "here's my approach" the user relies on to follow what the CLI is doing — so Zero jumped silently into tool calls. Keep the per-call anti-spam, but lead a multi-step task with a one- or two-sentence plain-language preamble. Prompt-only change; the TUI already commits streamed pre-tool prose as an assistant row, so no render change is needed.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe system prompt’s tool-use guidance now asks for a brief plain-language preamble before multi-step work, then directs the agent to use tools without narrating each call and to explain outcomes as it proceeds. ChangesTool-use prompt update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Zero automated PR reviewVerdict: No blockers found Blockers
Validation
ScopeHead: This deterministic review checks validation status and basic diff hygiene. A human reviewer still owns product judgment and design quality. |
Reconcile the narration guidance: keep #317's plain-language preamble lead AND this branch's per-significant-step running narration (the story flow), with both sides' 'don't narrate trivial calls / skip for one-step tasks'.
Problem
Zero jumps silently into tool calls — no upfront explanation of what it's about to do, so the chat reads like opaque machine output. A reference agent on the same task preambles ("I'll build this with a warm editorial direction… let me write the three files"), which makes the work easy to follow.
Root cause
internal/agent/system_prompt.mdtold the model: "Use tools to act, not to narrate. Do not announce each call; just do the work and explain the outcome." That correctly stops per-call spam, but it also suppressed the useful upfront approach statement. (The TUI already commits streamed pre-tool prose as an assistant row, so the render path was ready — the model just produced none.)Fix
One-file prompt change: lead a multi-step task with a 1-2 sentence plain-language preamble, while keeping the per-call anti-spam:
Notes
./internal/agent/...tests green. Behavior is a manual/eval check (not deterministically unit-testable); easiest of the chat-clarity series to tune or revert.Part 2 of 3 in the chat-clarity series (with #316). The third — write/edit diff preview — is a separate PR.
Summary by CodeRabbit