Files
LLeMbas-CLI/harness/tools/bash.json
T
HomerandClaude Fable 5.1 2183040db8 Harness spec 2.0.0: background work is a job — commands and subagents alike, seen and steered
One registry per process, every job owned by a session: bash's background commands (and a command
still running at its timeout, which now goes to the background instead of being killed) and
subagents started with task background: true. job_list, job_output, job_stop (the former
bash_list, bash_output, bash_kill) and the new job_send and report; a finished job wakes the owning
session in every front end with its marked note. The TUI counts jobs, lists them (/jobs), opens a
command's output, enters a subagent and messages it, moves a command to the background (ctrl+b)
and asks before quitting with jobs running. The link gains the jobs capability. Subagents get a
session row of their own, the spec's preamble and agent texts, and their errors reach the report.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-20 16:17:00 +00:00

54 lines
2.5 KiB
JSON

{
"name": "bash",
"scope": "cli",
"risk": "execute",
"exclusive": false,
"block": "shell",
"purpose": "description",
"aliases": {
"cli": [],
"llembas": [
"shell_run"
]
},
"argument_aliases": {
"workdir": "cwd"
},
"description": "Run a shell command (bash) and return its combined output and exit status.\n\n- Each call is a fresh shell: `cd` and variables do not carry over. Use `cwd` instead of `cd`.\n- Use the dedicated tools for files: read, not cat; edit/write, not sed or heredocs; grep and glob, not find.\n- Quote paths that contain spaces.\n- A command still running when `timeout` passes (default {{timeout}}, up to {{timeout_max}}) is not killed: it goes on in the background as a job, and the call returns what it had printed with the job id.{{background}}\n- Git: do not commit, amend, push or change git config unless asked. Before a commit, check `git status` and `git diff`, stage files by name, never commit secrets.",
"parameters": {
"type": "object",
"properties": {
"command": {
"type": "string",
"description": "The command line"
},
"description": {
"description": "One short sentence for the user: what this command is for — what you want to find out or get done. Shown when they are asked to allow it, and on the tool line.",
"type": "string"
},
"cwd": {
"description": "Directory to run in (default: working directory)",
"type": "string"
},
"timeout": {
"description": "Milliseconds to wait for the command before it goes on in the background",
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 600000
},
"background": {
"description": "Run in the background from the start and return a job id at once",
"type": "boolean"
}
},
"required": [
"command"
]
},
"variables": {
"timeout": "how long a command may run before it goes on in the background when the call names no timeout, in words (\"2 minutes\")",
"timeout_max": "the longest timeout a call may ask for, in words (\"10 minutes\")",
"background": "where commands may run in the background: \" For a server, a watcher or anything long, set `background: true`: it returns at once with a job id. Read a job's output with job_output, list jobs with job_list, stop one with job_stop; you are told when one ends.\" — otherwise empty, and the `background` parameter is not sent"
}
}