Busabase x Knowledge Base for Buda AgentKnowledge Base for Buda Agent
Buda Agent works in a visible cloud workspace: sessions preserve their own history, tool calls, and artifacts; the Agent Drive keeps files across sessions and restarts; Shared Space resources can be used across agents. Persistence makes context reusable, but it does not give an output a source, an owner, and a change history the whole organization can trace.
MAP
Buda keeps agent work visible and persistent; Busabase gives the outputs you share a source, an owner, and a reversible change history.
Buda Agent works in a visible cloud workspace: sessions preserve their own history, tool calls, and artifacts; the Agent Drive keeps files across sessions and restarts; Shared Space resources can be used across agents. Persistence makes context reusable, but it does not give an output a source, an owner, and a change history the whole organization can trace.
Messages, tool calls, artifacts, and diffs
Documents, code, configs, and generated files
Resources available to agents and human teammates
Source, Change Request, author, and history
BOUNDARY
Sessions are isolated while the Agent Drive persists across sessions and sandbox restarts
Buda keeps agent work visible and persistent; Busabase gives the outputs you share a source, an owner, and a reversible change history.
| Session evidence | Messages, tool calls, artifacts, and diffs | The trace of one isolated conversation |
|---|---|---|
| Agent Drive | Documents, code, configs, and generated files | Persistent working context for one agent |
| Shared Space | Resources available to agents and human teammates | Reusable team context with an explicit owner |
| Shared record | Source, Change Request, author, and history | Shared knowledge with every change attributed and reversible |
SCOPE
The workbench exposes tool calls, artifacts, and before-and-after diffs as inspectable evidence
Buda Agent works in a visible cloud workspace: sessions preserve their own history, tool calls, and artifacts; the Agent Drive keeps files across sessions and restarts; Shared Space resources can be used across agents. Persistence makes context reusable, but it does not give an output a source, an owner, and a change history the whole organization can trace.
The trace of one isolated conversation
Persistent working context for one agent
Reusable team context with an explicit owner
Shared knowledge with every change attributed and reversible
EVIDENCE
A persistent or shared file remains working context until it is written to Busabase as a Change Request
Sessions are isolated while the Agent Drive persists across sessions and sandbox restarts The workbench exposes tool calls, artifacts, and before-and-after diffs as inspectable evidence A persistent or shared file remains working context until it is written to Busabase as a Change Request
| Session evidence | Messages, tool calls, artifacts, and diffs | The trace of one isolated conversation |
|---|---|---|
| Agent Drive | Documents, code, configs, and generated files | Persistent working context for one agent |
| Shared Space | Resources available to agents and human teammates | Reusable team context with an explicit owner |
| Shared record | Source, Change Request, author, and history | Shared knowledge with every change attributed and reversible |
ACCEPTANCE
Buda keeps agent work visible and persistent; Busabase gives the outputs you share a source, an owner, and a reversible change history.
Sessions are isolated while the Agent Drive persists across sessions and sandbox restarts The workbench exposes tool calls, artifacts, and before-and-after diffs as inspectable evidence A persistent or shared file remains working context until it is written to Busabase as a Change Request
Verify Messages, tool calls, artifacts, and diffs before accepting The trace of one isolated conversation.
Verify Documents, code, configs, and generated files before accepting Persistent working context for one agent.
Verify Resources available to agents and human teammates before accepting Reusable team context with an explicit owner.
Verify Source, Change Request, author, and history before accepting Shared knowledge with every change attributed and reversible.
FAQ
Knowledge Base for Buda Agent: practical questions
Buda keeps agent work visible and persistent; Busabase gives the outputs you share a source, an owner, and a reversible change history.
Does a file become shared knowledge when Buda saves it to Drive?
No. Drive preserves the file and makes it inspectable. A shared Busabase record adds a source, owner, scope, and a Change Request history; give the agent a proposal-only key if you want to approve its changes first. How Change Requests work
Do Buda sessions automatically share conversation history?
No. Each session has isolated history, artifacts, and tool calls. The same Agent can still use files that persist in its Drive.
What belongs in Shared Space?
Put material there only when multiple agents or teammates should reuse it, and record its owner, version, and intended scope.
What should Busabase capture from a Buda task?
Capture the source artifact, producing Agent and session, proposed fields or diff, and the Change Request that merged it.
NEXT
Buda keeps agent work visible and persistent; Busabase gives the outputs you share a source, an owner, and a reversible change history.
Buda Agent works in a visible cloud workspace: sessions preserve their own history, tool calls, and artifacts; the Agent Drive keeps files across sessions and restarts; Shared Space resources can be used across agents. Persistence makes context reusable, but it does not give an output a source, an owner, and a change history the whole organization can trace.