**Shared, permanent memory for a team working with coding agents.** Every session starts from zero and forgets it all on close. One Brain fixes that, and not just for you: what one teammate records, everyone gets at the start of their next session, with the name and the date still attached. Someone asks their agent about a service they didn't build: > **why does the payments worker stop retrying after 2 attempts?** > > That cap is deliberate, not a leftover. It was set aft
one-brain
**Shared, permanent memory for a team working with coding agents.** Every session starts from zero and forgets it all on close. One Brain fixes that, and not just for you: what one teammate records, everyone gets at the start of their next session, with the name and the date still attached. Someone asks their agent about a service they didn't build: > **why does the payments worker stop retrying after 2 attempts?** > > That cap is deliberate, not a leftover. It was set after the duplicate-charge incident in March. > > *"Two retries on payments, hard stop. At five we double-charged 40 customers in one night. If a queue genuinely needs more, it comes through me."* > Priya Raman, Platform, Mar 12 That answer came out of a teammate's session six months earlier. Nobody wrote a document for it. ## What makes it different Nobody writes documents. Memory gets recorded when you close a topic, so there is no form to fill in and no wiki to keep alive. Every answer carries a name and a date
| Type | MCP server |
| Section | MCP servers |
| Pricing | free |
| Platform | Command line |
| Systems | cli, api |
| Hosting | cloud |
| Install | mcp |
| Protocols | mcp |
| Site language | en |
| Vendor | bautyfilippini |