@burtson-labs/bandit-stealth-cli 1.7.478 → 1.7.480

package/README.md

@@ -295,7 +295,13 @@ Workspace config overrides user config. Secrets belong in the user-level file, n
 
 ### Settings file — hooks, permissions, security guard
 
-Terminal `--auto` mode runs routine work immediately and reviews other actions with the selected provider/model. The reviewer considers the raw user requests in the current session, the proposed action and bounded local metadata. Requested cleanup can proceed without a blanket deletion prompt; uncertain effects or missing authorization still ask. External, system and irreversible actions need explicit authorization. Reviews use no tools, have a 12-second deadline, and their decisions appear in the turn log and `/permissions`. Explicit policy rules and security guards remain in force. Model review is fallible; `ask` mode remains available when every ungranted action should be reviewed by you.
+Terminal `--auto` mode runs routine work immediately and reviews other actions with the selected provider/model. The reviewer considers the raw user requests in the current session, the proposed action and bounded local metadata. Requested cleanup can proceed without a blanket deletion prompt; uncertain effects or missing authorization still ask. External, system and irreversible actions need explicit authorization. Reviews use no tools, have a 12-second deadline, and their decisions appear in the turn log and `/permissions`. Explicit policy rules and security guards remain in force. Targeted edits to existing user-owned temporary helper files can qualify as task-related scratch work when the host verifies file ownership and location; this does not authorize arbitrary temporary-file deletion or replacement. Model review is fallible; `ask` mode remains available when every ungranted action should be reviewed by you.
+
+Interactive sessions expose `monitor_job`, `check_monitor`, and `cancel_monitor`. Ask the agent to monitor a particular run and specify its cadence and authorized response, for example: “Check this run every five minutes; if it fails, collect its logs and diagnose it.” The monitor returns immediately and uses a timer to run the approved status command. A terminal result resumes the agent, including when other jobs are still running. Follow-up actions go through the normal permissions gate.
+
+Status commands must be read-only and return one compact JSON object with an exact job ID and status string. `target_id` is checked on every response; `id_path` and `status_path` select nested fields. Success, failure and pending state lists are configurable. Unknown status, a mismatched ID, or a failed status command never counts as success. The default interval is 300 seconds, each probe has a 15-second timeout, and the default overall deadline is 24 hours. Three consecutive probe errors stop observation and report that the remote job status is unknown. A retry creating a new run needs a new monitor.
+
+Use `/tasks` to see monitoring activity and `/cancel <task-id>` to stop it. Keep the CLI session open: monitors are session-local and stop when it closes or the conversation is cleared. Escape during an active agent turn also stops monitors. Automatic continuation preserves a draft in the composer and does not retry a failed model wake-up endlessly. Use existing command authentication or environment references rather than embedding tokens in polling scripts or tool arguments. Diff previews mask secrets for display while preserving the actual file contents.
 
 Separate from `config.json`, a **settings** file controls what the agent is allowed to do. It's read from two places and **merged** — the global file applies to every repo, the workspace file adds project-specific rules on top: