Launching today
Busabase
The general system of record for AI agents
439 followers
The general system of record for AI agents
439 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.
Free
Launch Team
Floot MCPBuild and ship web and mobile apps inside Claude or ChatGPT
Promoted
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.
If an agent updates a business record off a copy it read an hour ago and a teammate edited it in between, which change wins? Curious how "review changes when needed" works when it's an agent racing a person.
@lancelot_d_souza1 It's a bit like Git, and collaborative editing.
One shared base where different agents read the same records, docs and skills is the missing piece once you have more than a couple of agents, since context gets rebuilt from scratch every time otherwise. Reviewing changes before they land is a sensible safety net. How do you keep two agents from overwriting each other when they edit the same record at once?
@karimbenkeroum Thanks, Kareem! Conflict handling seems to be on everyone’s mind; it’s come up a few times today.
Our approach is quite similar to Git, with some ideas from collaborative editing mechanisms like OT/CRDT in how we handle conflicts. Feel free to try it with mutil agents updating the same record and see how it works.
the "review changes when needed, see what changed" line is what sold me, not the shared-base idea itself. every team I've seen try a shared context store for agents eventually hits the same wall: one agent writes something subtly wrong into the base and every agent downstream inherits it as fact, with no one noticing until output looks off three steps later. does the change review actually block a write until a human looks at it, or is it more of an audit log you check after the fact once something's already gone sideways
@galdayan It works similarly to Git and code review（Change log, Change review and Approval gate）, with humans acting as the final line of defense.