Use one approval and evidence model across the host tools your team already runs.

Use project-scoped Codex MCP and hook config to bring Bash-side actions under the same approval and receipt model.

• Writes `.codex/config.toml` with the MandateOS MCP entry
• Adds Bash PreToolUse guardrails in `.codex/hooks.json`
• Blocks conservatively when approval is still required

Bring Cursor sessions under the same approval, tool-scope, and receipt model as the rest of your agent operations.

• Configures local MCP entries for the repo
• Writes guarded shell and MCP hooks for the workspace
• Keeps the runtime path aligned with the rest of the trust layer

Use the same operating model in Claude Code so teams do not have to reinvent policy for each shell.

• Adds the local `mandateos` MCP entry
• Creates workspace-scoped settings for the selected repo
• Preserves a consistent approval and receipt path

Designed for OpenClaw’s flexible host surface so teams can keep explicit tool boundaries, approvals, and receipts around local agent power.

• Installs the OpenClaw bridge and plugin bundle
• Creates a guarded local profile for the selected workspace
• Uses the same mandate, approval, and evidence model as the other hosts

Repository-side actions are a natural next extension of the same policy and approval model.

• Designed to reuse the same mandate logic
• Lets teams extend review and evidence past local shell actions
• Explicitly not presented as fully available today