Busabase CLI
Busabase CLI backs up a shared workspace; restoring the archive requires an empty destination prepared by the user.
- 714 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The CLI can submit and merge changes, upload files and restore data with account permissions.
- The open local server allows workspace access without signing in.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/busabase-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The CLI can submit and merge changes, upload files and restore data with account permissions.
- The open local server allows workspace access without signing in.
This is third-party code. Review the repository files before installing.
What it does
Busabase CLI accesses workspace records, documents and files through a local or hosted server’s API. Agents search materials, upload files and submit change requests. Workspace policy determines whether a request applies immediately or waits for human review. The server retains each edit’s author and history. Data persists between conversations so another agent can find saved material and continue working on it. Users select the server and access profile before querying the database; client settings determine the destination.
Who it is for. Teams using shared project records to pass work between several agent sessions.
Good fit when
- A new agent continues from material left by an earlier session.
- A schema change is submitted as a separate request.
- Records are exported as JSON for a subsequent workflow.
- A workspace backup is saved before a consequential edit.
Not a fit when
- You need automatic publication outside workspace policy.
- A local server would be exposed to an untrusted network without protection.
- The client must work without a selected server or workspace.
Example request
Connect to my test Busabase, inspect the space and records, then prepare a change request without choosing a merge policy.Limitations
The CLI defaults to the hosted server; specify the local address explicitly before sending data if you intend to work locally. The local server provides one space without mandatory sign-in, so restrict network access separately. A change request can be applied immediately when permissions allow it: the request format does not ensure manual review of every write. Archive restoration targets an empty space; prepare a separate destination before transferring data.
How to disable. Exit the CLI and remove unneeded access profiles. Stop a local server separately; changes already applied remain in the database.
FAQ
Does the client need a server?
Yes. Connect an existing server or use `busabase`, which bundles the client and server command.
How do I start a local trial?
Run `npx -y busabase@latest server`. The example opens a demo at `http://localhost:15419/dashboard/local`.
How do I get agent instructions?
`busabase-cli skill` prints the manual. Use `busabase-cli skill setup` for onboarding or `busabase-cli skill install` to write the skill into an agent’s directory. Choose the action for your setup stage.
Can I use several accounts?
Yes. Select an account with `--profile` or `BUSABASE_PROFILE` to read its credentials without switching the shared active profile. Match the profile to the server before the first request.
How do I make a backup?
Run `busabase-cli backup -o ./space.bbdump` for the selected space and protect the output file.
Discussion
No questions or reviews yet.
Related
CLI toolsThe SQL client combines terminal database browsing with batch queries for agents using named connections and JSON results.
A lightweight database workspace with an MCP server: the agent reads the schema, runs queries and explores data in PostgreSQL, MySQL and more
The CLI imports CSV and JSON into SQLite, runs SQL and reshapes tables for agent-assisted local data preparation.
dblab is a terminal SQL client with saved connection profiles and optional password storage in the operating system keyring.
Search and page collection share an agent workflow, with sample data visible before proposed scraper fixes are applied.
1C Database Queries for Agents
1c-llm-requests
A tiny 1C extension with an HTTP service plus a skill, so an agent writes 1C queries itself and gets database data as TSV
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Busabase CLI (this card) | no | 714 | ||
| Basic Memory | no | not required | 4,509 | stores knowledge in local Markdown files with a link graph and semantic search |
| Nubase CLI | no | 620 | A CLI connects Claude Code and Codex to Nubase, installing skills and MCP tools for databases, functions and app deployment. | |
| Oxynote MCP | yes | OAuth | 515 | A technical wiki’s MCP lets agents read and edit documents while protected pages route changes through reviewable drafts. |
README in short
Output supports text, tables and JSON. Change requests can be reviewed, closed or applied separately, subject to workspace permissions.