From “didn’t we decide this?” to “it’s built”, right in your team chat.
Context Keeper sits in a team's chat. It answers with the source when a question was already settled, and turns new ideas into work for Claude Code. This page is the running agent, read from its own state.
How it works
- 1
It reads every message
People talk in Slack or Discord. Through Switch it reads every message in the room, tagged or not.
- 2
It answers with the source, or stays quiet
When someone raises something already decided, it replies with where it was decided. Otherwise it says nothing.
- 3
New ideas wait for a yes
A new idea goes to the owner to approve. Then Claude Code builds it in a new channel.
- 4
The person who asked signs it off
They check the result in the room and say it works.
Today
UTC day, 6 November 2026
What it did in its rooms since midnight UTC. Staying quiet is most of the job, so a big quiet number is a good sign.
Replies
0
Times it spoke up in a room: an answer with its source, a decision written down or an idea logged.
Catch-up briefs
0
Short summaries for someone coming back to a thread they missed.
Stayed quiet
0
Times it read the chat and decided no reply was needed, like small talk and thanks.
Model spend
$0.00of the $6.00 daily cap
What today's Claude calls cost. A daily cap stops it overspending. 0 model calls, priced high so this is an upper bound.
Ideas in progress
Newest change first
Ideas people suggested in a room, and how far each has got. Nothing moves to the next stage until a person says yes on an approval card in the room.
What the stages mean
- Noted
- Someone suggested it. It waits for the owner to approve.
- Who acts: The owner
- Approved
- The owner said yes. It is being handed to Claude Code.
- Who acts: The agent
- Building
- Claude Code is building it in its own channel.
- Who acts: Claude Code
- Waiting for Kash
- Claude Code needs an OK before its next step.
- Who acts: Kash, the owner
- Done
- Built. The person who asked checks the result.
- Who acts: The person who asked
- Signed off
- The person who asked says it works. Finished.
- Who acts: Nobody
Blue: movingAmber: waiting on a personGreen: doneRed: stuck, needs a look
Latest answers
Posted in public rooms, newest first
When someone asks about something the team already settled, it answers in the thread and links to where it was decided. The label says what kind of answer it was.
What the labels mean
- In the record
- Already decided. The reply links to where.
- The record says otherwise
- What was said clashes with an earlier decision.
- Reopen request
- Someone wants to change a decision. The owner decides.
- New idea
- Something new. It goes to the owner to approve.
- Related
- Not settled, but something close was discussed.
- Parked
- Raised before and set aside for later.
- Decision
- A new decision it has written into the record.
Rooms
The team chats it is in. One agent covers Slack and Discord at the same time.
- Ledgerly: ledgerly-pilotSlack
- Riverside Events: try-context-keeperDiscord
- ck-smoke-build-1104build room, Claude Code
Also 9 test rooms and 1 room it listens to without posting.
Switch pieces in use
Switch is the platform the agent runs on. These are the parts it uses, in plain words.
- Rooms and the agent event streamIn useSwitch passes it every message in its rooms, so it can follow the whole conversation.13 rooms connected; every message heard, tagged or not
- BridgesIn useThe same agent in Slack and Discord at once, not a copy for each.Discord, Slack: one agent, one Switch server
- Room documents and the Decision logIn useWhere the team's decisions are kept. Its answers link back here.the record it cites, read from each room's documents and history
- Claude Code, by targeted messageIn useHow it hands an approved idea to Claude Code to build.job E on; 6 ideas handed off, each step behind an approval card
- Switch TrustIn useRules on the server that limit what the agent may do. It cannot change them.a guardrail policy on the server (settings not shown here)