For developers using AI coding agents.
The AI only ever sees the messages you hand it — and you can see exactly what that is.
Select Slack messages in place. Review and redact. Seal a capsule. Your coding agent dereferences it through a read-only MCP server — no Slack token in the agent, ever.
rolling back to 2024.06.18. metrics show the latency spike started at 14:31 UTC.
cause: the new "warm pool" code path wasn't gated. patch incoming.
postmortem scheduled. attaching the timeline.
Reference
cap_h7n3pq2k…
Content hash
9c1b·4f3a·d802·17e6
Trust by construction
Three guarantees, each one verifiable.
01
Read-only Slack scopes.
The Slack app cannot post, edit, or delete anything. That's enforced by the install manifest, not a runtime check.
02
You curate, message by message.
Nothing leaves Slack unless you explicitly select it. No background sync. No channel scraping. The capsule is exactly what you picked.
03
Every read is recorded.
The agent reaches the capsule through an OAuth-scoped MCP endpoint. Each dereference is timestamped with actor and client in the audit log.
How it works
Manifest → connect → reference. Thirty seconds.
01
Install from the manifest.
One screen of read scopes. No write permissions are requested — they don't exist in the app.
02
Select in Slack.
In any message overflow menu, hit "Add to capsule." Or react with :capsule:. Or shortcut a whole thread.
03
Hand the agent the reference.
Seal the capsule, copy the id, paste it into your agent. The agent reads through MCP — never with your Slack token.
Open source. Self-host or use the hosted reference.
MIT licensed. docker-compose up brings the entire system up on your own infrastructure. The code, the schema, and the audit trail are all yours.