Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ironbee.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Before you start

Make sure you have logged in first: 
ironbee login
This connects the CLI to your IronBee account. If you haven’t done this yet, see the Quick Start.

​
Run the installer

From your project root: 
ironbee install
IronBee auto-detects your AI client. To specify it explicitly: 
ironbee install --client claude   # Claude Code
ironbee install --client cursor   # Cursor

​
What gets installed

File / SettingDescription
Hook configurationTells the client to call IronBee when the agent finishes a task
Verification skillInstructions the agent follows during verification
Verification ruleEnforces the verification gate
browser-devtools MCP serverBrowser mode — bdt_ prefix tools for navigation, screenshots, console
node-devtools MCP serverNode mode — ndt_ prefix tools (installed but inactive until you opt in)
backend-devtools MCP serverBackend protocol mode — bedt_ prefix tools for HTTP/gRPC/GraphQL/WebSocket (installed but inactive until you opt in)
PermissionsGrants the agent access to all devtools tools

​
Cursor: additional activation

After running ironbee install in a Cursor project:
  1. Restart Cursor to load the new hooks and MCP config
  2. Go to Settings → Tools & MCP and confirm all three of browser-devtools, node-devtools, and backend-devtools are listed as enabled
  3. If a server shows as enabled but tools are unavailable, toggle it off and back on
This is a known Cursor limitation — MCP servers added via mcp.json sometimes need manual activation.

​
Enable Node.js runtime verification

By default, only the browser cycle is active. To also require Node.js V8 inspector verification for backend file changes: 
ironbee node enable
This writes a minimal { "node": {} } block to your project config. Code defaults (e.g. server/**, pages/api/**, **/server.{ts,js,mjs,cjs}) apply at runtime — nothing is materialized into the file. To disable: 
ironbee node disable

​
Enable backend protocol verification

For any backend runtime (Node, Java, Python, Go, Rust, and more), you can require the agent to exercise real HTTP, gRPC, GraphQL, or WebSocket calls before completing: 
ironbee backend enable
This writes a minimal { "backend": {} } block to your project config. Code defaults covering server/**, api/**, routes/**, controllers/**, handlers/**, and services/** apply at runtime. To disable: 
ironbee backend disable

​
Disable the browser cycle

For backend-only projects where browser verification is not appropriate: 
ironbee browser disable
To re-enable: 
ironbee browser enable

​
Monitoring-only mode (no enforcement)

If you want to collect session data without requiring the agent to verify: 
ironbee disable-verification
In this mode:
  • The enforcement hook, verification skill, and MCP servers are not installed
  • Session lifecycle events, tool calls, and timing still flow to the IronBee Collector
  • The agent never sees a verify gate
To re-enable enforcement: 
ironbee enable-verification
Restart your editor or agent session after toggling — the change takes effect on the next session.

​
Check status

To see the verdict status of active sessions in a project: 
ironbee status

​
Remove IronBee from a project

ironbee uninstall
This removes all hooks, skills, rules, and MCP server entries IronBee added.

​
Next step

Configuration

Customize verify patterns, retry limits, and devtools settings.