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

# investigate

> Run a multi-agent investigation from a prompt, seed document, issue, or PR.

entire-investigate is an installable [plugin](/cli-reference/plugin.md) for the Entire CLI. It runs a multi-agent investigation: agents take turns appending findings, evidence, and analysis to a shared findings document until quorum is reached.

Install it before running `entire investigate`:

```bash theme={null}
entire plugin install investigate
```

Running `entire investigate` without the plugin offers to install it, and reports `the entire-investigate plugin is not installed` in a non-interactive run.

```bash theme={null}
entire investigate [SEED_DOC] [flags]
entire investigate SUBCOMMAND
```

`entire investigate` is experimental while the workflow is still being refined. Its flags are unchanged from when the command shipped in the CLI itself.

> [!NOTE]
>
> Settings move with the command. Copy any old `investigate` settings object into `.entire/investigate.local.json`; a legacy `investigate` block in `.entire/settings.json` is ignored.

## Inputs

Use one of these inputs:

| Input | Description |
| - | - |
| `SEED_DOC` | Path to a starting findings file |
| `--issue-link URL` | GitHub issue or pull request URL resolved through `gh` |

When neither input is supplied and the multi-agent picker opens, the picker collects an investigation prompt that becomes the topic for the run.

## Flags

| Flag | Description |
| - | - |
| `--agents AGENTS` | Override configured agents with a comma-separated list |
| `--max-turns N` | Per-agent turn budget. Defaults to `2`. |
| `--quorum N` | Approvals needed to terminate. `0` means all agents. |
| `--continue RUN_ID` | Resume an existing run |
| `--edit` | Re-open the investigate config picker |
| `--findings` | Browse local investigation manifests |
| `--allow-untrusted-seed` | Required for non-interactive `--issue-link` investigations because the seed is attacker-influenced GitHub content |

## Subcommands

| Subcommand | Description |
| - | - |
| `show RUN_ID` | Print a saved investigation's summary and findings |
| `fix RUN_ID` | Launch a coding agent with the run's findings as grounded context |
| `clean RUN_ID` | Delete a saved investigation. Add `--force` to skip the confirmation prompt. |
| `clean --all` | Delete all saved investigation artifacts |

## Examples

```bash theme={null}
entire investigate leaderboard-route-investigation.md --max-turns 1
entire investigate --findings
entire investigate show RUN_ID
entire investigate fix RUN_ID
entire investigate clean RUN_ID
```

## Continue With

> **[Investigate Why Code Exists](/learn/investigate-why-code-exists.md)**
>
> Walk through a complete provenance investigation.

> **[plugin](/cli-reference/plugin.md)**
>
> Install, list, and upgrade Entire plugins.
