claude-code-history-viewer
Desktop app and web server to browse, search and analyze your AI coding assistant history, Claude Code, Codex CLI, GitHub Copilot, Gemini CLI, Cursor, OpenCode and more. 100% offline.
Runssource: GitHubhomepageTypeScriptMITcommit 7f48907081d9
TypeScript, MIT licensed. The project labels itself: ai coding assistant, chat history, claude, claude code, codex, conversation history, copilot cli and cursor.
claude-code-history-viewer runs. An Argusic agent installed it in 41 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The WebUI server binary builds, starts, and serves the full frontend HTML on port 3727 with a health endpoint returning {'status':'ok'} and HTTP 200 on every route; all 1392 frontend JS tests and 1111 Rust library tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System -dev libraries missing (glib, gtk, webkit, etc.) for Rust build10 minutes
- Runtime .so libraries missing for server binary (gstreamer, enchant, wayland, dbus, icu, dw, orc, xslt, etc.)5 minutes
- pkg-config proto packages (xproto, kbproto, renderproto, etc.) absent3 minutes
- pnpm binary not found in PATH1 minute
- @tailwindcss/oxide-linux-x64-gnu native binding missing in pnpm store1 minute
- Node.js 18.19 too old for Vite 7 (requires 20.19+)1 minute
- Install time
- 41 minutes
- Cold machine to finish
- 43 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- pnpm exec vitest run: 128 test files, 1392 tests passed; cargo test --no-default-features --lib: 1111 Rust tests passed, 0 failed; ./claude-code-history-viewer --serve --no-auth --host 127.0.0.1: curl /health returned '{"status":"ok"}'; curl / returned HTTP 200 with full React app HTML
- Model tokens used
- 1,906,694
- Exact commit tested
- 7f48907081d9
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "Start: ~12:50 UTC" echo "End: ~13:31 UTC" echo "Duration: ~41 minutes"' in /work/repo succeeded in 0ms: 13:32:08 Start: ~12:50 UTC End: ~13:31 UTC Duration: ~41 minutes Here is the complete verified result report. tokens used 1,906,694 Here is the complete verified result report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 41 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 ai-coding-assistant projects Argusic has installed and timed, claude-code-history-viewer was the 6th fastest to reach a running state, and 6 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-coding-assistantchat-historyclaudeclaude-codecodexconversation-historycopilot-clicursordesktop-appdeveloper-toolsgemini-cligithub-copilotoffline-firstopencodereactrustsession-viewertauri
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claude-code-history-viewer)Questions
- Does claude-code-history-viewer run?
- Yes. claude-code-history-viewer runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test claude-code-history-viewer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7f48907081d9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test claude-code-history-viewer?
- The run that produced this verdict cost $1.00: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does claude-code-history-viewer take to install?
- 41 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does claude-code-history-viewer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing claude-code-history-viewer?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does claude-code-history-viewer compare with the alternatives?
- Of the 6 ai-coding-assistant projects Argusic has installed and timed, claude-code-history-viewer was the 6th fastest to reach a running state, and 6 of 6 reached one at all.
- Where is the evidence for claude-code-history-viewer?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.