> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bugster.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Destructive Agent Testing

> Use AI agents to break your application and find bugs in changed pages

Run AI-powered destructive agents like `form_destroyer` and `ui_crasher` to find potential bugs in your recent code changes by attempting to break your application.

## Basic Usage

```bash theme={null}
# Run destructive agents on all changed pages
bugster destructive

# Run in headless mode for faster execution
bugster destructive --headless

# Limit number of agents (default: 5)
bugster destructive --limit 10
```

## Common Scenarios

### After Feature Development

You just built a new checkout flow and want to stress-test it:

```bash theme={null}
# Run destructive testing with moderate scope
bugster destructive --limit 8

# Run multiple agents in parallel for speed
bugster destructive --max-concurrent 5
```

### Pre-Release Testing

Before deploying, run comprehensive destructive testing:

```bash theme={null}
# Extended testing session
bugster destructive --limit 15 --verbose

# Export results for review
bugster destructive --output destructive-results.json
```

## Key Options

**--limit** `integer` (default: 5)

Maximum number of destructive agents to run.

**--max-concurrent** `integer` (default: 3)

Number of agents running simultaneously for faster execution.

**--headless** `boolean` (default: false)

Run agents without browser UI for faster, unattended testing.

**--output** `string`

Save detailed results to JSON file for analysis or CI integration.

> [!WARNING]
>
> Destructive agents can generate unusual data and trigger error states. Always run in development or staging environments, never production.

## Next Steps

> [card] [Local Development](https://docs.bugster.dev/guides/local-development.md)
>
> Integrate destructive testing into your daily development workflow

> [card] [CLI Commands](https://docs.bugster.dev/commands/destructive-agent.md)
>
> Explore all destructive agent command options and flags

> [!NOTE]
>
> Destructive testing is most effective when combined with regular testing. Use it to discover edge cases that traditional tests might miss.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.