A team knowledge layer agents can read and write.
The brain is the third pillar of this+that, alongside DoBox (your task manager, fed by messages, workflows, or by hand) and Workflows (automations triggered by messages, schedules, or anything else you wire up). It's a writable knowledge layer where the same pages humans read are the pages agents act on. Workflows ground their decisions in what your team actually knows. Sub-trees publish outward as customer-facing artifacts. The result is a team that compounds.
Free during beta · No credit card required
Single-player wikis collapse the moment work involves anyone else.
Obsidian, Mem, and the rest of the personal-brain tools work great if you're the only one tending the garden. The patterns mostly assume one curator, one agent, one knowledge graph. Fine for individual research. It collapses the moment a teammate needs to find the fact you wrote down, or an agent learns something during a run and has nowhere to record it, or a customer thread needs a price that nobody owns the source of truth for.
The personal-brain patterns aren't wrong, they're under-scoped. What makes a knowledge base useful for one person — markdown, hierarchy, linking — is not what makes it useful for a team. That requires identity, permissions, multi-author edits, and a surface the agent can write to in real time.
More on the thesis in our essay on why agents need a brain they can write to.
Workflows read the brain. Workflows write the brain.
Humans reading and writing a wiki is the baseline. What's different about the brain is that agents are equal-class participants in both directions. Read and write are the two structural moves, and on each, the agent half is the novel half.
Workflows that read the brain
An agent or workflow reads existing team knowledge to act. The agent's reply is grounded in what your team actually decided, not in what a base model guesses.
A sales agent backed by a price sheet
Pricing questions arrive over email. The agent answers using the canonical price sheet maintained in the team brain, schedules a follow-up call if the prospect is interested, and logs the interaction as a task that links back to the source thread. When pricing changes, you edit the brain page once. Every downstream answer updates.
Workflows that write the brain
An agent or workflow produces durable knowledge over time. Output that used to be a one-shot report becomes a compounding history you can search.
A competitive analysis agent that compounds
Each run produces a page in the brain. What the agent found, what was new since last time, what changed. The next run reads the previous one as context. Over weeks the brain accumulates a history of how competitors have moved, which positioning they've tried, what's worked.
Humans get a normal wiki too.
Markdown editor with @-mentions for people, tasks, and other pages. Hierarchical page nesting. Page-level versioning and conflict detection when two people or two agents edit at once. Attachments. Search. The familiar wiki experience is the baseline, not the differentiator.
We can write into yours instead.
Some teams have already settled on a different home for knowledge: a Notion workspace, a Confluence, a shared Git repo. Our agents can read from and write into those through MCP, the same way they read from and write into the brain.
The brain inside this+that is the default, with the lowest friction and the tightest integration with the rest of the product. But if your team has already settled on another home for knowledge, our agents can keep that home up to date instead.
Your brain is not training data for anyone.
Brain content is encrypted at rest with AWS-owned keys. No this+that employee can decrypt it. We never use Customer Data (including content from the brain) to train, fine-tune, or improve any machine learning model — ours or any third party's. The contractual commitment lives in our DPA and our no-training clause. Sub-processors that touch brain content are bound by the same restriction.
Build a brain your team and your agents both contribute to.
Sign up and start writing pages today. Your first read-and-write workflows can land this week.
Free during beta · No credit card required