Cman
Search and summarize prior Claude Code sessions, plans, and memory across projects so long-running solo builds stay coherent.
Overview
cman is a plugin marketplace for the Operate phase that lets Claude Code search and summarize past sessions, plans, and memory across projects for agentic continuity.
What is this marketplace?
- Agentic memory across Claude Code sessions, plans, and stored memory
- Browse and search past work spanning multiple projects
- Summarize long session histories without manual copy-paste
- Marketplace metadata v1.3.0 from laiso
- Single cman plugin sourced from repository root
Community signal: 28 GitHub stars.
What problem does it solve?
Your Claude Code work is scattered across sessions and repos, so you waste time reconstructing plans and decisions instead of shipping the next task.
Who is it for?
Solo builders running multiple Claude Code projects who need durable session and plan recall without maintaining a separate knowledge base.
Skip if: Teams that already enforce a single source of truth in Notion or Linear with no local session history, or users who only run one-off chats with no repeat workflows.
What do I get? / Deliverables
After installing cman, you can query and summarize prior sessions and plans so each new agent turn starts with recovered context across projects.
- Searchable access to prior Claude Code sessions and plans
- Summaries of long multi-session threads for faster restart
- Lower context-rebuild cost when switching between projects
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Operate/iterate is the canonical shelf because cman shines when you are maintaining context across many sessions after initial build spikes—not a one-shot code generator. Iterate reflects continuous recall of past decisions, plans, and session notes rather than net-new feature coding or launch distribution.
How it compares
Cross-session memory marketplace for Claude Code, not an LLM integration skill or cloud observability MCP.
Common Questions / FAQ
Who is Cman for?
Indie developers and agent-heavy workflows that depend on Claude Code session history, plans, and memory files across more than one codebase.
When should I use Cman?
Use it whenever you resume work—scoping, building, shipping, or iterating—and need to find or summarize what earlier sessions already decided.
How do I add Cman to my agent?
Add the laiso/Cman Claude Code marketplace, install the Cman plugin (v1.3.0), and use its browse/search/summarize flows against your local session and memory stores.