cass

Index and search local coding agent histories across multiple agents.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/trungtnm/claude-code-utils --skill cass-trungtnm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cass
Source: https://github.com/trungtnm/claude-code-utils/tree/main/plugins/skills/cass
Command: npx skills add https://github.com/trungtnm/claude-code-utils --skill cass-trungtnm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding teams and developers store past sessions in many agents. CASS unifies indexing and searching across Claude Code, Codex, Gemini CLI, Cline, OpenCode, Amp, Cursor, ChatGPT, Aider, Pi-Agent, and Factory to expose a single, searchable history.

Core Features & Use Cases

  • Cross-agent search across multiple agent histories to accelerate debugging and knowledge transfer.
  • Incremental indexing, fast lookups, and machine-readable outputs (JSON/robot) for automation.
  • Use cases include QA reviews, post-mortems, and onboarding by surfacing relevant past sessions.

Quick Start

Index all local coding agent sessions and run a sample search with JSON output using the robot flag.

Frequently Asked Questions about cass

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

FAQPage Schema
How do I search across multiple coding agent histories at once?

To search coding agent histories, you first index local sessions from tools like Claude Code, Codex, and Cursor. This creates a unified, searchable history for fast lookups, debugging, and knowledge transfer across agents.

Can I search Cursor and Claude Code session logs together?

Yes, searching Cursor and Claude Code session logs together is supported. The tool indexes local histories from multiple agents, exposing them in a single searchable interface for cross-agent reuse and auditing.

What is the best way to audit past coding agent sessions?

Auditing past coding agent sessions is best done by indexing local histories across agents like Cline, OpenCode, and Factory. This exposes a unified history with timeline views and JSON outputs for automated QA reviews.

Does this cross-agent history search support JSON output for automation?

Yes, cross-agent history search supports JSON output for automation. Using the robot flag provides machine-readable outputs alongside standard search, view, and timeline functions for incremental indexing workflows.

How do I index local coding agent sessions for post-mortems?

To index local coding agent sessions for post-mortems, apply the tool to histories from supported agents like ChatGPT and Pi-Agent. It performs incremental indexing to surface relevant past sessions quickly for review.