Verbose mode means your agent logs the full content of every step — not just whether it succeeded, but what it actually processed and produced. It’s the difference between a receipt and a transcript. Use it when you need to understand what happened; disable it when the agent is running stably and you’re comfortable with summary-level logging.
What Changes in Verbose Mode
In standard logging, a step entry might look like: “Step 3 — Tool call: wp_get_post — Status: success.” In verbose mode, that same entry includes the exact parameters sent to the tool, the full response it returned, the agent’s interpretation of that response, and any intermediate reasoning it applied before moving to the next step. You go from a one-line summary to a paragraph of detail.
The tradeoff is storage and readability. Verbose logs are larger and harder to scan. For a high-volume agent that runs hundreds of times a day, verbose logging can generate enormous log files that slow down your database and bury the signal in noise. For a new agent you’re evaluating or a stable agent that just started behaving unexpectedly, verbose mode is exactly what you need.
When to Use Each Mode
Use verbose mode when: you’re deploying a new agent for the first time and want to verify it’s working as intended; you’re debugging a specific failure and need the full content at each step; you’re evaluating whether a prompt change improved the agent’s behavior; or you’re building a training dataset from real agent runs. Use standard logging when: an agent has been running reliably for several weeks; the output quality is consistent; and you’re checking the log for oversight rather than debugging.
What This Means for Educators
Think of verbose mode as your learning tool and standard logging as your operations tool. New agents get verbose logging until you’ve read enough traces to be confident in their behavior. Trusted agents run on standard logging with verbose available as a switch when you need it.
The Simple Rule
New agent: verbose on. Stable agent: verbose off. Something went wrong: verbose on for the next 10 runs, then reassess.