Phistory

What Phistory does

For each supported release, Phistory installs the exact CLI package and runs it through claude-tap, which captures the prompt-bearing HTTP request without calling the real model provider. The result is stored as prompt.md, trace.jsonl and meta.json in a captures directory organized by agent, version and variant. The prompt.md file is rendered from the archived trace, so system blocks, reminder blocks and system messages are preserved. GitHub Actions checks tracked releases every hour and commits new snapshots.

The hosted viewer at phistory.cc compares snapshots across versions and includes Chinese translations of runtime prompt diffs. Hermes Agent is tracked through the hermes-agent package, next to Claude Code, Codex, OpenClaw, Kimi CLI, opencode, Pi, Oh My Pi and others. Local commands built on uv can capture a latest release, backfill a version range, translate prose and build the static site for offline use.

Key features

• Versioned system prompt snapshots per agent CLI release
• Web viewer for comparing prompts across versions
• Raw trace, rendered prompt and metadata stored for each snapshot
• Hourly GitHub Actions checks for new releases
• Chinese translations for runtime prompt diffs

When to use it

• Checking how the Hermes Agent system prompt changed between releases
• Comparing Hermes tool and policy instructions with Claude Code or Codex
• Citing a stable prompt snapshot in a post or audit

Who it is for: Developers, researchers and auditors who study how agent system prompts evolve.

How it fits with Hermes Agent

Tracks Hermes Agent as one of more than a dozen supported agent CLIs, so each Hermes release's system prompt can be compared over time.

FAQ