- mark built-in agents that resolve to the current binary as "available" and remove install hints in Agents UI
- thread self-resolved status through overview rendering for consistent labeling in overlay and bottom pane
- add regression test for available status copy
Refs #429
- keep failed overlong coordinator outputs in the conversation, suppress compaction notices, and surface a retry action in the Auto Drive card so follow-up requests retain the error context
- add explicit Action app event, pass compaction notice intent through to the TUI, and raise the coordinator worker stack to 1 MiB with an opt-in backtrace hook for debugging validation overflows
- simplify bottom_spacer_hysteresis_requests_followup_frame to a known viewport pair to avoid FD exhaustion during repeated harness setup
Fixes#432Fixes#430Fixes#433Fixes#429
Replace the retry Thinking event text with a neutral message so the Auto Drive card shows the retry without exposing prompt-length guidance to the user. Build fast remains green.
fixes#432
Add assistant retry note into the conversation so the Auto Drive card shows context while retrying overlong prompt_sent_to_cli errors. Developer guidance string remains in the conversation; raw model output stays in assistant message.
fixes#432
Resolve command check for code/codex/cloud so they are treated as built-in when using the default CLI, even if coder is absent or overridden; prevents skipping agents and avoids running PATH coder when current exe should be used.
fixes#429
Assistant message now keeps the raw model output; developer note carries the fixed guidance string so the coordinator sees both the failure context and the explicit <=600 notice. Build fast remains green.
fixes#432
- Always use the running binary for built-in code/codex/cloud agents unless the user set a custom command; keep model args when self-spawning so labels stay accurate.
- Add tests for the new current-exe preference and preserve custom overrides.
fixes#429
Replace the retry assistant insert with a fixed error string so the CLI clearly sees the overlong prompt error without echoing the long prompt. Persist the message in the conversation and simplify developer notes.
fixes#432
Surface the invalid assistant JSON as an assistant message before retrying recoverable validation errors (e.g., overlong prompt_sent_to_cli) so the coordinator can see what failed. Retains existing retry guidance path.
Refs #432
James Peter