Observed
In the running Pear app, an agent session shows corrupted terminal rendering: after a long
task completes (a status line like "Crunched for 2m 5s") and a follow-up question is asked
("give me the full path of the file"), the terminal pane shows garbled/overlapping text —
stale content from the prior turn (a markdown spec preview) interleaved with the new
prompt/response line, rather than a clean redraw.
CLI attribution is uncertain — operator first said codex, then said it may actually be
claude. Debug BOTH --cli=claude and --cli=codex in the term-fidelity matrix; don't assume
either is exonerated until you have byte-level evidence.
Context
Related prior work:
Ask
- Reproduce via
npm run test:term-fidelity -- --cli=claude AND --cli=codex with a
workload that mirrors: long-running task → completion → immediate follow-up question
referencing prior output.
- Root-cause per-CLI with the byte-level dump-pty discriminator before proposing a fix —
don't declare either CLI clean/dirty on impression alone.
- Fix whichever CLI(s) reproduce, and add regression case(s) to the term-fidelity matrix.
cc coordinator thread: #term-fidelity channel (agent-relay workspace)
Observed
In the running Pear app, an agent session shows corrupted terminal rendering: after a long
task completes (a status line like "Crunched for 2m 5s") and a follow-up question is asked
("give me the full path of the file"), the terminal pane shows garbled/overlapping text —
stale content from the prior turn (a markdown spec preview) interleaved with the new
prompt/response line, rather than a clean redraw.
CLI attribution is uncertain — operator first said codex, then said it may actually be
claude. Debug BOTH
--cli=claudeand--cli=codexin the term-fidelity matrix; don't assumeeither is exonerated until you have byte-level evidence.
Context
Related prior work:
claudeandcodexare supported CLIs intests/term-fidelity/harness.ts(
SUPPORTED_CLIS).workloads.tshas codex-specific handling (--no-alt-screen,asking-confirmation detection) that claude does not share — a likely source of a
codex-only divergence class, but claude is not yet ruled out for THIS symptom.
Ask
npm run test:term-fidelity -- --cli=claudeAND--cli=codexwith aworkload that mirrors: long-running task → completion → immediate follow-up question
referencing prior output.
don't declare either CLI clean/dirty on impression alone.
cc coordinator thread: #term-fidelity channel (agent-relay workspace)