Example · ships with Charlie
Bash
Lets Charlie run commands on your computer. Anything new gets a pop-up first, and you can tell it to remember your answer.
What's in the folder
bash/
├── manifest.json
├── handlers/
│ ├── run.js runs a command
│ ├── rules.js lists what you've allowed or denied
│ └── lib/rules.js shared code for both
└── build/
├── ApprovalModal.js the "Run this command?" pop-up
└── Settings.js its settings panel
The manifest
{
"name": "bash",
"description": "Run shell commands on the operator's machine. Every command n...",
"version": "0.1.0",
"developer": {
"name": "Andy Dale",
"contact": "(hidden on this page)"
},
"tier": "core",
"settings": {
"component": "./build/Settings.js"
},
"instructions": "Real commands, on the operator's real machine. bash__run exec...",
"tools": [
{
"name": "rules",
"description": "List every command/program with a remembered allow or deny de...",
"input_schema": { ... },
"handler": "./handlers/rules.js",
"delivery": "narrated"
},
{ "name": "run" }
]
}| Line | What it plugs into |
|---|---|
"tools" | 1 · Tools. Two tools: run and rules. Charlie sees them as bash__run and bash__rules. |
"instructions" | 3 · Instructions. Reminds Charlie these are real commands on your real machine, and that they don't get around any other rule. |
"settings" | 4 · Settings. Its own panel. |
"ui": { "surface": "modal" } | 5 · Surfaces. On the run tool, so the approval pop-up appears when Charlie runs something. |
Ideas to borrow
- A pop-up on a tool is an easy way to put a person in the loop before something real happens.
- Give Charlie a way to check before it acts.
bash__ruleslets it see what will prompt you instead of guessing from memory. - Use instructions to explain the stakes, not just the steps. Bash's tell Charlie why its commands are different from a sandbox.