How Souvenir is organized
Souvenir is four parts over one shared context. Anything you do in one part is available to the others — that shared context is what makes the team of agents work as one.
One shared context
The spine of Souvenir is a single operational layer that every part reads from and writes to. Your connected apps, conversations, pins, and decisions all live here once — so an agent doesn’t start from a blank slate, the Brain knows what you’ve already done, and your team isn’t the manual bridge between tools.
The four parts, and how they relate
You start in the Chatspace — one chat, every model. When a task needs a specialist, you hand it to an Agent. When a job is multi-step or recurring, the Brain runs it across your connected apps. And you can drive all of it from Slack, where your team already works. Each part feeds the same shared context, so work flows between them instead of getting stranded in tabs.
Words you’ll see across the product
- Chatspace
- Your unified chat. Every frontier model in one thread, auto-routed, with memory that persists.
- Agent
- A role-tuned AI specialist you set up once — its instructions, model, knowledge, and tools — and reuse.
- Brain
- The orchestrator. Give it a goal and it plans and runs the multi-step work across your apps.
- Connector
- A link to one of your apps (Gmail, Slack, Notion, Drive, and more) that Souvenir can read from and act in.
- Pin
- A saved card — a response, insight, or artifact you keep on a Pinboard, auto-tagged and searchable.
- Highlight
- A selection you mark inside a chat to keep or reuse, without saving the whole response.
- Project
- A shared folder of chats, pins, and context — the unit teams collaborate in.