> join
Join your chat channel.
Take part in the channel you already use, and answer there.
Join the chat channel you use
Answer in that same channel
Said in the room.
Asked back tomorrow.
One stored decision, ready when you ask.
Why Sederunt
> join
Take part in the channel you already use, and answer there.
Join the chat channel you use
Answer in that same channel
> act
Take one confirmed action from the request to the tool.
Interact with apps and tools using MCP
Confirm one action before it is sent
> remember
Ask, and you get the decision in words. The file stays where you stored it.
Ask what was decided
Get the decision in words
Works in Slack today · more chat apps coming
> multi-tenant
Only people in that meeting or channel can ask about it.
It stays with the group
Or the people invited
> portable
Tips for getting startedRun /init to create a CLAUDE.md
Recent activityNo recent activity
Keep the same recall in Claude Code, Cursor, Codex, or any agent that speaks MCP.
Ask from the agent you have open
Read the recall in that session
Sederunt joins a channel or a meeting, keeps the decision, and answers later from the agent you already use.
A channel, a meeting, or an announcement. It can answer in the room. An announcement can name a file.
The sentence that was kept, including who decided and which files were named. The files sit in Walrus Console. The answer does not open the file by itself.
Sederunt asks the person who made the request. It does not guess in the channel.
Both stay. The later name does not erase the earlier one. You choose which one is current.
Only people in that meeting or channel can ask about it, if the bot was there to hear it.
Yes files one task in Linear. One yes covers that write, and nothing else moves.