It is Monday. Two agent sessions ran on Friday, one issue was planned over the weekend, and you have no idea which of it landed. Fifteen minutes before standup.

​
Start with What’s next

What’s next holds the committed work: Review first, then In progress, then Planned, so the thing closest to done leads the list. That is the set you can actually act on this morning, and it is where Friday’s finished work shows up for review. Two neighbors tell you the rest of the story:
  • Triage is incoming work, decided one issue at a time: accept it, plan it, or decline it. Anything filed over the weekend is waiting here.
  • Backlog is accepted work you have not committed to. It is not today’s work, however urgent it looks.
Issues is the wide lens: everything committed, Planned through Done and Cancelled, with closed work kept for two weeks after its last touch. When the question is “what shipped on Friday”, this is the view that answers it.

​
Sweep the sessions

Open the Sessions panel. Recent rows read Working… while a session is active and show its last message otherwise, so a slow scan tells you what is still running. Open anything that finished and read the right rail: the reported goal, task progress, whatever waits on your approval, and the artifacts the session produced. Anything you still owe an answer to, answer now. A session paused on a tool approval does not resume until you decide.

​
Then search for the specific thing

The morning sweep answers “what happened”; the palette answers “where is it”:
  • Cmd+K opens the command palette from anywhere. It searches sessions, projects, issues (including code lookup on an issue’s key), docs, and agents, so an issue code or a session title in your head is two keystrokes from open.
  • In Docs, Cmd+P or Cmd+O opens the same switcher over documents.
  • The Search issues box narrows whichever view you are in, and every view and filter combination lives in the URL, so a configured view is a link you can share.

​
Hand the first item off

By now one item is obviously first. Hand it to an agent instead of staring at it: open a session, state the goal and the constraint, and let the loop run while you go to standup. One thing to know before you do: an engineer agent works in an ephemeral cloud sandbox that resets between sessions, when a session crashes or times out, and when another agent works in the same space. Work that was never pushed does not survive a reset. Anything you want kept, get pushed.

​
What good looks like

  • What’s next was your first surface, and the first item you touched was the one closest to done.
  • Every session that ran since Friday either produced something you reviewed or got one.
  • Nothing is waiting on your approval while you are in standup.
  • The first handoff happened before standup, not after.