Omniscio documentation
Browse all documentation
  1. Getting Started18
  2. Sessions & Agents134
  3. Inbox & Notifications67
  4. Projects & Tasks98
  5. Automation & Scheduling77
  6. Knowledge & Memory28
  7. AI Features71
  8. Integrations106
  9. Plugins & Marketplace34
  10. Cloud & Teams53
  11. Settings & Customization67
  12. Account & Billing28
  13. Troubleshooting79
  14. CLI & API Reference27
  15. Legal & Policies5
  16. Uncategorised17

Crew period summaries

A crew's lead can ask the app for plain-language summaries of what its crew did — hourly, every few hours, daily, weekly or monthly. Each finished window gets exactly one summary, written by a cheap one-off session from the crew's own record, and you read them on the crew's **Dashboard** in the Overseers hub. The lead gets the newest one on its next wake so it can quote it in its update, and nothing is sent to your inbox.

What it is

A crew can have the app write short, plain-language accounts of what it did, one for each finished period of time. A cheap one-off session writes each one from the crew's own record, so the account reflects what actually happened rather than what anyone remembers.

What a summary covers

  • Exactly its own window: tasks moved or closed, deliverables moved, notes, decisions and rules logged, work that landed, and helpers that joined or left.
  • A day or longer also carries the lead's scorecard for those days, including its own spend and its helpers' spend.
  • A weekly summary is written from the daily summaries of that week (and a monthly one from the dailies), plus the headline counts — so a long period never re-reads every task move. With no shorter cadence on, it reads the record directly.

Where to find it

You read them on the crew's Dashboard, in the Overseers hub, which also shows which cadences are on. You switch them on by asking the lead in the crew's chat ("send me a daily and a weekly summary"): the lead sets them for its crew, and the Dashboard says so rather than offering a control that would change them itself.

How it behaves

Turning summaries on and off

  • Cadences: hourly, every 2, 3, 4, 6, 8 or 12 hours, daily, weekly (Monday to Sunday) and monthly (1st to the end of the month). Any mix works.
  • Windows follow your local clock: hours count from midnight, days start at midnight, weeks on Monday, months on the 1st. The first summary covers the window the cadence was switched on in.
  • Off by default for every crew. Switching a cadence off and on again starts fresh — it never summarizes the time it was off.

What it costs, and when nothing is written

  • One cheap one-off session per summary (the same worker engine the crew's memory scribe uses), at most one per crew at a time, and only for a window in which something happened.
  • A quiet window costs nothing — no session, no summary, nothing shown.
  • The app was closed for a while? The missed stretch is covered by ONE summary on the next pass, never one per missed hour, and never lost.
  • A summary that could not be written shows on the Dashboard with the reason, where it would have been.

For agents

  • GET /crew/summaries — the caller's own crew: its cadences and summaries, newest window first (?cadence=daily, ?limit=N). Any live crew member.
  • PUT /crew/summaries/cadences with { "cadences": ["daily", "weekly"] } — lead only; an empty list switches them off. Leaves one line in the crew log.
  • Every written summary also leaves one crew-log line, and the lead's next wake carries the newest unseen summary of each cadence, once.
  • Off switch for the whole app: AMC_DISABLE_CREW_PERIOD_SUMMARIES=1. The feature rides the Agent crews switch (Settings → Lab → Agent crews).
  • Contract: crew-period-summaries-contract.md.

Related

What a crew is, how its lead gets work and what it may decide — Agent crews is the page to read first, with part 3 for the lead's own duties. What the lead is judged on, including the spend a day-or-longer summary quotes, is on Crew lead scorecard, and how a crew keeps what it learned between sessions is How overseers remember.

Last verified 2026-10-11