Claude Code, Codex & Cursor Plugin
Persistent memory for AI coding agents
Your agent forgets everything between sessions. wire-memory fixes that. Decisions, corrections, patterns, and preferences, captured automatically and retrieved when relevant. Backed by Wire containers via MCP.
Free and open source · MIT license · No account required to try
The Problem
Every session starts from zero
Sound familiar?
No continuity
Your agent forgets everything between sessions. Every conversation starts from zero, no matter how much ground you covered yesterday.
Repeated corrections
"Don't mock the database in tests." You said it last week. And the week before. And you'll say it again tomorrow.
Re-explaining context
"Here's how our project works..." again. Every session, you re-teach the agent things it should already know.
No cross-project awareness
Your coding preferences, communication style, and tooling choices don't carry over. Each project is an island.
How It Works
Memory that works in the background
wire-memory captures context as you work and retrieves it before your agent responds. No manual note-taking, no extra prompting.
Automatic logging
Decisions, corrections, and patterns are captured as they happen. No manual note-taking required.
Automatic retrieval
Before responding, your agent searches past context for relevant decisions and corrections. No extra prompting needed.
Scoped by project
Memory is tagged by project and user. Retrieval stays relevant to the work at hand, not polluted by unrelated context.
Portable via MCP
Stored in a Wire container. Access the same memory from Claude Code, Codex, Cursor, or any MCP-compatible tool.
Transcript capture
Optionally upload full session transcripts to your container. Secrets are redacted automatically. Disabled by default.
Getting Started
Set up in 60 seconds
Pick your editor. Connect. Start coding.
Install the plugin
# Add the Wire marketplace (one-time)
/plugin marketplace add usewire/wire-plugins
# Install wire-memory
/plugin install wire-memory@wire-pluginsConnect your container
/wire-connect Authenticates via your browser and links a Wire container for storage. No Wire account required. Get a free 7-day trial container instantly.
Start coding
That's it. wire-memory automatically captures decisions and corrections as you work, and retrieves relevant context at the start of each session. No configuration, no extra prompting.
Requirements: Node.js ≥ 18 and Claude Code, Codex, or Cursor. wire-memory has zero npm dependencies.
Memory Types
What your agent remembers
Four types of context, captured automatically.
Decisions
Architectural choices and trade-offs
"Use Drizzle ORM over Prisma for Cloudflare Workers compatibility"
Corrections
Feedback when you redirect the agent
"Don't mock the database in integration tests. Use a real test DB"
Patterns
Coding conventions and established practices
"All API routes use requireAuth() middleware before requirePermission()"
Preferences
Global style and communication preferences
"Keep responses concise. No trailing summaries after code changes."
MCP Tools
Five tools, zero configuration
wire-memory exposes these MCP tools to your agent automatically.
Full-text and semantic search across your stored memory
Log decisions, corrections, patterns, and preferences
Browse what's stored: types, schemas, entry counts
From a known entry, reach its siblings, full source, or relationships
Remove outdated or incorrect entries
Built on the Wire SDK
The same primitives any team can ship on
wire-memory is a first-party app on top of @usewire/sdk. The connect flow you ran is a few lines of TypeScript. The same SDK is public, so whatever you are building, an agent, a harness, a plugin, a backend, an internal tool, you can hand it a scoped Wire container the same way wire-memory does.
Three methods
connect, getStatus, disconnect. That is the whole connection lifecycle.
Browser-driven auth
Wire owns the connect screen and authorization. Your code shows a short code, the user picks a container, you get a connection back.
Scoped MCP credentials
connect() resolves with an MCP URL and API key scoped to one container. Hand them straight to your agent's MCP client.
Runs anywhere agents run
Node 18+, Cloudflare Workers, Deno, Bun. Light dependencies, Web Crypto under the hood.
// Same SDK wire-memory uses internally
import { WireClient } from '@usewire/sdk';
const client = new WireClient({ agentId: 'my-agent' });
// Shows a short code, opens the user's browser,
// resolves once they pick a container.
const connection = await client.connect({
label: 'my-laptop',
});
// Hand to your agent's MCP client:
connection.mcpUrl;
connection.apiKey;
connection.containerId; Frequently asked questions
Common questions about wire-memory.
What is wire-memory?
Is wire-memory free?
Which editors does wire-memory support?
usewire/wire-plugins marketplace serves all three. Your memory is stored in a standard Wire container with MCP access, so you can also connect from any other MCP-compatible tool to read and search your stored context.What data does wire-memory store?
Where is my data stored?
Do I need a Wire account to try wire-memory?
How does automatic retrieval work?
Can I build my own agent or tool on the same SDK?
@usewire/sdk, the same SDK any team can install. The SDK gives you connect, getStatus, and disconnect. Wire owns the connect screen and authorization, then hands your code a scoped MCP URL and API key for the container the user picked. Use it from an agent, a harness, a CLI, a plugin, or a backend, anywhere you can run TypeScript.Can my team share a memory container?
What is transcript capture?
/wire-configure. It is disabled by default.Give your agent a memory
Install wire-memory and stop repeating yourself. Free and open source.
View on GitHub