claude code history files finder

Other Community

Skill notes

Capabilities

Recover exact captured bytes for deleted or lost files from file-history snapshots, including files changed after their original Write call Search for specific code or content across conversation history Analyze file modifications across past sessions Track tool usage and file operations over time

Completeness invariant

A normal history search must cover both source classes: auto-discovered active homes (~/.claude, profile homes, and the current CLAUDE_CONFIG_DIR), and every archive registered in ~/.claude/history-sources.json. Do not conclude that a session, topic, file, or action is absent unless the

Session File Locations

Each Claude history root stores sessions at <history-root>/projects/<encoded-project-path>/<session-id>.jsonl. Active roots are discovered automatically. Durable archive roots are configured once in ~/.claude/history-sources.json and then included by default. Claude may also keep checkpoint payloads at

Active profiles and long-term archives — searched together by default

~/.claude is only the default home. Anyone who runs Claude Code against third-party models through per-model profiles (each profile is its own CLAUDE_CONFIG_DIR) accumulates parallel history that never touches ~/.claude: ~/.claude-profiles/<name>/projects/… — one per profile (e.g. a kimi, deepseek, glm, step profile) ~/.claude-<name>/projects/… — occasional sibling homes whatever CLAUDE_CONFIG_DIR points at in the current shell

1. List Sessions for a Project

Find all session files for a specific project: Shows sessions ordered by their maximum internal JSONL timestamp, with the full internal range, size, path, and source provenance. File mtime is never used. Optional: --limit N to show only N sessions (default: 10), and --from-date or --to-date to keep sessions whose internal range overlaps the requested

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview claude-code-history-files-finder.preview
# Workflow Examples

For detailed workflow examples including file recovery, tracking file evolution, and batch operations, see `references/workflow_examples.md`.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.