Session Search

CommunityPopular

pchalasani

session-search

For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.

Overview

Publisher	pchalasani
Repository	`claude-code-tools`
Skill name	`session-search`
Stars	2K
Forks	134
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by pchalasani on GitHub. Read the source before you install it.

Installation

Install the Session Search AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/pchalasani/claude-code-tools/tree/main/plugins/aichat/skills/session-search
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/pchalasani/claude-code-tools/tree/main/plugins/aichat/skills/session-search

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git /tmp/claude-code-tools
mkdir -p .claude/skills
cp -r /tmp/claude-code-tools/plugins/aichat/skills/session-search .claude/skills/session-search

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Session Search in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Session Search on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Session Search is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

If you are Claude Code: Do NOT use this skill directly. Use the session-searcher subagent via the Task tool instead - it handles this more efficiently without polluting your context.

session-search

Search and find previous code agent sessions (Claude-Code or Codex-CLI) for specific work, decisions, or code patterns.

Workflow

Understand the query: Identify what the user is looking for (code patterns, decisions, specific work, design direction)
Search with aichat: Run aichat search --json -n 10 "[query]" (use -g "project" to filter by project)
Parse results: Use jq to extract fields from JSONL output (session_id, project, created, snippet, file_path)
Deep dive if needed: Read session files at ~/.claude/projects/*/[session-id].jsonl (max 3 files)
Summarize: Return a focused summary with key findings and references

Run aichat search --help to see all options (date filters, branch filters, etc.) and JSONL field names.

Output Format

Return a concise summary containing:

Key Findings: 2-3 bullet points answering the query
Relevant Sessions: Session IDs and dates for reference
Specific Content: Code snippets or quotes if directly relevant

Format as clean markdown, not raw JSON.

Example

Query: "Find sessions where we discussed authentication design"

bash
aichat search --json -n 10 "authentication design"

Summary:

Session abc123 (Dec 10): Discussed JWT vs session-based auth, decided on JWT
Session def456 (Dec 8): Implemented refresh token rotation pattern

Constraints

ALWAYS use --json flag with aichat search (otherwise it spawns interactive UI)
NEVER return raw JSON output to the user - summarize and distill findings
NEVER read more than 3 session files per query
If no results found, suggest alternative search terms
ONLY report information directly observed in files - never infer or extrapolate

Error Handling

If aichat search command fails or is not found, ask user to install:

bash
uv tool install claude-code-tools   # Python package
cargo install aichat-search         # Rust search TUI

Prerequisites:

Node.js 18+ (for action menus)
Rust/Cargo (for aichat-search)

If user doesn't have uv or cargo:

bash
curl -LsSf https://astral.sh/uv/install.sh | sh           # uv
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh  # Rust

Frequently asked questions

What does the Session Search AI skill do?

For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.

Why use Session Search on TypingMind?

Because you install it once and use it with any model. Session Search is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Session Search in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pchalasani/claude-code-tools/tree/main/plugins/aichat/skills/session-search. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Session Search?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Session Search?

As many as you like. As long as a model supports skills, you can use Session Search with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Session Search AI skill free?

Yes. It is published on GitHub by pchalasani under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Claw Score

openclaw

OrganizationPopular

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

session-search

Workflow

Output Format

Example

Constraints

Error Handling

Frequently asked questions

Related AI Skills

Set up your own AI workspace now