ironbee session view
Show what IronBee knows about a session right now:- the one-line state: edits waiting, the running cycle with each platform’s progress, the verdict, or why the gate blocked
- the running or last cycle: the project checks, every verification tool call tagged with its platform, and in enforce mode what the gate still wants from each platform
- the verdict: issues, checks, fixes, and a warning when the code changed after it
- the evidence: captured screenshots and recordings, and the Console link to the run
- a scenario run’s steps and result
verification.changes.source is set to. With git, an edit made through a shell command isn’t shown as waiting, although the gate still asks for its verification.
Two helper commands serve the in-app view, and work in any terminal:
ironbee session thumbnail <file>draws a PNG screenshot as terminal cells, a low-resolution preview.--columnssets the width (default72) and--max-rowsthe height (default30).ironbee session open <target>opens a screenshot or recording in its viewer, or anhttp(s)link in the browser. It opens nothing else.
ironbee status
Show the verdict status of the sessions in a project:pass, fail or not_applicable), the number of checks recorded, for failures the list of unresolved issues, and the verdict’s summary when it has one. A verdict file that can’t be read shows as invalid JSON. 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:summary: present, with its length, or absent. A summary that isn’t a string, or is longer than 10,000 characters, fails the check, and the result is ✗ BLOCKED, because the verdict has schema errors. 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.