Skip to main content
Most of the time you’ll review sessions in the Console. But two commands let you inspect sessions straight from the terminal, useful for quick checks and debugging a session that won’t pass.

​
ironbee status

Show the verdict status of the sessions in a project:
For each session it prints the verdict (pass / fail), the number of checks recorded, the retry count, and, for failures, the list of unresolved issues. Sessions with no verdict yet show as missing, or as monitoring-only when verification is disabled. An assist-mode session that never ran a manual /ironbee-verify cycle also shows as monitoring-only (there was no gate); one that did will carry its verdict.

​
ironbee verdict

Dry-run the verdict checks for a session without changing anything, a read-only version of the gate that runs when the agent stops:
If only one session is active, the session ID is auto-detected. Use this to understand exactly why a session would pass or fail before the agent retries. Add -p, --project-dir <dir> to target a project other than the current directory.
This command used to be ironbee verify [session-id]. ironbee verify now runs a cloud verification job through the IronBee API — see Verification Jobs. The local dry-run lives on unchanged as ironbee verdict.

​
What’s next?

Runtime files

Where verdicts, state, and session data are stored on disk.

Job queue

Inspect and drain the background queue that ships session data.