Memodb Io
Persist what Claude Code learns across sessions by auto-capturing, organizing, and reusing skills as a memory layer.
Overview
memodb-io (Acontext) is a plugin marketplace for the Build phase that adds a skill memory layer so Claude Code can auto-capture, learn, and reuse skills over time.
What is this marketplace?
- Single acontext plugin (v0.1.3) as a skill memory layer for Claude Code
- Auto-capture, learn, and reuse skills across sessions
- Targets builders who repeat similar coding rituals and want compounding agent knowledge
- Source packaged under memodb-io’s Claude Code plugin path
- 1 plugin in marketplace (acontext)
- Plugin version: 0.1.3
- Owner: memodb-io
Community signal: 3.5k GitHub stars.
What problem does it solve?
Every new session resets tacit know-how—custom skills, fixes, and workflows do not stick unless you manually rewrite prompts.
Who is it for?
Indie builders running Claude Code daily on the same products who want session-to-session skill reuse without maintaining a giant manual prompt library.
Skip if: One-off experiments with no repeat workflows, or teams with strict policies against automated capture of local session content.
What do I get? / Deliverables
After installing acontext, recurring skills and learned behaviors can be captured and invoked again without rebuilding context from scratch.
- acontext plugin in Claude Code
- Auto-capture and reuse pipeline for skills
- Versioned marketplace entry (0.1.3) for catalog install
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Agent-tooling is the canonical shelf because the product is explicitly a skill memory layer for Claude Code, installed where you configure the agent stack. Acontext extends the agent with capture-and-reuse mechanics rather than shipping end-user product UI.
How it compares
Agent memory marketplace plugin, not a single task skill like a linter or deploy script.
Common Questions / FAQ
Who is Memodb Io (Acontext) for?
Claude Code users who want durable skill memory—capture, learn, and reuse—across long-running solo or small-team projects.
When should I use Acontext?
Use it when you are setting up agent-tooling and expect the same skills (deploy, test, scaffold) to run repeatedly across the builder journey.
How do I add Memodb Io to my agent?
Add the Memodb Io marketplace in Claude Code, install the acontext plugin (0.1.3), and follow Memodb Io setup for capture and storage.