catchup

name	catchup
description	Re-orient after a break — aggregates live work context from all sources and session memory into a concise briefing.

Catchup

Workflow

1. Run the data aggregator (Linear, GitHub, Drive, Slack) from the project root:

   uv run python scripts/catchup.py
   

   This includes Slack mentions and unread DMs via the SDK. If Slack data is missing from the output (e.g. token expired), fall back to the slack-reader browser agent.

2. Query Granola MCP for recent meeting notes, decisions, and action items. If unavailable, skip.

3. Search session memory for recent context (decisions, open threads, things flagged for follow-up).

4. Synthesize all sources into a briefing with three sections:

   • In progress — active work items across all sources
   • Needs attention — unread mentions, review requests, DMs awaiting reply, meeting action items
   • Since you were away — notable changes, merged PRs, closed issues, new threads, meetings held

Keep the briefing tight. Lead with the most time-sensitive items. Skip sources that returned no signal.