Busabase

The general system of record for AI agents

Productivity

Developer Tools

Database

Visit WebsiteSee on Product HuntGithub ⧉Twitter ⧉

honestly for dev teams I'd still keep that context in git, every coding agent already reads the repo. from my experience building Voiden that works well. is Busabase mostly for the business side, or do you see engineering teams moving it out of the repo too?

Does it work with agents I build myself, or only with tools like Claude Code and Codex??

Amazing idea!

Have to deal with this a lot now. Setting up each agent is a challenge. Would give this a shot today!

Looks cool, I want to ask if an agent should read project records but only propose CRM changes, how would you set that up? What can the reviewer see before accepting a proposal?

@seey @mrkelly Curious how this compares with existing databases and agent memory solutions ?

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.

Congratulations on the launch, Team

Connecting Claude code, Codex and other tools to the same base saves a lot of repeat setup. How long does it take to connect a new agent for the first time?

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

Congratulations on the launch! I really like the collaboration between all of you, and that each of you has shared your reasons for building it. I think this is a really exciting tool for businesses that work with freelancers or contractors. From experience, I know it can be very difficult to share the right information with the right people.

Curious about the permission system. Is it possible to set granular access so different team members can only view certain project records？

Congrats, Kelly and team! The before-and-after view of an agent's changes caught my eye. I'd want to see that before letting it update shared records.

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?

Congrats on Launch Do Shared Playbooks hold both Skills and custom prompts? How would a teammate reuse the same working instructions with another supported agent?

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?

Love this concept. A shared source of truth for agents is long overdue. Upvoted!

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.