Next work and loose ends

Surfaces: web app (the Next work band on the dashboard) · your agent (next-work and loose-end tools)

The web app is at https://<your-workspace>.kcap.ai for a cloud workspace; on the local edition the same pages are served from your machine. The desktop app opens it from Help and support → Open dashboard, and kcap local open opens the local one from a terminal

Next work is a ranked feed of what deserves your attention: work teammates are waiting on, review requests, sessions you interrupted, loose ends you or your agents left, unfinished work items, and new backlog. Every row says why it is there and points at the evidence. A loose end is the smallest unit in it: one concrete piece of unfinished work that an agent or a person declared, which someone can claim and close

What you can do

See what to work on next. Read the Next work band at the top of the dashboard, or ask your agent. Rows take turns by the signal behind them, so one signal cannot crowd out the rest. With teammates, what they are blocked on leads; alone, your own unfinished work does. Each row shows its reason, the latest session or work item, and who is involved. All clear for now means the feed is empty

From your agent:

What should I work on next?

The agent presents the feed with its reasons, and offers it unprompted when a task wraps up

Snooze, dismiss and restore. On a loose end, Snooze holds it out of the feed until tomorrow, three days or next week; Show now lifts the snooze. Dismiss removes any suggestion; the dismissed table at the bottom lists them with Restore. A dismissed row is dismissed for you, not for the team

Start an agent on a suggestion. Work on this opens a launch dialog with the daemon and checkout, the harness and model, and the prompt the agent will receive, prefilled from the row. The agent starts with the work item or loose end attached, and the row leaves the feed once it is claimed

Leave a loose end. When a session stops short, the agent records what is left:

I’m stopping here. Leave a loose end for the retry test that still needs writing

A loose end names the work, the session that left it, and the repository. Agents also declare them on their own when they defer something. To see what is open:

What loose ends are open in this repository?

Pick up a loose end. Claiming a loose end makes it yours; a second claim is refused and names the holder. Close it when the work is done, or release it to hand it back:

Claim the loose end about the retry test and work on it

The retry test is in. Close the loose end you claimed

Release that loose end, I’m not going to get to it this week

The trace on a loose end shows who declared it, who claimed it, where it was closed and the sessions that sighted it along the way

Help me get unstuck

The feed shows work I already finished. The signal behind it has not caught up: a merged PR not yet seen, a session still marked active. Dismiss the row; restore it if it comes back for a real reason

A loose end says someone else has it. They claimed it. Ask them, or wait for them to release it. A refused claim is not permission to start anyway

My agent did not present next work. The list is one of the session-start pieces, and it is skipped when disable_nextwork_nudge is set. In a terminal, kcap config show prints your settings; kcap config unset disable_nextwork_nudge turns the list back on from the next session. It also needs a workspace plan that includes work items