cass

# cass Session Search > **Core Insight:** Recurring prompts identify candidates to investigate. Repetition can reflect success, repeated failure, copied instructions or retries; check the surrounding evidence before reuse. `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. - Within authorized sources and destinations, treat a stale index as searchable and refresh it only when the selected invocation permits indexing, using a bounded background command; stale is not broken. - Preserve source sessions and require explicit permission for destructive cleanup; recovery may rebuild only derived index state. ## Authorization and episode association Before any search, view, context lookup, export, index recovery or sync, check source-owner, task, model/provider and destination authorization. Indexes, hit metadata, source paths and tracker comments...