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 turn an output into an approved organizational record.
MAP
Buda keeps agent work visible and persistent; review decides which outputs become shared knowledge.
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 turn an output into an approved organizational record.
Messages, tool calls, artifacts, and diffs
Documents, code, configs, and generated files
Resources available to agents and human teammates
Source, proposed change, reviewer, and decision
BOUNDARY
Sessions are isolated while the Agent Drive persists across sessions and sandbox restarts
Buda keeps agent work visible and persistent; review decides which outputs become shared knowledge.
| 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 |
| Approved record | Source, proposed change, reviewer, and decision | Canonical knowledge accepted by the organization |
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 turn an output into an approved organizational record.
The trace of one isolated conversation
Persistent working context for one agent
Reusable team context with an explicit owner
Canonical knowledge accepted by the organization
EVIDENCE
A persistent or shared file remains working context until an owner promotes it through review
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 an owner promotes it through review
| 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 |
| Approved record | Source, proposed change, reviewer, and decision | Canonical knowledge accepted by the organization |
ACCEPTANCE
Buda keeps agent work visible and persistent; review decides which outputs become shared knowledge.
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 an owner promotes it through review
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, proposed change, reviewer, and decision before accepting Canonical knowledge accepted by the organization.
FAQ
Knowledge Base for Buda Agent: practical questions
Buda keeps agent work visible and persistent; review decides which outputs become shared knowledge.
Does a file become approved knowledge when Buda saves it to Drive?
No. Drive preserves the file and makes it inspectable. Approval still requires a source, owner, scope, and decision.
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, reviewer, and final decision.
NEXT
Buda keeps agent work visible and persistent; review decides which outputs become shared knowledge.
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 turn an output into an approved organizational record.