Why
Agent sessions usually end in a branch and a pull request. The question after "is the agent done" is "is the PR green", and today that means leaving flue for github.com. A small status chip on the session row closes that loop without turning flue into a tracker.
Rough scope
- Session metadata gains: current branch, associated PR if one exists, PR state, checks rollup (green, red, pending).
- Source is the
gh CLI already authenticated on that machine, queried by the daemon and shipped alongside the session info it already sends. No OAuth app, no tokens stored by flue.
- Chip on the session row and in the session header, links out to the PR.
Deliberately thin
flue is the transport and the view, not a project tracker. No issue lists, no PR review UI, no merge button in v1. For the same reason a Linear integration was considered and skipped: agents already reach Linear through MCP, and flue has nothing to add there.
Priority
Backlog, behind the notification arc and the composer.
Why
Agent sessions usually end in a branch and a pull request. The question after "is the agent done" is "is the PR green", and today that means leaving flue for github.com. A small status chip on the session row closes that loop without turning flue into a tracker.
Rough scope
ghCLI already authenticated on that machine, queried by the daemon and shipped alongside the session info it already sends. No OAuth app, no tokens stored by flue.Deliberately thin
flue is the transport and the view, not a project tracker. No issue lists, no PR review UI, no merge button in v1. For the same reason a Linear integration was considered and skipped: agents already reach Linear through MCP, and flue has nothing to add there.
Priority
Backlog, behind the notification arc and the composer.