Persistent Memory
A per-project knowledge base that captures and reuses context across scans. Each time AuditAgent scans the project, the memory grows with what it learned about the codebase. Subsequent scans build on that context instead of starting from scratch, which reduces false positives and surfaces more meaningful findings.
Persistent Memory is available on any paid plan. The number of project memories you can hold at one time depends on the plan. See Subscription Plans for the per-plan breakdown.
What memory captures
Memory accumulates five kinds of context as you scan:
- Architectural summary. A markdown overview of components, dependencies, and assumptions.
- Invariants. Properties of your contracts that should always hold true.
- Hypotheses. Threat models and working theories surfaced during analysis.
- Contradictions. Mismatches AuditAgent detects between your documentation and your code.
- Excluded findings. Issues you flagged as not relevant, so they stop showing up in future scans.
You can also add custom instructions (up to 10,000 characters) to steer future scans toward what matters most for your project.
Pricing
| Item | Cost |
|---|---|
| Memory initialization | 500 credits ($5.00). Flat fee, regardless of project size. |
| Subsequent scans with memory | Standard scan pricing. No extra charge. |
Initialization is a one-time setup per project. Once it completes, every future scan of that project uses the memory automatically at the normal scan price.
Plan caps
Each plan caps how many active project memories you can hold at one time. The cap counts every memory in your workspace, including ones still initializing. When you reach the cap, delete an existing memory before starting a new one. Your other memories remain fully usable.
| Plan | Project memory cap |
|---|---|
| Pro | 1 project memory |
| Business | Up to 5 project memories |
| Custom | Custom amount, configurable during onboarding |
Memory status
Each project memory carries one of three statuses.
| Status | Meaning |
|---|---|
| Initializing | Memory is being built from the initial scan. |
| Ready | Memory is active and available for use in scans. |
| Updating | Memory is being updated by an ongoing scan. |
Where memory entries come from
Every item in a project memory is tagged with its source.
| Source | Meaning |
|---|---|
| Scan | Automatically generated by AuditAgent's analysis. |
| User | Manually added or edited by you. |
User-sourced items are preserved during automatic updates. Your manual edits are never overwritten by a scan.