Brain
What your team knows, every agent knows.
Today each agent starts from zero, and the know-how sits in heads, chat threads and copies on laptops. Brain is one shared place for your company's skills, notes and facts. Write it once, give folders to the people and agents who need them, and every Crew, Code workspace, Goal and MCP client reads the same thing.
BrainCompany / Engineering
In Claude CodeReading from Brain
How do we roll back a bad checkout deploy?
Read Engineering / Payments / Checkout / deployment from Brain
Roll back to the last tagged release, then check the payment queue before reopening traffic. The steps are in the team's deployment skill; I followed version 4.
Illustrative example.
What it solves
Know-how that stays put. Agents that start from scratch.
Every chat starts empty
People paste the same context into every conversation. In Brain it is written once and every agent reads it.
The same facts, copied everywhere
Notes about the company and its people end up duplicated across workflows, Crews and laptops, and drift apart. Brain keeps one copy.
Skills copied between laptops
A skill shared as a file goes stale in every copy. Publish it to Brain once, and clients fetch the current version.
Knowledge in heads and threads
Decisions and runbooks live in a few people's memory or a Slack thread. Brain gives them a home your agents can search.
No control over who sees what
Access is set per folder with Reader, Editor and Owner roles, and an agent only reaches what the person it runs as can.
It piles up and gets messy
One command,
/organize, merges duplicates and tidies folders by products, teams or entities, and every move is reported.
How it works
Folders, roles and one connection. Used by every agent.
Organize in folders
Skills, notes, facts and sources live as Markdown entries in nested folders. You choose the structure, and agents can tidy it.
Grant by folder
Give people and agents Reader, Editor or Owner on a folder. Access carries down into the folders inside it.
Connect your agents
Crews, Code and Goals use Brain directly. Claude Code and other MCP clients connect to the same Brain. Each project picks off, read only, read and write, or chosen folders.
Keep it safe
Every entry has a history you can roll back, and you can back it up to a private Git repository.
Company skills
Publish a skill once. Everyone gets the current version.
Skills are shared today as files people copy into their own AI. In Brain, a skill is an entry with a version and an author. Anyone with access to its folder can use it from their own agent, and the agent says which version it followed. Skills that include scripts need a folder Owner to publish them.
One source
Update the skill in Brain and every agent that uses it gets the change.
Versioned
Each publish makes a new version, with the author and date recorded.
Works from your own tools
An MCP client such as Claude Code fetches a skill and installs it in its own skills folder.
FAQ
Brain, answered.
What goes in Brain?
Skills (how to do a task), notes (what happened or was decided), facts (specific statements) and sources (the original document or a link to it). They are plain Markdown entries in nested folders, like Engineering/Payments/Checkout.
Who can read and change it?
Whoever you give a folder to. Access is set per folder and inherited by the folders inside it, with Reader, Editor and Owner roles. An agent can only touch the folders that the person it runs as can.
Can I undo a change?
Yes. Every entry keeps its history, and each change records who made it and why. Edits use a version check, so two agents can't silently overwrite each other.
Where is it stored, and is it backed up?
On your AgentWorks server as Markdown files. You can connect a private Git repository and publish a backup yourself: commit the versions you choose, then push.
Which agents can use it?
Crews, Code and Goals on AgentWorks, and any MCP client, such as Claude Code, through the same connection. Each project chooses how much Brain it gets: off, read only, read and write, or only chosen folders.
Does it search by meaning?
Not today. Search finds the exact text you type and shows the matching lines. Organizing entries into folders and tags is what makes things easy to find.
Do agents learn on their own?
They write to Brain when a project is set to read and write and the work calls for it, or when you ask. You decide per project. Nothing is saved from a chat unless an agent saves it.
Can I edit it by hand?
Browse, search and read it in the app, and use the Brain chat to manage access and backup. Content is changed by agents and clients, so a person tells an agent what to add or fix.
Start with what everyone keeps asking. Put it in Brain.
We set up Brain with your team: pick the first folders, move in the notes people ask about most, and connect your agents.