Bamboo
Local Rust agent harness with sessions, tools, skills, MCP and HTTP/SSE/WebSocket runtime.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.
crates:russh 0.64.1russh: Agent server never calls `Agent::confirm`, so keys added with the confirm constraint (`ssh-add -c`) sign without confirmation (GHSA-vp5q-ff62-jwqv, high, fixed in 0.65)
Linux x86_64
You need first
- Runtimes:
Rust 1.95+ - Keys or accounts: provider key
These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:
mkdir -p "$HOME/work" && cd "$HOME/work"cargo install bamboo-agent --locked (built from crates.io, ~18 min, installed bamboo to ~/.cargo/bin)
cargo install bamboo-agent --locked
Verified in pickfit: the commands exactly as its sandbox ran them
For the record only: they name the sandbox's home, /home/sbx.
cargo install bamboo-agent --locked 2>&1export PATH="$HOME/.cargo/bin:$PATH" && bamboo --helpexport PATH="$HOME/.cargo/bin:$PATH" && cd /home/sbx/work && bamboo -p "ping" --echoCheck that it works
export PATH="$HOME/.cargo/bin:$PATH" && bamboo --helpThe output should contain “QUICK RUN (headless server):”.
First thing to try
export PATH="$HOME/.cargo/bin:$PATH" && cd "$HOME"/work && bamboo -p "ping" --echoWhat it does
- Serve local browser UI and HTTP APITested
- Run agent prompts on a workspace from terminalNot tested
- Resume persistent agent sessionsNot tested
- Connect MCP servers, skills and scheduled promptsNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 1 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- Run a prompt against a workspace and continue the session later
- Embed assistant via HTTP, WebSocket/SSE events or Rust SDK
- Carry facts across turns with session notes and durable memory
- Connect MCP servers, skills, plugins and scheduled prompts
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its service answers requests
- Replayed from scratch
- Works offline
- Checked on 16 Nov 2026
- Version 2026.11.23
Differences the test machine hit
- README: Standalone Bamboo: cargo install bamboo-agent --locked; bamboo --help
In the test: ~/.cargo/bin must be on PATH (the box's PATH did not include it); the install itself worked with the box's Rust toolchain and took about 18 minutes. - README: Bodhi desktop app: curl ... install.sh | sh (terminal installer)
In the test: The script installs a different product (Bodhi-AI desktop, a .deb) with sudo apt-get and needs a terminal for the sudo prompt. It cannot run without root, so it was not used; the Bamboo CLI came from cargo. - README: bamboo init (interactive provider setup) then bamboo serve
In the test: bamboo serve starts without init. Headless runs need a provider key, which was not available, so bamboo -p failed with HTTP 500 and doctor reported no config.json and no anthropic API key. - README: bamboo -p "Summarize the README in this workspace." --workspace /path/to/project
In the test: Needs a configured model provider API key; without it the run fails with 'execute rejected: HTTP 500'.