Skip to content

Daily Brief & Inbox Loop

Daily Brief & Inbox Loop

The vault now learns. Anything captured into inbox/ — X bookmarks, dumped URLs, podcasts, freeform text, daily notes — gets read every night by an LLM synthesis loop that draws connections, routes action items to Apple Reminders, and writes a structured brief the owner reads the next morning. The previous routing-table “shred” (URL→Instapaper, action-verb→Reminders, raw-archive bookkeeping) was retired in favor of this loop.

What lands in inbox/

Capture is intentionally thin — extract content and stash a file, nothing else. Three surfaces feed it:

  • dump skill — the owner types dump <url> (or sends a URL, image, or block of text to the agent). The skill extracts via trafilatura for articles, podcast-transcript for podcasts, OCR for images, or plain pass-through for text, and writes a single file to inbox/YYYY-MM-DD-<slug>.md. No wiki maintenance, no cross-linking on capture.
  • Daily X Bookmarks — system cron at 03:00 PT pulls the owner’s previous-day bookmarks via OAuth read-only scopes and writes one digest to inbox/YYYY-MM-DD-x-bookmarks.md.
  • inbox/quick-capture.md — append surface for freeform notes. Anything typed here joins the inbox pile.

The Daily Brief (04:00 PT)

An OpenClaw cron fires openai/gpt-5.5 in an isolated, light-context agent session every morning at 04:00 PT — one hour after the X-bookmarks ingest. Three steps:

  1. Route Reminders. Run inbox-to-reminders over inbox/*.md. Lines starting with action verbs (I need to…, Remind me to…, I want to…, TODO, Don't forget) become Apple Reminders via reminder-cli. Hash-dedupes so re-runs are safe.
  2. Read the window. Every file modified in inbox/ in the last 24 hours plus every file added or modified in notes/ in the last 7 days. The vault root AGENTS.md is read first as the authoritative contract.
  3. Write the brief. inbox/session-summary-YYYY-MM-DD.md with three sections:
    • Connections — three cross-references between recent captures and older notes, each cited with [[wiki-link]].
    • Pattern — one pattern across this week’s captures.
    • Question — one question worth sitting with today.
    • Reminders Routed — one-line summary of what Step 1 created.

No chat delivery. The brief lives in the vault, where the owner reads it during morning review.

The Weekly Synthesis (Sundays at 09:00 PT)

Same model, longer window, sharper questions. Reads everything added or modified in the last 7 days across inbox/, notes/, and ideas/. Writes inbox/weekly-synthesis-YYYY-MM-DD.md with:

  • Emerging Thesis — what idea is forming across the captures?
  • Contradictions — where do recent notes disagree with earlier ones?
  • Knowledge Gaps — what perspective is missing?
  • One Action — the single highest-leverage move this week.

It also produces an inline-styled HTML rendering at /tmp/weekly-synthesis-YYYY-MM-DD.html and emails both versions (HTML + markdown fallback) to the owner’s inbox via iCloud SMTP. The HTML email arrives before Monday morning.

Vault Layout

The kit conventions live at the vault root. See codex-knowledge-llm for the source kit.

FolderRole
inbox/Raw captures, daily session summaries, weekly synthesis. Everything new lands here.
notes/Source material plus index notes. The Daily Brief reads from here as “source of truth” for cross-references.
ideas/Synthesis, teardowns, implementation notes, original thinking.
projects/Active work and decisions.

Routing of an inbox capture into notes/<Title> - Original.md + <Title> - Index.md + a route-specific note (Structure Teardown, Implementation Notes, Concept Synthesis, Book Notes) is handled by the codex-knowledge-llm skill when the Daily Brief decides a capture is worth promoting.

State

The brief loop is stateless beyond two small files:

  • ~/.config/x-bookmarks-state.json — last 500 seen tweet IDs for the X bookmarks ingest.
  • ~/.config/inbox-to-reminders-state.json — hashes of action-verb lines already turned into Reminders (so the same line in quick-capture.md doesn’t duplicate the Reminder on re-read).

If a brief produces a useful synthesis, the markdown file in inbox/ is the durable record. If the owner wants something promoted from the brief into a permanent note, that’s a manual or codex-knowledge-llm-mediated move into notes/ or ideas/.