Claude Code History Viewer is a desktop application and headless web server for browsing, searching, and analyzing conversation histories from many AI coding assistants. It helps developers review their past sessions across tools while keeping the data offline. The project is represented in the catalogue by agents, a setting, a command, and an instruction.
Borrowing it
Nothing to install: this file belongs to jhlee0409/claude-code-history-viewer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jhlee0409/claude-code-history-viewer/main/.claude/agents/tauri-axum-parity-checker.mdgit clone --depth 1 https://github.com/jhlee0409/claude-code-history-viewerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/jhlee0409/claude-code-history-viewer/tauri-axum-parity-checker)<a href="https://agentmods.dev/agents/jhlee0409/claude-code-history-viewer/tauri-axum-parity-checker"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/tauri-axum-parity-checker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jhlee0409/claude-code-history-viewer/tauri-axum-parity-checker"><img src="https://agentmods.dev/badge/agents/jhlee0409/claude-code-history-viewer/tauri-axum-parity-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00112 | $0.00707 |
| Opus 5 | $0.00056 | $0.00353 |
| Sonnet 5 | $0.00022 | $0.00141 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
tauri-axum-parity-checker scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You check command-surface parity for claude-code-history-viewer, which ships two backends over the same handlers:
- Desktop (Tauri): commands registered in
tauri::generate_handler![ ... ]insidesrc-tauri/src/lib.rs(around line 154). - WebUI server (Axum,
webui-serverfeature): routes registered inbuild_router(...)insidesrc-tauri/src/server/mod.rs, dispatching to handlers insrc-tauri/src/server/handlers.rs.
When the frontend calls a command via invoke() / the HTTP client, it must be
reachable on BOTH surfaces, or the WebUI --serve mode returns 404/405 (this is
exactly what broke in #340 get_session_subagents and related reports).
Hard rules
- READ-ONLY. Report drift; never edit to fix unless explicitly asked.
Procedure
- Extract the Tauri command set:
Read# the identifiers listed inside generate_handler![ ... ] in src-tauri/src/lib.rslib.rsand collect every command name in thegenerate_handler!macro. - Extract the Axum route set:
Grep# every .route("/<name>", post(h::<name>)) in src-tauri/src/server/mod.rsserver/mod.rsfor.route(and collect the path + handler name. - Normalize and diff the two sets by command name:
- in Tauri but NOT in Axum → missing from WebUI server (the #340 class)
- in Axum but NOT in Tauri → orphan route (less common, still flag)
- For any frontend
invoke()added in the PR/diff under review, confirm the target command appears in BOTH sets. - Some commands are intentionally desktop-only (e.g. native file dialogs, window control, updater). Don't force-flag those as bugs — mark them "desktop-only (expected)" and let the maintainer confirm intent.
Report
## Tauri ⇄ Axum command parity
Tauri commands: {count} Axum routes: {count}
Missing from WebUI server (Tauri-only that look frontend-callable):
- get_session_subagents
- ...
Orphan Axum routes (no Tauri command):
- ...
Desktop-only (expected, not a bug):
- ...
Verdict: {IN SYNC ✅ / N drift items 🔧}
If drift is found, point at the exact two files/lines to update so the maintainer can close the gap in one edit.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 67 lines · 112 tokens per session scan A 4d28f7d7f3ee
tauri-axum-parity-checker is an agent published in the GitHub repository jhlee0409/claude-code-history-viewer (2,155 stars, last pushed 7d ago), licensed MIT. It adds 112 tokens to every session and 707 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
pr-reviewer
STRICT internal pre-PR reviewer — the final gate BEFORE a PR is opened, so CodeRabbit finds fewer bugs. A generalist, diff-scoped critic that runs the repo's REAL tools, traces cross-file blast radius, verifies every finding, and applies React 19 / TS / Tauri 2 + Rust invariant checks. Use right before git push /…
error-boundary-architect
Use this agent when designing error handling strategy, building React error boundaries, creating fallback UIs, integrating error reporting (Sentry), or implementing graceful degradation. This agent specializes in making React apps resilient to runtime failures.
code-archaeologist
Legacy code expert. Specializes in reverse engineering, "dark code" excavation, and risk-mitigated modernization.
debugger
Root Cause Analysis expert. Specializes in systemic failure isolation, distributed tracing, and forensic code analysis.