agent-session-search

Index and search coding agent session history via a unified CLI/TUI.

14|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/oakoss/agent-skills --skill agent-session-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-session-search
Source: https://github.com/oakoss/agent-skills/tree/main/skills/agent-session-search
Command: npx skills add https://github.com/oakoss/agent-skills --skill agent-session-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of scattered and difficult-to-search AI coding agent conversations by providing a unified interface to index and query history from multiple agents.

Core Features & Use Cases

  • Unified Indexing: Aggregates session history from over 13 different coding agents into a single searchable index.
  • Fast Search: Provides sub-60ms latency search queries.
  • Robot Mode: Designed for AI consumption with JSON output and forgiving syntax.
  • Use Case: Quickly find a specific code solution or explanation you received from a coding assistant weeks ago, across different tools you've used.

Quick Start

Use the agent-session-search skill to find past conversations about implementing a JWT authentication flow.

Frequently Asked Questions about agent-session-search

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

FAQPage Schema
How do I search AI coding assistant history across multiple tools?

You can search AI coding assistant history across multiple tools by indexing local session logs from agents like Claude Code, Codex, Gemini, and Cursor into a unified interface. This lets you query past interactions and find previous solutions across agents.

What is the best way to find an old code solution from a previous coding agent session?

The best way to find an old code solution is using a unified CLI that aggregates session history from over 13 AI assistants. It supports lexical, semantic, and hybrid search modes with sub-60ms latency to quickly locate specific past explanations.

Can I filter coding assistant history searches by agent, workspace, or time?

Yes, you can filter coding assistant history searches by agent, workspace, and time. The unified index supports these filtering options alongside lexical, semantic, and hybrid search modes to narrow down past session logs efficiently.

Does agent-session-search work with my local Claude Code and Cursor logs?

Yes, agent-session-search works with local Claude Code and Cursor logs, alongside Codex and Gemini. It indexes session history from over 13 different coding agents into a single local index, requiring no external dependencies.

How do I get JSON output from searching AI session logs for automated processing?

You get JSON output from searching AI session logs by using the dedicated Robot Mode. This mode is designed for AI consumption, providing JSON output and forgiving syntax to parse past coding agent interactions programmatically.