Bound and revoke autonomy
Autonomous approval is off by default. A person sets scope and exit conditions only when needed.
Guide verification basis: Holmes-Kit 0.40.0 · 2026-11-05 · Installation target: latest at execution time
Choose a CLI, OS and installation mode to see the matching commands. This page does not inspect or execute on your computer.
AGY CLI ordinary integration is supported. AGY run start is refused in 0.40.0; this orchestration lesson has no executable AGY start procedure. Keep your choice, select a different CLI explicitly, or return to Basics.
Prerequisites, evidence and installation tradeoffs
Before you start
- Your own workspace and connected MCP session after the basics. Define HOLMES_CLI or PowerShell HolmesCli from the installation step in this terminal and verify its file and version.
- Operator-defined work, time, cost and network limits
Inspect autonomy posture and route out-of-scope actions to refusal or official review.
Documented for 0.40.0 · release contracts reviewed 2026-11-04. Native evidence is the historical 0.39.0 run of 2026-11-01. Read-only binding matched for Codex and Claude in an independent macOS workspace. Claude hook events were observed but routing is unverified; Codex hooks were not observed. Native revalidation on 0.40.0 and RED/GREEN acceptance of a small governed change remain incomplete. Windows/Linux instructions have no native acceptance run.
- 1. Separate user folder
- Keeps project dependencies and global npm installation unchanged; separate versioned folder. Manage its path and updates separately; retain the folder while workspaces use it.
- 2. Project local
- Project/team versioning through a lockfile; recommended for the practice project. Changes package.json and lockfile; may introduce npm metadata to a non-Node project.
- 3. Global npm
- Convenient shared installation across projects. Check write permissions and update impact on all projects sharing this installation.
Package location and client settings are separate. Even project-local Codex wiring may change user-level settings.
Step 1 / 4
Inspect current authority first
Decide whether this task needs autonomous approval.
Terminal in your workspace
node "$HOLMES_CLI" autonomy statusTerminal in your workspace
node "$HOLMES_CLI" autonomy statusTerminal in your workspace
node "$HolmesCli" autonomy statusExpected result — inspect your actual output
- The current posture is explicit and an off state is not enabled implicitly.
If the result differs
The session is off but a project default remains enabled.
Inspect the remaining authority in the output and have the operator resolve it through official configuration.
What the agent does / terms
Read autonomy status and distinguish active scope, expiry and project defaults.
- MCP
- The connection through which your AI calls Holmes tools.
- REQ → H-SPEC → A-SPEC → T-SPEC
- Requirement → high-level design → implementation design → test specification. Use actual IDs returned by the tools.
- Hook / binding
- A pre/post execution check / matching this session to the intended project and server.
Step 2 / 4
Define allowed work and stop conditions
Decide the exact directory, time, request count, cost, network and push/publish policy.
Ask your agent
Before autonomous execution, propose the exact root, time, cost and request limits, network policy, recovery point and stop conditions. Do not issue authority yourself; inspect the human approval route supported by the installed version.Expected result — inspect your actual output
- A concrete envelope is ready for human review, with push/publish not allowed by default.
If the result differs
The envelope covers the whole disk or unlimited network use.
Narrow the envelope to the task boundary and leave out-of-scope work for a separate decision.
What the agent does / terms
Propose the envelope in writing; the agent must not issue its own authority.
- MCP
- The connection through which your AI calls Holmes tools.
- REQ → H-SPEC → A-SPEC → T-SPEC
- Requirement → high-level design → implementation design → test specification. Use actual IDs returned by the tools.
- Hook / binding
- A pre/post execution check / matching this session to the intended project and server.
Step 3 / 4
Execute only on supported paths
Personally review autonomy full --scope and --allow-push, --allow-publish, --no-architecture. Reissuing replaces every flag; name every flag to keep.
Terminal in your workspace
node "$HOLMES_CLI" autonomy --helpTerminal in your workspace
node "$HOLMES_CLI" autonomy --helpTerminal in your workspace
node "$HolmesCli" autonomy --helpAsk your agent
Inspect the profile and push/publish flags. For full-autonomy.refused, state that no request was filed; have the operator act directly or reissue the required flags. Do not claim that outside-scope writes or human approval gaps are blocked.Expected result — inspect your actual output
- Inspect both the chosen profile authority and actual enforcement limits.
If the result differs
A flag is missing or the current harness approval route is unverified.
Have the operator review the profile instead of repeating or bypassing the refusal. Revoke the profile before work requiring ordinary human approval.
What the agent does / terms
For recognized execution forms without push/publish flags, full-autonomy.refused files no request and an existing grant does not lift it. The help/dry-run forms pass; a force-push form while push is disabled is the exception. Coverage does not extend to unrecognized execution such as package script bodies. The hook prevents accidents; it is not a verified security boundary. It does not refuse plain writes outside its scope. Under full there is no way to request a human approval for a sealed-contract amendment that requires one; revoke the profile and return to ordinary review before that work.
- MCP
- The connection through which your AI calls Holmes tools.
- REQ → H-SPEC → A-SPEC → T-SPEC
- Requirement → high-level design → implementation design → test specification. Use actual IDs returned by the tools.
- Hook / binding
- A pre/post execution check / matching this session to the intended project and server.
Step 4 / 4
Revoke and verify ended authority
Choose revocation matching the mode used.
Terminal in your workspace
node "$HOLMES_CLI" autonomy offTerminal in your workspace
node "$HOLMES_CLI" autonomy offTerminal in your workspace
node "$HolmesCli" autonomy offTerminal in your workspace
node "$HOLMES_CLI" autonomy statusTerminal in your workspace
node "$HOLMES_CLI" autonomy statusTerminal in your workspace
node "$HolmesCli" autonomy statusFull only · operator replaces the scope with the actual status value
node "$HOLMES_CLI" autonomy full --revoke "<ACTUAL_SCOPE_FROM_STATUS>"Full only · operator replaces the scope with the actual status value
node "$HOLMES_CLI" autonomy full --revoke "<ACTUAL_SCOPE_FROM_STATUS>"Full only · operator replaces the scope with the actual status value
node "$HolmesCli" autonomy full --revoke "<ACTUAL_SCOPE_FROM_STATUS>"Expected result — inspect your actual output
- Remaining project, session and profile authority is explicit in output.
If the result differs
off exits nonzero or a full profile remains.
Read the reason and use the official revocation command for that mode; do not claim one off command ended all authority.
What the agent does / terms
For an ordinary session use autonomy off; for a full profile use the installed --revoke route, then inspect remaining authority with status.
- MCP
- The connection through which your AI calls Holmes tools.
- REQ → H-SPEC → A-SPEC → T-SPEC
- Requirement → high-level design → implementation design → test specification. Use actual IDs returned by the tools.
- Hook / binding
- A pre/post execution check / matching this session to the intended project and server.
Apply to your project
This guide neither issues an autonomy profile nor claims an unattended run. It is a conceptual example of defining task limits and checking the approval route supported by your harness.
Related case ↗Continue with your project
Use Adoption for existing code without specs, or Requirements when specifications already exist. Other workflows require their stated prerequisites.