coding_agent_session_search

ta is deleted during indexing and checked again before exporting. My setup is a laptop and a mac mini without an interface. The agent can work on the mini all night, and in the morning I extract its memory. Then the agent on my laptop will know what the mini tried, what broke, and what eventually worked. There are other projects (cass, ctx, claude-mem): https://github.com/Dicklesworthstone/coding_agent_session_se... https://github.com/ctxrs/ctx https://github.com/thedotmack/claude-mem I wanted deja to intentionally use a small approach: one binary code with zero dependency, no LLM calls, searchable verbatim text instead of generated summaries, and synchronization via your own SSH. It does not implement its own network transport; it just connects to the system ssh/scp. You can install it via curl, brew, npx or go install, then run: deja install --all

use but might in the future (like opencode, aider, and others). So I made cass in super high-performance rust with every optimization I could think of, and a huge amount of attention to ergonomics and user experience. I’m very pleased with how it came out and think you will be, too. But just as my recent bv ( https://github.com/Dicklesworthstone/beads_viewer ) tool is now being used way more by my agents than by me, I knew from the start that cass should have a “robot mode” designed specifically for use by coding agents. This tool gives coding agents the ability to reach into their own working notes and those of all their peer agents across tools. It’s like a human developer being able to search their Gmail, their notes, and their company Slack and Jira to find things. I went through countless iterations of improving the tool so that agents really love to use it. You can just add this blurb to your AGENTS dot md file to get them to use it (after doing the one-liner curl install, which takes 3 seconds): ``` cass — Search All Your Agent History What: cass indexes conversations from Claude Code, Codex, Cursor, Gemini, Aider, ChatGPT, and more into a unified, searchable index. Before solving a problem from scratch, check if any agent already solved something similar. NEVER run bare cass — it launches an interactive TUI. Always use --robot or --json. Quick Start # Check if index is healthy (exit 0=ok, 1=run index first) cass health # Search across all agent histories cass search "authentication error" --robot --limit 5 # View a specific result (from search output) cass view /path/to/session.jsonl -n 42 --json # Expand context around a line cass expand /path/to/session.jsonl -n 42 -C 3 --json # Learn the full API cass capabilities --json # Feature discovery cass robot-docs guide # LLM-optimized docs Why Use It - Cross-agent knowledge: Find solutions from Codex when using Claude, or vice versa - Forgiving syntax: Typos and wrong flags are auto-corrected with teaching notes - Token-efficient: --fields minimal returns only essential data Key Flags | Flag | Purpose | |------------------|--------------------------------------------------------| | --robot / --json | Machine-readable JSON output (required!) | | --fields minimal | Reduce payload: source_path, line_number, agent only | | --limit N | Cap result count | | --agent NAME | Filter to specific agent (claude, codex, cursor, etc.) | | --days N | Limit to recent N days | stdout = data only, stderr = diagnostics. Exit 0 = success. ```