Welcome to Busabase
Busabase is the system of record for AI agents — an open-source (MIT) context database and workspace where agents and people share the same data, docs, skills, and apps.
Busabase is the system of record for AI agents — an open-source (MIT) context database and workspace where agents and people share the same data, docs, skills, and apps. Run it on your own machine, self-host it inside your network, or use Busabase Cloud.
Agents read what is already in the workspace, do the work, and leave the result there. The next agent, and your team, builds on it instead of starting over. Every change carries a message, a diff, an author, and a history you can undo.
New here? Jump to the Quick Start: connect your agent and get your first Base and records in about 5 minutes.
The problem: agent work disappears
Your agents produce more every week, and most of it ends up in chat logs and one-off files. When the session closes, the next agent starts from nothing, and your team can't find, trust, or reuse what was done.
Busabase is where that work stays. It lands as things people and agents can both use, with the history behind every change.
What lives in a workspace
| What | Stored as | What it gives you |
|---|---|---|
| Data | Bases with typed fields, views, and records | Tables your agents and your team read and update together |
| Docs | Doc, File, and Drive nodes | Knowledge an agent can search and cite |
| Skills | Skill nodes and playbooks | A way of working saved once, so any connected agent can follow it |
| Apps | AirApps | Interfaces built on the same data, that open inside the workspace |
Agents reach all of it over MCP, an agent skill, the CLI, or the REST API. Busabase has no built-in model: you bring your own agent.
Every change is on the record
Writes work like git, so nothing is overwritten and every row has a past.
| Git | Busabase | What it is |
|---|---|---|
| repo | base | a content type and its fields |
| commit | commit | an immutable snapshot of an edit |
main | record | the current, merged row |
| pull request | change request | an edit, with its message, diff, and author |
| merge (ff) | move the record pointer | merging advances the record; nothing is overwritten |
An agent with write access merges right away, so a change request doesn't mean anyone has to wait. See Core Concepts for the full model.
Hold back the writes that matter
Human review is optional, and you turn it on per credential. Give an agent a proposal-only (changeRequest) key, or send a single write with autoMerge: false, and that change waits in the Inbox until a person decides. See Change Requests and API keys.
What you can do with Busabase
Connect your agent
Claude Code, Codex, Cursor, or anything that can call MCP or HTTP.
Start from a template
Install a working setup: data, a manual for your agent, and often an app.
Keep your data in Bases
Typed fields, views, and records that agents and people share.
Save a skill once
Agents find the skills and prompts you saved, and follow them.
Build an app on it
Packages, skills, templates, and AirApps on top of the same workspace.
Read it over the API
Merged records flow downstream over a token-authenticated REST API.