Documentation
Oh My Bee
In DevelopmentTools
Bee ships with a compact built-in tool surface for files, shell execution, workflow state, approvals, and session control.
Section
Current tool groups
| Group | Examples |
|---|---|
| Workspace | `pwd`, `list_files`, `find_files`, `read_file`, `grep_files` |
| Execution | `run_shell`, `run_terminal`, `terminal_session` |
| Workflow | `workflow_bootstrap`, `plan_write`, `todo_write`, `review_write` |
| Session control | `checkpoint`, `rewind`, `workflow_state` |
| Utility | `clipboard`, `image`, `highlight` |
| Editing | `edit_file` with approval-aware staging |
Section
Approval-aware edits
In manual mode, `edit_file` creates a staged approval record before touching the file. That record keeps target metadata, checksums, and a diff preview so the write can be reviewed and replayed safely.
bash
bee -p '@tool edit_file {"path":"src/main.rs","op":"replace","selector":"symbol:main","region":"body","find":"println!(\"old\");","content":"println!(\"new\");"}'
bee approvals listSection
Design principles
- Keep the tool core small and predictable.
- Use workflow commands so operators rarely need raw tool JSON.
- Keep permissions and replay behavior explicit.