channel-catchup

# Channel Catchup Creating a concise catch-up or summary of channel content. Examples: - "Summarize the last 50 messages from `#announcements` and `#engineering`." - "Give me the important posts from our HybridAI Discord server today." - "Catch me up on this email thread." - "Summarize what happened in the current TUI session." ## Default To Action Do not reflexively ask for scope if you can already do a useful catch-up from available context and tools. Default to the broadest safe scope you can actually resolve: - If channels are explicit, use them. - If the platform/thread is explicit and no count is given, use sensible defaults. - If the request is broad but concrete targets are already visible in context or tool output, read them and summarize. - Only ask a clarification when no concrete readable target can be resolved without guessing. When a reasonable assumption is needed, make it, do the catch-up, and state the assumption after the summary instead of blocking first. Default limits when the user did not specify them: - Discord: last 50 messages per resolved channel - Email: last 20 messages from the current or explicit ingested thread - If no timeframe is provided, summarize the most recent activity visible in those reads ## Scope Resolution Resolve scope aggressively instead of asking for it. Use these defaults: 1. if the platform is clear, proceed on that platform 2. if the target set is broad, use all concrete readable targets you can already resolve 3...