# Testing an agent

The Test tab runs a real turn against the agent you're building — same engine, same persona — so you can see how it answers (and which tools it reaches for) before you ship it.

## Run a test turn

Open the Test tab in the agent editor, type a prompt (it starts with a sensible default like “In one sentence, who are you and what do you do?”), and click Save & run.

Running first saves the agent — so the turn uses its very latest persona, instructions, and wiring — then sends a one-off message to it. The response streams into the panel below.

## Tools called

Above the output, Foxora lists the tools the agent invoked during the turn, in order. It’s the quickest way to confirm the agent is reaching for the right capabilities — and not, say, ignoring a skill you attached.

## Writes and commands stay gated

A test run executes in Ask mode: anything that writes a file or runs a command is still gated, so a test can’t quietly change your project. It’s a safe dry run of the agent’s behavior.

> When a test failsIf the run errors, the editor shows a clear failure callout with the reason — an unreachable engine, an empty model response, or a tool error. Fix the cause (often a missing connection or an empty name) and run again. Use Clear to reset the panel.

> Test, then shipA green test isn’t a guarantee, but it catches the obvious problems early. Once it answers the way you want, save and put it to work — or add it to a crew.