mirror of
https://github.com/block/buzz.git
synced 2026-10-28 21:11:48 +00:00
docs(vision): match the agent's unsafe claim to the policy
buzz-dev-mcp already used unsafe for Windows job objects, so "Zero unsafe" was untrue. Say what holds: no unsafe beyond audited OS calls. Signed-off-by: Pinky <5f5ab050ec58ae208332edd544ebf705221e24c1b86d82a6ca07038a7a8f6ac9@buzz.block.builderlab.xyz>
This commit is contained in:
@@ -54,7 +54,7 @@ Two pipes. Two protocols. Each session gets its own MCP server instances — ful
|
||||
|
||||
- **Minimal.** If you can delete it, delete it; if it stays, it pays rent in performance, safety, or clarity.
|
||||
|
||||
- **Hardened.** Zero unsafe. Zero panics. Bounded process lifetime, bounded output sizes, bounded history. Process-group kill on every exit path. File edits resolve against the working directory. The shell runs at the operator's trust level, like bash itself. History validity is maintained on every cancellation path. The system degrades gracefully, with bounded failure modes.
|
||||
- **Hardened.** No unsafe beyond audited OS calls. Zero panics. Bounded process lifetime, bounded output sizes, bounded history. Process-group kill on every exit path. File edits resolve against the working directory. The shell runs at the operator's trust level, like bash itself. History validity is maintained on every cancellation path. The system degrades gracefully, with bounded failure modes.
|
||||
|
||||
- **Protocol-native.** ACP is the only interface to the agent. MCP is the only interface to the tools. No runtime coupling. No shared state. No custom wire formats.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user