Skip to main content

​
Debugging

When a run stalls, fails repeatedly, or produces unexpected results, Gump gives you several tools to understand what happened.

​
The terminal display

During a run, Gump shows progress by turn:
Each line shows the turn number, a classified label (coding, execution, exploration, planning, reasoning, reviewing, writing, mixed), action counts, tokens, and duration. Labels are deterministic heuristics — no LLM involved.

​
Verbose mode

In verbose mode, each turn expands to show individual actions. More than 20 actions per turn shows the first 10 + ... +N more.

​
Error messages

Gump’s error messages are contextual. At the end of a failed run:

​
Common issues

The agent runs out of turns — The max_turns guard killed it. Increase the limit or simplify the task. The gate keeps failing on test — Check gump report --detail for the test stderr. If the error is in the test infrastructure, the agent can’t fix it. The cost is higher than expected — Escalations are the main cost driver. Consider starting with a slightly more capable agent. The agent writes files it shouldn’t — The no_write guard catches this for split/validate steps. For code steps, use untouched: "glob" in the gate.