session-digest

Digests yesterday's closed agent sessions into a journal-led narrative estate via codex workers.

14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/intendant-dev/Intendant --skill session-digest-intendant-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-digest
Source: https://github.com/intendant-dev/Intendant/tree/main/automations/session-digest
Command: npx skills add https://github.com/intendant-dev/Intendant --skill session-digest-intendant-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a durable, searchable narrative record of daily AI agent sessions is tedious and error-prone when done manually. This Skill automates the daily digestion of closed sessions into a derived narrative estate, so long-term context accumulates without manual effort or double-processing. ## Core Features & Use Cases - Daily Automated Digestion: Fires once per day on a stamped cadence to digest the previous day's closed sessions into journal-led, idempotent narrative entries. - Bounded Codex Worker Pool: Dispatches up to 22 synchronous rolling codex exec workers on subscription OAuth, with quota-aware backoff, retry rules, and a three-failure suspension breaker. - Idempotent Estate Writes: Produces redacted digest markdown, JSON sidecars with verbatim anchored quotes and territory paths, and atomic journal appends, skipping trivial or already-digested sessions. - Use Case: An operator running Intendant-supervised Codex sessions stamps an evening anchor once; every night the Skill digests that day's sessions into the narrative estate that the weekly narrative-pyramid workflow later folds, with cost annotated per firing. ## Quick Start Stamp the daily digest schedule by running ctl agenda stamp session-digest with your project directory and an evening time so it fires nightly.

Frequently Asked Questions about session-digest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule a daily digest of agent sessions?▼

Stamp the automation once with ctl agenda stamp session-digest --project <dir> --at 'YYYY-MM-DD HH:MM', choosing an evening time. The daily cadence phase-locks to that first fire, so the anchor sets the nightly hour.

How does the session digest avoid double-processing sessions?▼

Digestion is journal-led and idempotent: candidates are only journal-absent or watermark-advanced sessions idle over six hours. If a narrative-backfill run is live, the firing annotates itself as skipped and exits so the two lanes never double-digest.

Does the session digest require an API key or billing?▼

No API key is used. Digests run as codex exec workers authenticated via Codex subscription OAuth only, never direct API billing. Reported costs are estimates, not billed dollars, and approving the manifest once is the standing spend authorization.

What happens when codex workers hit rate limits during digestion?▼

Quota failures never consume retries and never mark sessions stalled. The pool pauses refilling, backs off with shell sleeps, and resumes after a cheap probe succeeds; a hard cap ends the firing cleanly and surfaces via the suspension breaker.

Why did the digest fail with 'NS tool not installed'?▼

The pinned export tool at the estate's bin directory is missing. Run the narrative-backfill action once first; it stages the intendant export tool the digest depends on, then the daily cadence will proceed normally.