> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/ai-code-analysis/ai-code-audit-overview/track-progress-and-findings.md). # Track Progress and Findings Once you've started an analysis, 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 Analysis** 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. [Data Exposure Audits](/ai-code-analysis/what-is-dspm/data-exposure-audit.md) don't include a Threat Model tab. While the analysis is running, the **Overview** tab shows the current status and the header shows elapsed time and an estimated time remaining. The AI **Code Analysis Information** block lists who requested the analysis and when it started. **Code & documentation** lists the repositories linked to the analysis. ### Analysis statuses The status on the **Overview** tab reflects where the analysis is in its lifecycle: * **Pending:** The analysis 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 analysis finished. All findings are in the **Issues** tab and in your global feed. * **Failed:** The analysis couldn't finish. Open the assessment for details, or reach out via Intercom chat. * **Cancelled:** The analysis 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. Once you've pushed a fix, click **Re-test** on the finding to have Aikido re-check it against your latest code. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.aikido.dev/ai-code-analysis/ai-code-audit-overview/track-progress-and-findings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.