AgentLayerโ–ธdocs
Use it

Standup and checkpoints

Where things stand, at a glance. Your standup as a card to read while you talk, and a checklist of where one session, or every recent session, has got to.

Standup is for the meeting: it turns the last day's work into what you did, what's next, and what's blocked, ready to read when your turn comes. A checkpoint is for getting your bearings: it maps the session you're in, or every recent session, as a checklist of what's done, what's next, and what's waiting on you.

Standup

"Standup is coming up", or attention standup, builds what you did, what's next, and what's blocked from git, pull requests, sessions, and the board. It derives all three rather than asking: Next comes from Today, and Did from what landed, what the sessions did, and the tasks you closed. attention standup 48 widens the window from the last 24 hours.

The reply is a glance card, meant to be read mid-sentence when standup reaches you:

๐Ÿ™ STANDUP ยท Tue Jan 06 ยท last 24h
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿšข SHIPPED ยท 2
   #101    retry flaky webhook sends    โœ“ verified
   #102    cap the export page size     โ— merged

๐Ÿ”ง IN FLIGHT ยท 1
   #105    signup flow test pass        โ—Œ needs review

โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿ‘‰ NEXT
   1  #106 search demo                tomorrow

โณ WAITING ON
   Alex       #103 repro steps        today
  • โœ“ is verified or done, โ— merged but unverified, โ—Œ waiting on someone, โœ— failed.
  • The card opens with your agent's own emoji.
  • The full update, with its evidence, is saved as a report you open when someone asks a follow-up. The report keeps the standup name, so the next run can tell what a skipped day left unsaid.
  • With Slack connected, standup checks what you already posted so you don't announce it twice.
  • On Monday it also sets the week's goals, and on Friday it scores them, the way goals week does.

Checkpoints

A checkpoint answers "where does this stand?" in a form you can read at a glance. It is written when you ask for it and never between turns. attention checkpoint maps the session you're in:

**Fix the export timeout**

โœ“ Timeout reproduced with a 50k-row export (test fails before the fix)
โœ“ Page size capped at 5k rows (tests green)

โ–ถ Checking the CSV stream on staging
โ–ท next: re-run the 50k export on staging and time it

โ˜… **Waiting on you**
  1. Merge #102 now or after staging? โ†’ after staging: the cap changes a public limit

โš  The cap also applies to the API export, which two customers use

**Changed since the last checkpoint**
  acme-app  feat/export-cap  the cap and its test  (committed a1b2c3d)

Every finished step says how it was proven, or is marked (assumed). โ–ถ is what is in progress and โ–ท the next step. Decisions waiting on you carry the agent's pick, traps get a โš , and a section with nothing in it is left out. The checkpoint is written in chat, so the session capture files it into knowledge. When the work belongs to a task, it also lands on that task's thread.

Every session at once

attention checkpoint all does the same for every session in the last 24 hours that ran in this home or its code folders. attention checkpoint all 48 widens the window, and a word narrows it to sessions whose folder or title contains it.

โ˜… **Waiting on you**
  1. Fix the export timeout: merge #102 now or after staging? โ†’ after staging: the cap changes a public limit
  2. Onboarding emails: send the draft to Alex for review? โ†’ yes, the copy is final

## ๐ŸŸข In motion (last hour)

**1. Fix the export timeout** ยท *12m ago*

โœ“ Timeout reproduced with a 50k-row export (test fails before the fix)
โœ“ Page size capped at 5k rows (tests green)

โ–ถ Checking the CSV stream on staging
โ–ท next: re-run the 50k export on staging and time it

โ†ณ `claude --resume 3f2aโ€ฆ`

## ๐Ÿ• Earlier today

**2. Onboarding emails** ยท *3h ago*

โœ“ Three-email sequence drafted (assumed)

โ–ท next: send the draft to Alex

โ†ณ `claude --resume 9c41โ€ฆ`
  • It opens with every decision waiting on you, ranked by importance and then by how long it has waited. Decisions are listed once, there, so a card holds only the session's own steps.
  • A card per session follows, with its resume command.
  • A session that already wrote a checkpoint has that checklist reused, with anything that happened since folded in.
  • When you ask for it yourself, it ends by offering to jump to one of the waiting sessions.

The saved report is the session radar. The dashboard's Sessions page shows it, plan reads it so work you already started ranks above anything new, and the briefings put its waiting decisions in their first moves. The dashboard and sync run it to keep it fresh. To find a past session by what it worked on rather than when, use find-session.

On this page