Skip to main content

Using Claude Code, Cursor, or another coding agent? Paste this into your prompt to run cross-browser and real-device tests, debug sessions, and wire up CI on the TestMu AI cloud:
Every Kane CLI run ends with a result_code in the run_end event. This page lists every code, explains what triggered it, and tells you what to do next.

How to Read Result Codes

Result codes follow HTTP-style groupings: The run_end event includes both result_code (numeric) and reason_code (descriptive string):

1xx — Success

100 COMPLETE


2xx — Cancelled

200 USER_CANCELLED


3xx — Stuck

The agent ran into a dead end. These are not crashes - the agent recognized it could not make further progress.

310 MAX_STEPS

320 DAG_CYCLE

330 AP_STUCK


4xx — Agent Error

An internal agent component failed. These typically indicate a transient issue or a problem with the session state.

410 AP_NO_ACTION

420 REASONING_FAILURE

430 CLEAN_START_INVALID

440 CHILD_FAILED


5xx — Infra Error

Platform or infrastructure failures. These are independent of the objective itself.

510 SCREENSHOT_FAILED

520 BROWSER_CRASHED

530 TIMEOUT

540 EVENT_DISPATCH

550 CONTROLLER_AUTH

Verify with kane-cli whoami, then retry the run.

560 CREDITS_EXHAUSTED


6xx — Blocker

An external obstacle on the target website prevented the agent from completing the objective. These are not agent bugs - they require changes to the environment or objective.

610 CAPTCHA

620 PAYWALL

640 BLOCKED

650 ERROR_PAGE

660 AUTH_NO_CREDENTIALS


7xx — Assertion Error

The agent completed its actions but one or more assertions or checkpoints did not pass.

710 FINAL_VERIFICATION

720 CHECKPOINT_FAILED

730 NO_BRANCH_MATCHED


Quick Lookup Table


Handling Errors in Agent Mode

When consuming Kane CLI output programmatically, use result_code ranges to determine your next action: