local-conversation-history

Routes local AI conversation history requests across Claude Code, Codex, and Kimi CLI providers.

1.4k|216|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/daymade/claude-code-skills --skill local-conversation-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-conversation-history
Source: https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/local-conversation-history
Command: npx skills add https://github.com/daymade/claude-code-skills --skill local-conversation-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you ask about past AI conversations without naming a platform, a single-provider lookup can silently miss history stored elsewhere. This Skill acts as the entry point that decides which provider-specific skill should handle your request, and it owns the one job no single provider can do alone: a unified inventory spanning Claude Code, OpenAI Codex, and Kimi CLI history.

Core Features & Use Cases

  • Platform and intent routing: Directs each request to the correct executor skill based on platform (Claude Code, Codex, Kimi CLI) and whether you need evidence (what was said) or resumption (continuing interrupted work).
  • Cross-provider inventory: Produces a single list of sessions with titles, dates, and IDs across all three providers using the --source all scope.
  • Cross-provider content search: Extends full-text search beyond Claude's store by adding --codex and --kimi flags when a quote, file, or tool result could live in any provider.
  • Use Case: You ask "what have I been working on this week?" without remembering which tool you used. This Skill routes to the bundled inventory with all providers in scope, so no conversation store is silently skipped.

Quick Start

Ask the assistant to list all your recent AI conversations across Claude Code, Codex, and Kimi CLI, or to find which past chat discussed a specific topic.

Frequently Asked Questions about local-conversation-history

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

FAQPage Schema
How do I search my AI conversation history across multiple tools?

Use the cross-provider content search route, which runs the Claude history search with --codex and --kimi flags added. Each provider maintains a separate store, so all three flags are needed to cover every conversation source.

How do I list all my past Claude Code and Codex sessions?

Request a cross-provider inventory, which routes to the bundled inventory command with --source all. This returns session titles, dates, and IDs spanning Claude Code, Codex, and Kimi CLI in one list.

Can I resume interrupted work from a previous AI session?

Yes, but resumption requires a verified read first. The router sends you to the matching continuation skill (continue-claude-code-work or continue-codex-work) only after a read confirms the session identity.

Does this skill support Kimi CLI conversation history?

Yes, Kimi CLI history is supported exclusively through this entry point since no dedicated Kimi reader or continuation skill exists. Both inventory and search routes handle Kimi via read-claude-code-history with the Kimi scope named.

Why does a history search return zero results when I know we discussed it?

Zero results do not prove absence because ranked recall and bounded searches miss content phrased differently. Widen the search terms or verify which provider stores were actually covered before concluding the conversation never happened.