[P0] Executor batches everything into one silent "mega-turn" → long dead-air #34

New issue

Open

opened 2026-05-23 21:52:21 +00:00 by thabeta · 0 comments

thabeta commented

2026-05-23 21:52:21 +00:00

Owner

Problem
The executor generates its whole first turn (approach text + many file_write tool calls with full file bodies) before any tool executes. Measured: job started 21:29:03, first file_write executed at 21:30:21 — 78s of dead air after the approach line. The operator sees "Working 1m+" with no actions.

Evidence

audit_log for the job's session: first tool row 78s after started_at.
Prompt: prompt_builder.rs Execute mode ("write all files in one go").

Proposed fix
Instruct the executor to narrate one short line before each step and act in small increments (a file or two, then continue) instead of one silent batch — so talking + actions are continuous.

Related: #29.

Filed from a comparative audit of Hero Shrimp vs Qwen-Code / kimi-cli / picoclaw (2026-05-23). Severity in title: P0=correctness/trust, P1=reliability/UX, P2=cleanup.

**Problem** The executor generates its whole first turn (approach text + many `file_write` tool calls with full file bodies) before any tool executes. Measured: job started `21:29:03`, first `file_write` executed at `21:30:21` — **78s of dead air** after the approach line. The operator sees "Working 1m+" with no actions. **Evidence** - audit_log for the job's session: first tool row 78s after `started_at`. - Prompt: `prompt_builder.rs` Execute mode ("write all files in one go"). **Proposed fix** Instruct the executor to narrate one short line *before each step* and act in small increments (a file or two, then continue) instead of one silent batch — so talking + actions are continuous. Related: #29. --- _Filed from a comparative audit of Hero Shrimp vs Qwen-Code / kimi-cli / picoclaw (2026-05-23). Severity in title: P0=correctness/trust, P1=reliability/UX, P2=cleanup._