竹子AI代理

Install

For a published package:

cargo install bamboo-agent --locked
bamboo --help

For the source described here, use Rust 1.95+ and run from this checkout:

node scripts/frontend-package.cjs stage
cargo install --path . --locked

The staging command verifies the committed frontend package. Normal builds require the locked Lotus Next artifact; they fail if it is missing or invalid. They do not silently download a moving latest. The exact identity is in frontend-package-lock.json.

For an intentionally API-only source build:

BAMBOO_FRONTEND_BUILD_MODE=api-only cargo build --bin bamboo

That POSIX shell assignment needs PowerShell's $env:BAMBOO_FRONTEND_BUILD_MODE = "api-only" on Windows. API-only builds have no compiled-in browser UI. See the deployment guide and frontend staging script for explicit external or local frontend paths.

Configure and open the local interface

bamboo init
bamboo serve

init interactively configures your provider and stores its key encrypted at rest under the Bamboo data directory (normally ~/.bamboo/). config.json holds configuration metadata rather than the encrypted provider key. Use a model available to your provider/account. With the frontend included, open http://127.0.0.1:9562. In another terminal:

bamboo health
bamboo doctor

The health endpoint is GET /api/v1/health; bamboo health requires a reachable server. doctor checks configuration and provider credentials, failing on those errors; its server-reachability probe is informational, so an absent server alone does not make doctor fail. serve --port, --bind, --data-dir, --static-dir, and --workers override configuration; run bamboo serve --help for the full list.

See the browser interface prepare project context

Static image · Recording details

Real source-checkout recording with a disposable workspace and a real Bamboo backend. It shows project creation and selection, with no provider call or claimed agent task completion. It is not a recording of the published desktop package.

Use it as a Rust SDK (in-process)

For SDK embedding, bamboo_sdk::agent::Agent provides run, run_stream, and execute over the same engine. Defaults require a configured provider; they do not supply credentials. A complete built-in defaults assembly also supports run_with_skills(session, SdkSkillInput) and its cancellation variant. These async entries validate current selections and the portable submission hook before appending the prepared User. They require a new empty Session or the exact durable Session; save and reload staged edits before submitting. The existing String entries keep their synchronous append and error order. Explicit tool policies, custom executors and from_runtime do not supply this finite Skills host and reject typed input before append. Low-level execute retains its custom-request contract. See first-run CLI / HTTP / SDK examples, API reference, and the published crate's rustdoc.

Source checkout or published package?

This README describes the development source checkout, with the original product audit at 025641317c5703226052a4b94a52d1844615c352 and this documentation refresh based on dev revision 10ca51ccdf1f253ff6ec1e78f21b4c74835e1582. It is not a claim that every command or capability is in the latest crates.io release. Check the installed binary's bamboo --help and the release/source audit when comparing versions. Source manifests deliberately use 0.0.0; publishing stamps the release version separately. The recording below retains its separate, older source provenance.