skills.rest
vinzenz
vinzenzCOMMUNITY
Explore all skills by this author →
Website𝕏@evilissimoGitHub

agent-log

Query local coding-agent session logs across projects through a unified indexed CLI.

Updated Jul 28, 2026
Search Tags:#developer tools#cli#claude code#full-text search#session history#session logs#codex cli
One-click install
npx skills add https://github.com/vinzenz/workflows --skill agent-log-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-log
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/agent-log
Command: npx skills add https://github.com/vinzenz/workflows --skill agent-log-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Past coding-agent sessions are scattered across raw stores like ~/.claude/projects, ~/.codex/sessions, and ~/.copilot/session-store.db, which can total gigabytes and are impractical to grep manually. This Skill provides a read-only, incrementally refreshed index over all of them so questions about past work can be answered cheaply and deterministically. ## Core Features & Use Cases - Cross-agent session search: Query sessions from GitHub Copilot CLI, Claude Code, Codex CLI, and opencode with one command, scoped to the current project or across all projects. - Full-text search and transcripts: Use FTS5 search to find sessions mentioning an error or file, then view compact or full transcripts filtered by role, tool, or keyword. - Stats and index health: Aggregate usage by agent, day, project, tool, branch, repo, and model, and inspect or rebuild the index when needed. - Use Case: You hit an ECONNREFUSED error and suspect you solved it before. Run a search across all indexed sessions, find the matching session, and view the compact transcript to recover the fix. ## Quick Start Ask the agent to use agent-log to find which past session touched a specific file or mentioned a specific error message.

Frequently Asked Questions about agent-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past Claude Code or Codex CLI sessions?▼

Use agent-log search with a query string to run FTS5 full-text search across all indexed sessions. Add --agent claude or --agent codex to narrow results, and --project to scope to a specific repository.

How do I find which coding agent session touched a specific file?▼

Run agent-log search with the file path, such as agent-log search "src/auth/tokens.ts". Then use agent-log show with the session ref to view the compact transcript of what that session did.

Can I query agent sessions from a different project?▼

Yes. Run agent-log projects to list indexed projects, then use --project <name> on sessions or search commands, or pass --all-projects to drop the project filter entirely.

Is it safe to grep ~/.claude/projects or ~/.codex/sessions directly?▼

It works but is impractical: the Codex corpus alone is about 1 GB across hundreds of files. agent-log replaces raw grepping with a read-only incremental index that refreshes automatically before each read.

Why is my agent-log index out of date or showing errors?▼

The index refreshes automatically before every read unless --no-refresh or AGENT_LOG_NO_REFRESH=1 is set. Run agent-log index status to check for errors, or agent-log index reset to rebuild from scratch.

Related Skills

Explore More Software Engineering Skills→
harivansh-afkharivansh-afk
3

coding-agent

Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent in background processes.

Community
Advanced
HuuBarHuuBar

claude-code-history-files-finder

Recover deleted code from Claude Code session history files.

Community
Advanced
berkcangumusisikberkcangumusisik
11

git-blame-explain

Explain code line origins using git blame and commit history.

Community
Intermediate
kmshihab7878kmshihab7878
6

recall

Searches semantic vector memory, structured files, and session logs for relevant context.

Community
Advanced