The pattern you're describing — tasks scattering across Slack, email, and the CLI — is really a signal flow problem. Email is still where a lot of meaningful work originates (a client sends a question, a contractor delivers an update), but nothing today bridges that into an agent-native task queue cleanly.

Your roadmap mentions GitHub issues and email inboxes as upcoming integrations. For email specifically, the friction point I'd flag is that most inbound email carries context that agents need: who sent it, what prior thread it belongs to, what action is expected. A raw forward loses that structure. Worth thinking about whether the inbox integration consumes a parsed webhook payload (structured sender, subject, body, thread ID) vs. raw MIME — the former is dramatically easier for agents to act on.

The compressed context snapshot (ai-context.md) is a clever workaround for the amnesia problem. The gap it can't close is task provenance — knowing why a task exists, not just what it is. Linking tasks back to their originating email/Slack message/PR would give agents (and you) much better auditability when something goes wrong.