Analysis history
Navigate to History in the sidebar to see all your past analyses.Overview stats
At the top of the page you’ll see three summary metrics:- Total analyses — the total number of analyses you’ve run
- Total tokens — cumulative token usage across all runs
- Last analysis — when your most recent run completed
Tabs: Recent and Saved
Analyses are split into two tabs:- Recent — analyses that expire after your configured retention period
- Saved — analyses you’ve permanently saved, which never expire
Searching and filtering
The filter bar lets you narrow the list by:| Filter | Options |
|---|---|
| Search | Match by repository URL, analysis title, or input type |
| Provider | All, Claude, LM Studio |
| Input type | All, Code Paste, GitHub, File Upload |
| Sort order | Newest first, oldest first, longest duration, provider A–Z |
| Date range | Filter by creation date from/to |
Actions on each analysis
Click any analysis card to open its detail page. From there you can:Resume
Available when an analysis has status Interrupted or In Progress. Resumes from the last completed chunk — you don’t lose work already done. The button shows how many chunks completed out of the total (e.g., Resume (3/8)).
Run Again
Re-runs the analysis with exactly the same configuration, files, provider, and model parameters. Useful when you want to regenerate output after updating your code.
Run Different Analysis
Uses the same files but lets you choose a different goal — Full Analysis, Security Audit, Generate Test Cases, Edge Case Analysis, or User Stories. Opens a dropdown menu from the ⋮ button.
Share
Generates a public link that anyone can view without an Orizon QA account. See Output Formats for details on share links.
History retention
By default, analyses in the Recent tab expire after your configured history retention period. The server-side file cache is also tied to this setting — cached file analysis results expire after the same number of days. To change your retention period, go to Settings and update the History retention value. Analyses you save permanently (by toggling Save Permanently) are not subject to retention and will never expire.Server-side file cache
When Orizon analyzes files, it stores the per-file analysis results in a server-side cache. On subsequent runs that include the same files from the same repository and branch, Orizon reads from the cache instead of re-analyzing those files. This reduces token usage significantly for large codebases that change incrementally.What gets cached
- The analyzed content of each file, keyed by repository, branch, and file path
- Cache entries expire after your configured history retention period
Viewing cache stats
Clearing the cache
You can clear the cache at two levels of granularity:- By repository and branch — removes only the cache entries for a specific repo/branch combination
- All entries — removes everything from your server-side cache
Click Clear
Click Clear next to a specific repository entry to clear that repo’s cache, or click Clear All to remove everything.
Clearing the server cache does not delete your analysis history — it only removes the cached file-level analysis results used to save tokens on re-runs. Your past analysis outputs remain in History.
Browser (OPFS) file cache
In addition to the server-side cache, Orizon caches raw file contents from GitHub in your browser using the Origin Private File System (OPFS). This is separate from the server cache and only applies to the GitHub input method. When you re-open the same repository and branch, files that are already in the OPFS cache load instantly. Only files not found in the cache are fetched from GitHub.Managing the browser cache
Use the Local Cache panel on the Analyze page to:- See which repositories and branches are cached, how many files are stored, and the total storage used
- Remove a specific repository’s cached files
- Clear all cached files at once