Skip to main content
A verification is a complete testing cycle the agent runs to prove that its code changes work. Before any task can complete, every affected code path must be exercised with real tools. Verifications are accessed through the Session Timeline and they appear as labeled intervals (Verification 1, Verification 2, …) nested inside activity bars. Click a verification interval to open the Verification Detail panel.

​
Verification types

IronBee supports three cycle types that can run in parallel:

​
Browser cycle

The agent uses browser devtools to verify frontend and full-stack changes:
  • Navigates to affected pages
  • Takes screenshots at key states
  • Checks the browser console for errors
  • Tests user interactions (clicks, forms, navigation)
  • Records a browser session video
  • Submits a verdict with evidence
The browser cycle is active by default for most code file types. Disable it with ironbee browser disable.

​
Node cycle

The agent connects to a running Node.js process to verify backend changes via V8 inspector:
  • Connects to the Node inspector
  • Sets tracepoints or logpoints at changed code paths
  • Exercises those paths via API calls or UI interactions
  • Reads back execution snapshots or runtime logs
  • Submits verdict with backend evidence
The Node cycle is opt-in and enable it with ironbee node enable.

​
Backend cycle

The agent drives real HTTP, gRPC, GraphQL, or WebSocket requests against a running backend service and verifies the responses. Works for any backend runtime (Node, Java, Python, Go, Rust, and more). Evidence is collected across three domains: The backend cycle is opt-in and enable it with ironbee backend enable.

​
Verification status

​
Retry behavior

If a verification fails, the agent must fix the issues and re-verify. By default, it gets 3 attempts (maxRetries). After the limit is reached, the session can complete but must report unresolved issues. Each retry creates a new verification cycle, you can see the full history in the timeline.