Launching today
Busabase
The general system of record for AI agents
139 followers
The general system of record for AI agents
139 followers
Different agents. One shared base. Busabase is a general-purpose database and workspace for people and AI agents. Keep business records, docs, skills, and apps in one place so the next task can build on them. Connect Claude Code, Codex, and more. Set access, review changes when needed, and see what changed. Busabase is open source, with Cloud, Personal Desktop, and self-hosting options.
Love this concept. A shared source of truth for agents is long overdue. Upvoted!
@carlvert Thanks for the support, Carlvert! I'd love to hear your use case if convenient
If I connect an agent, what actually enters the shared workspace? Do private chats and local files stay private unless someone chooses to add them?
@stellylin Thanks for commenting, Stelly!
Connecting an agent doesn't automatically share your private chats or local files. Content enters Busabase when you or your agent explicitly adds it. You can also set permissions so that agent changes go through review before being merged into your team's data.
What kind of information would you like to share with your team? I may be able to help you find a setup that fits.
@stellylin Stelly, connecting an agent does not automatically copy its existing private chats or local files into Busabase. Content enters the shared workspace when you or an authorized agent submit it.
You can put a rule in your project’s AGENTS or CLAUDE instruction file, such as “save approved project briefs to Busabase, but never save private chats.” That tells the agent when to use the Skill. The permission grant is the stronger boundary: start with read-only or proposal-level access, verify the workspace it connected to, and check the agent app’s own local-file permissions separately. Connection and permissions guide: https://busabase.com/docs/mcp
Which are you most concerned about: chat history, local files, or customer data?
If a company already uses agents across engineering, marketing, and sales, what should it add to Busabase first so managers can get useful project updates by simply asking?
@alexia_li Hi, Alexia, I'd start with one project that spans those teams.
Add its goal and brief, then a simple tracker with owners, status, blockers, and next steps. You don't need to move all three departments' information at once.
Have each team's agents record relevant updates there. A manager can then ask, "What changed this week, what's blocked, and who needs to act next?" The answer is grounded in the information your team has recorded and kept up to date.
@alexia_li @matthewwei asked a related question about sharing context between Codex and Claude Code. In my reply, I shared an example of using project instructions to tell agents when and where to fetch relevant business context from Busabase.
For a company using agents across departments, I’d start with one active project. Add its brief, goals, and relevant product or business information as a shared knowledge base. That gives each department’s agents the same factual starting point, helping keep their work consistent.
Then add the information a manager needs for updates: current status, owners, recent progress, blockers, key decisions, and next steps. Include when each update was recorded, and make keeping those records current part of the team’s workflow.
With that context available and the right access, a manager can ask, “What changed this week?” or “What’s blocking the launch?” Their agent can pull the relevant records across engineering, marketing, and sales.
If you’d like a more detailed example for your team’s workflow, feel free to reach out!
@alexia_li Seey’s suggestion to start with one cross-team project is exactly right. If you’d rather begin with something tangible, Busa Standup is a starting template for team check-ins and blockers: https://busabase.com/templates/busa-standup
I’d adapt it around one project: keep its brief in a Doc, and ask each connected agent to record its dated outcome, owner, blocker, next step, and source after completing work. Then the manager can ask what changed and inspect the underlying updates. The template won’t collect every agent’s activity automatically; that write-back step is what makes the answer useful. Which project would you pilot first?
As a fellow AI founder, I’m really glad to see someone working on this. There’s so much attention on what agents can do in a single session, but I’m just as interested in what the next session—or another teammate—can actually build on. That’s what makes the shared base idea compelling to me.
I’d love to hear how you handle two agents updating the same record. How does a person review conflicting changes and decide what to keep?
Congrats on the launch, team. This feels like a problem worth spending years on, and I’m rooting for you.
@leo_ye Thanks, Leo! I care about that too: the next task should be able to build on work already done.
If two agents start from the same version and change different fields, those changes can be combined. If they change the same field to different values, the merge is blocked and the conflicting fields are flagged.
On the review page, a person can inspect the proposed changes and open the current record for comparison. They can then revise the proposal to keep the current value, use the proposed value, or combine the information before reviewing and merging it. They can also close the proposal and leave the record unchanged. The changes and revisions stay in the history.
It's a bit like Git, but for business data such as customer records and project statuses.
It means a lot to have your support as the founder of MyClaw.ai, Leo! Thanks Again。
Are you thinking about agents collaborating within your team, or agents in your product maintaining shared data? I can walk through an example for your use case.