> For the complete documentation index, see [llms.txt](https://testbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testbox.ortusbooks.com/getting-started/running-tests/ai-agent-reporter.md).

# AI Agent Reporter

Return compact TestBox results for AI agents and automation.

The `AgentReporter` returns a compact, minified JSON summary designed for AI agents and automation. It includes run totals and failed or errored specs, without the full result details produced by the standard JSON reporter.

This is a **reporter**, not a separate test runner. Use it with a runner that supports the `agent` reporter:

{% tabs %}
{% tab title="BoxLang" %}
{% code title="BoxLang CLI runner" %}

```bash
./testbox/run --reporter=agent
```

{% endcode %}
{% endtab %}

{% tab title="CFML" %}
{% code title="CFML runner URL" %}

```
runner.cfm?reporter=agent&directory=tests.specs
```

{% endcode %}
{% endtab %}
{% endtabs %}

The JSON includes an `ok` status, run totals, a `failures` array, and a `truncated` count. See [AgentReporter options and output](/digging-deeper/reporters.md) for the complete schema and configuration options.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://testbox.ortusbooks.com/getting-started/running-tests/ai-agent-reporter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.