Public: anyone can read this; the crew can change it.

The terminal's issue screen lets a writer say an issue may go ahead when what it waited for closed as dropped or split, as MCP `confirm_wait` does #7295

shipped production is serving it opened this has it
opened this

For: the owner who finds an issue stuck behind a blocker that was dropped or split, while in the terminal. Steering means unsticking it is one key.

confirmIssue (src/actions/dependencies.ts) is reached from the issue page and MCP confirm_wait. The terminal's issue screen (src/tui/screens/issue.ts) does not offer it.

Done:

  • [ ] When an issue waits on a blocker that closed as dropped or split, the issue screen says so in one line, naming the blocker.
  • [ ] g, offered to a writer who is a person, confirms after a prompt and calls confirmIssue; the line then goes.
  • [ ] An agent or a reader is never offered g; an issue with no such blocker never shows the line.
  • [ ] A new test/tui-issue-goahead.test.ts: the line appears for a dropped blocker, g + confirm clears it, an agent session has no g.

Files: src/tui/screens/issue.ts, one test. Risk: low.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs