Inbox, Planboard, Review

The sidebar is the inbox. Threads that need you stay up top. Quiet runs fold into a Working shelf at the bottom, next to Snoozed and Settled. Footer icons are Threads, Planboard, Review, and More. The right-hand inspector is Environment, Agents, Memory, and Skills. It is not a second home for settings.

• Planboard shows one project's plan as its GitHub or GitLab issues in Todo / In progress / Done. Cards open the issue on its host, and Start task on a Todo card opens a thread on it, in worktree, orchestrator or plain mode.
• Review lists the open PRs per project with their checks, and jumps to the thread that opened one. The Needs me toggle swaps the per-project groups for one list of agent PRs across projects, sorted by what each needs: ready to merge, needs your review, stale or closeable, or waiting on the agent or CI.
• More holds Activity, Kanban, Automations, Usage, Fleet, Insights, and the morning digest.
• Kanban groups every thread by status (working, waiting on you, done, failed) so a pile of parallel runs stays readable.
• Activity is a chronological feed, grouped by day, of everything your agents did.

Planboard reads the board from labels. Agents on a GitHub-origin project write with the coder-threads tools issue_create, issue_list, issue_set_plan, issue_complete, issue_comment and issue_label (omitted when the origin is not GitHub). Sandboxed gh cannot see macOS keychain credentials, so those tools run on the host instead. An issue labelled plan:doing lands in In progress, plan:done or a closed issue in Done, and any other open issue in Todo. Other labels show as badges on the card. Agent sessions are told this convention, so “keep the plan on the board” is enough to have multi-step work tracked as issues. The view needs a project whose origin is on GitHub or GitLab. GitHub calls go through its API with a token saved per host in Settings, Git, under Source Control, or the GitHub CLI's token when none is saved; GitHub Enterprise hosts work the same way. GitLab goes through glab, including self-hosted hosts with "gitlab" in the name. The header also shows review load: how many open, non-draft PRs are waiting and their combined line count. Thresholds follow the 400-line cap, four PRs or 1,200 lines is busy; seven or 2,400 is overloaded, because an orchestrator that parallelizes agents manufactures review bottleneck, not agent bottleneck.

The board can also dispatch for you: turn on auto-dispatch and an issue entering plan:todo starts its own thread, so labelling a ticket is the same act as queueing the work.

Cards can depend on each other. An issue that GitHub marks as blocked by another, or that carries a blocked-by: #12 label, shows a Blocked by badge, and auto-dispatch skips it until the blocker lands. Live plan steps now come from OpenCode and Kimi runs as well as Claude, and the planboard works on SSH remote projects.

The sidebar's project scope filter limits Kanban, Planboard and Activity to the same repo, not only the thread list. Spaces are gone; cards carry their project slug instead.

Saved views and returning to work

Save a named sidebar view to reuse a combination of project, search, status, provider and tag filters. Views store matching rules, so new matching threads appear automatically. Changing a filter marks the active view modified; update or rename it from the same menu. Deleting a view leaves its threads alone. If its project or another filter is missing, the view says it is unavailable instead of showing all work.

Activity and Kanban have a project selector in their own header. Planboard search accepts a title, an issue number or #123. The PR view searches number, title and branch, and offers more results beyond its initial list. Open a thread from a board or report and use Back to to restore the view, filters, scroll and row focus. Usage's thread breakdown also links directly to its threads.

Recently deleted and moving threads

Delete offers Undo and keeps the thread in Recently deleted for seven days. Restore returns the same conversation, notes and work log without starting a run. The shelf shows the expiry and also offers permanent deletion. Restoring a thread is not a guarantee that its former worktree is still on disk.

Move to project in a thread's menu moves an idle conversation to another project. A running thread, worktree thread or pending worker cannot move. The move clears the old repository's session, branch and PR bindings so the next run uses the new project.