Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
sno away-brief run reads what already exists and prints one page of at most 60 lines. It changes nothing
except its own list of quota readings, and Reach, which may note that it has seen the cards that the inbox
read listed (it never moves, accepts or finishes them).
## Done new commits, charters delivered since the cutoff (with how many checks are proven),
progress records that finished or are still going
## Stuck charters not finished (with the numbers of the checks not yet proven), progress records
with tasks left that nobody has touched for two hours
## Needs you Reach cards of type question or decision waiting in the inbox
## Spend your heartbeats, and each vendor's quota now with the change since the last reading
A source it cannot read prints not read: <what> -> <why> and the rest of the page still prints. Each section has
its own share of the 60 lines; items beyond it are replaced by an and N more not shown line, so a long Done list
never pushes out what waits for the owner or the quota.
Prerequisites: bash 4+, GNU coreutils, git and jq. It uses sno deliver-proof (the deliver skill) to count
proofs, sno reach inbox, sno heartbeat --list and sno subscription-quota-check when they are installed.
sno away-brief run --since 12h in the project's git folder. Change --since to the time the owner
left (8h, 2d, or a date). Add --repo DIR for each other repository and --charters DIR for
folders that hold charters or progress records outside those repositories. Add --as <your seat> (or
set SNO_REACH_ADDR) so the inbox is read.sno away-brief mark
once; it stores a reading, so the next page can show what was spent since. Without an earlier reading
the page says so instead of guessing.sno handoff-checkpoint) with tasks left and no update for two hours. An agent that is busy but does not
write records looks quiet.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Answer how long agent work will take, how much longer active work needs, or what clock time applies. Estimate full AI-agent wall time, measure active progress first, and get owner-facing times from `sno report-time`. Never estimate human-developer time.
The English summary is being prepared. Showing the original description.
Prove that a reported run caused its intended real effect. Walk the executor path from entry to effect, capture one observable per hop, and report a result a no-op could not produce.
The English summary is being prepared. Showing the original description.
Report how many problems the two brains found: mutual review (the other model checks the work, from the peer-review records) and self-check (an agent finds its own error in its own conversation, judged by that agent's own model), side by side. Use when the owner asks whether the second agent or the reviews are worth it, or wants the week's review results.
The English summary is being prepared. Showing the original description.
Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.
The English summary is being prepared. Showing the original description.
MANUAL-ONLY: load solely when the human owner types `/cos`, uses `$cos`, or asks you to act as the Chief of Staff (COS). The COS is the one agent the owner talks to; it coordinates the owner and the per-project Project Leads (PLs). A task card, charter, or dispatch makes you an executor, not COS.
The English summary is being prepared. Showing the original description.
Turn repeated management failures into enforced COS or PL rules. Load ONLY after the owner has explicitly activated the cos role for this session and the COS core routes here. Never invoke directly.
The English summary is being prepared. Showing the original description.