Skip to content

feat(dispatch): the Dispatch section, a list with the selected item beside it - #56

Merged
borght-dev merged 1 commit into
dispatch/01-enginefrom
dispatch/02-section
Oct 12, 2026
Merged

borght-dev merged 1 commit into
dispatch/01-enginefrom
dispatch/02-section

Conversation

@borght-dev

@borght-dev borght-dev commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

Part 3 of 8 of Dispatch in BorgDock. The stack, bottom up: #54 → #55 → #56 → #57 → #58 → #59 → #60 → #61.

A new section, second in the rail (keys 1 to 5), that shows the work assigned to you sorted by what it needs.

What changed

  • The list groups items by bay, waiting on you first. Each row says why it sits there and shows the slot its agent runs in.
  • The detail beside it shows the ADO state, the slot, the pull request with live checks, the agent's question or last message, the next action and the item's place in its workflow.
  • You can answer a question, approve a plan, settle a thread, open the thread in T3, move the ADO state or hide a suggestion without leaving the section. Nothing changes in ADO unless you press a button.
  • The slot strip shows every T3 project per host: free, yours, busy.
  • Keys: J and K move, Enter opens the work item, A takes the first action, M moves the state, O opens the thread in T3.
  • When T3 is not paired, or its token expired, a notice offers to pair in place.
  • Settings, Agents has the slot pattern.
  • New T3 commands: t3_respond, t3_send_message, t3_settle.

Approve plan sends a go-ahead message, with Open in T3 beside it.

How I checked it

Unit tests, and screenshots of the stories RailDispatch, RailDispatchPlan and RailDispatchOutOfSync in both themes.

🤖 Generated with Claude Code

…eside it

A new section, second in the rail (keys 1 to 5), that shows the work
assigned to you sorted by what it needs.

- The list groups items by bay, waiting on you first. Each row says why it
  sits there and shows the slot its agent runs in.
- The detail beside it shows the ADO state, the slot, the pull request
  with live checks, the agent's question or last message, the next action
  and the item's place in its workflow.
- Answer a question, approve a plan, settle a thread, open the thread in
  T3, move the ADO state or hide a suggestion without leaving the section.
  Nothing changes in ADO unless a button is pressed.
- The slot strip shows every T3 project per host: free, yours, busy.
- J and K move, Enter opens the work item, A takes the first action, M
  moves the state, O opens the thread in T3.
- T3 not paired, or its token expired: a notice offers to pair in place.
- Settings, Agents: a slot pattern limits which T3 projects are slots.
- New T3 commands: t3_respond, t3_send_message, t3_settle.

Starting an agent comes with the launch sheet in the next change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant