What problem does it solve? Coding sessions are scattered across multiple AI engines (Claude, Codex, OpenCode, APX) with different storage formats and locations, making it hard to find a past conversation, recall what was decided, or continue work where you left off. ## Core Features & Use Cases - Cross-engine discovery: Find sessions by title or transcript content across every detected engine with apx session find, without knowing which engine owns the session. - Summarize and ask: Generate LLM summaries of any session or ask questions about large transcripts via map-reduced RAG-style Q&A. - Resume and migrate: Re-open sessions in their native CLI, or convert a Codex/Claude session into a new APX session with --into apx:slug to continue work under a different agent. - Use Case: You remember discussing sidebar changes last week but not which tool you used. Run apx session find "sidebar", then apx session ask <id> "what sidebar changes were left pending?" to recover the context instantly. ## Quick Start Ask the agent to find the session about improving the web UI and summarize what was left pending.
