# Track Progress and Findings

Once you've started an audit, Aikido takes you to the assessment detail page. From there, you can watch progress and read findings as they land.

## Tracking progress

Open an assessment from the **AI Code Audit** home to see its detail page. The page has an **Overview** tab, an **Issues** tab (with a badge when there are open issues), and a **Threat Model** tab when one's available — see [Threat Model](/pentests/coverage-and-findings/threat-model.md) for how to read it.

While the audit is running, the **Overview** tab shows the current status and the header shows elapsed time and an estimated time remaining.

The **AI Code Audit Information** block lists who requested the audit and when it started. **Code & documentation** lists the repositories linked to the audit.

### Audit statuses

The status on the **Overview** tab reflects where the audit is in its lifecycle:

* **Pending** — the audit is queued and waiting for agent capacity.
* **Running** — agents are actively reasoning over your code. Findings can land in the **Issues** tab while this status is showing.
* **Completed** — the audit finished. All findings are in the **Issues** tab and in your global feed.
* **Failed** — the audit couldn't finish. Open the assessment for details, or reach out via Intercom chat.
* **Cancelled** — the audit was stopped before it completed.

## Reading findings

Findings appear in the **Issues** tab on the assessment and in your global issue feed alongside other Aikido findings. They follow the standard Aikido finding lifecycle — see [Manage Findings](/getting-started/core-functionalities.md) for ignore, snooze, severity, and task-tracker integrations.

Click **Attack Analysis** on any finding to open the standard Aikido finding modal, with sections for summary, description, risk, root cause, remediation, and more.

The reproduction block is titled **Evidence** rather than **Reproduction Steps**. The content is code- and reasoning-based — it points at the specific files and logic that make the issue exploitable, rather than walking through a live HTTP exploit. Treat it as the developer-facing justification for the finding.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.aikido.dev/ai-code-audit/track-progress-and-findings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.