fix-chat-with

Fix: 'Chat with Agent' picker shows non-chat tasks (e.g. abandoned fix-new-chat-3)

Metadata

Statusdone
Assignedagent-1269
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Modelclaude:sonnet
Created2026-04-30T16:18:25.920149448+00:00
Started2026-04-30T16:23:16.773801125+00:00
Completed2026-04-30T16:56:06.306269970+00:00
Tagsfix,tui,ux,chat, eval-scheduled
Eval score0.76
└ blocking impact0.80
└ completeness0.75
└ coordination overhead0.80
└ correctness0.75
└ downstream usability0.75
└ efficiency0.75
└ style adherence0.75

Description

Description

The TUI's 'Chat with Agent' picker pane shows entries that aren't chat tasks. User screenshot 2026-04-30 shows fix-new-chat-3 (abandoned · §1.2k) 1h listed in the picker alongside .chat-31 (open · ⌁50) — fix-new-chat-3 is a regular fix task that was abandoned, not a chat agent.

User quote: 'this is not quite right...'

Likely cause

The picker is filtering by something too permissive — probably 'show all tasks' or 'show recent tasks' rather than 'show tasks tagged chat-loop' or 'show tasks with id matching .chat-*'.

Fix

Filter the picker to chat-task-id pattern (.chat-* prefix) AND/OR chat-loop tag. Exclude:

  • Regular tasks (fix-, audit-, design-, etc.)
  • Abandoned tasks
  • Done tasks (unless we explicitly want history — separate UX choice)

Confirm what the current criterion is in the picker code, then tighten it.

Validation

  • Failing test or repro: open the chat picker. Pre-fix: shows non-chat tasks. Post-fix: only .chat-* tasks appear.
  • Abandoned tasks no longer appear regardless of name pattern
  • Regular .chat-N tasks still appear correctly
  • cargo build + cargo test pass
  • cargo install --path . was run before claiming done

Depends on

Required by

Log