cass

# cass Session Search > **Core Insight:** Your repeated prompts are your best prompts. If you typed it 10+ times, it works. Mine your history. `cass` is an upstream (Dicklesworthstone) tool and is **self-describing** — do not re-learn its surface from this skill. Discover it live: ```bash cass capabilities --json # features/connectors/limits of the installed binary cass introspect --json # full schema of every command + response cass robot-docs guide|commands|examples|schemas|contracts # machine-targeted docs ``` This skill carries only the AgentOps operating doctrine: when to reach for cass, the discovery workflow, the recovery posture, and the anti-patterns we have actually hit. ## Constraints - Never run bare `cass` because it launches a blocking TUI; use a JSON, robot, or explicit file-output command. - Treat a stale index as searchable and refresh it with a bounded background command because stale is not broken and an unbounded rebuild can stall the lane. - Preserve source sessions and require explicit permission for destructive cleanup; recovery may rebuild only derived index state. ## When to Use - "What did I ask last time?" / "find that prompt that worked" — session archaeology - Prior-art check before inventing a new approach, plan, or prompt - Scope archaeology: "when did we decide NOT to do X?" - Post-context-loss recovery: what was searched for after a crash = what mattered ### Folded triggers (ag-s43tg wave 1): `casr` + `cass-memory` route...