···98989999By default (i.e. if no reporter is specified), Vitest will display summary of running tests and their status at the bottom. Once a suite passes, its status will be reported on top of the summary.
100100101101+::: tip
102102+When Vitest detects it is running inside an AI coding agent, the [`agent`](#agent-reporter) reporter is used instead to reduce output and minimize token usage. You can override this by explicitly configuring the [`reporters`](/config/reporters) option.
103103+:::
104104+101105You can disable the summary by configuring the reporter:
102106103107:::code-group
···636640 },
637641})
638642```
643643+644644+### Agent Reporter
645645+646646+Outputs a minimal report optimized for AI coding assistants and LLM-based workflows. Only failed tests and their error messages are displayed. Console logs from passing tests and the summary section are suppressed to reduce token usage.
647647+648648+This reporter is automatically enabled when no `reporters` option is configured and Vitest detects it is running inside an AI coding agent. If you configure custom reporters, you can explicitly add `agent`:
649649+650650+:::code-group
651651+```bash [CLI]
652652+npx vitest --reporter=agent
653653+```
654654+655655+```ts [vitest.config.ts]
656656+export default defineConfig({
657657+ test: {
658658+ reporters: ['agent']
659659+ },
660660+})
661661+```
662662+:::
639663640664### Blob Reporter
641665
···606606607607The cleanest approach is using [Test Projects](/guide/projects):
608608609609-610609```ts [vitest.config.ts]
611610import { env } from 'node:process'
612611import { defineConfig } from 'vitest/config'
···662661 },
663662})
664663```
665665-666664667665Follow the [official guide to create a Playwright Workspace](https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests?tabs=playwrightcli&pivots=playwright-test-runner#create-a-workspace).
668666