memory that knows what matters right now.memory that knows what matters right now.

// install with your agent// install with your agent

the prompt at the top of this page makes your agent audit Pulse before it installs anything: read the repo, explain what gets written, ask confirmation, run doctor, then run the demo — honestly.

// compatible harnesses// compatible harnesses

• Claude Codeprimary supported path — the one-command install above
• Claude Desktop / local MCP clientscompatible — add a stdio MCP server running the same npx command
• Cursorcompatible — add Pulse as a stdio MCP server if your setup supports MCP tools
• Windsurf / other MCP-capable coding agentscompatible — same stdio npx command
• Codex / OpenAI agent harnessesMCP-compatible target — use the stdio command where MCP config is available
• Gemini CLI / Gemini agent harnessesMCP-compatible target — use the stdio command where MCP config is available
• LangChain / CrewAI appsdeveloper integration target — run Pulse MCP as a local tool server
• ChatGPT app / store connectorlater — not in this preview
• Claude Directory / hosted connectorlater — not in this preview
• Pulse Cloudlater — not in this preview

Pulse is an MCP server — it runs anywhere a host can start a local stdio command with npx. the preview proves the Claude Code path first; the same MCP tools (pulse_remember, pulse_recall, pulse_resume, pulse_status, pulse_wipe and friends) answer any compatible host. statuses mirror the Compatible Harnesses table in the repo.

// what the demo proves// what the demo proves

not "it remembers across sessions" — everyone has that. the demo proves the part others don't show: same query, different state, different memory — with the reason visible on every line. and friction is signal: a tense session, a hard week — when state and salience signals are present, Pulse can rank which memory matters now (shown in the demo on a labeled simulated corpus).

1. pulse demo seeds an isolated, labeled SIMULATED corpus — never your data.
2. One question runs in three user states: drained, restored, angry.
3. Different episodes surface — each line shows why: state x1.15 · anchor x1.05 · emotion x1.15.
4. An old structural anchor outranks this week's noise, and the breakdown proves it.
5. The continuity pack shows exactly what your next agent session receives.
6. pulse demo --clean erases the whole demo store.

your first memory will read something like "You installed Pulse MCP and connected it to Claude Code." Pulse may guess an emotion (maybe curiosity?) — curious / relieved / skeptical / skip — but no emotion is stored until you choose one. silence is not consent. Pulse works quietly even if you never import old chats.

// the demo, recorded live// the demo, recorded live

a real run of pulse demo on the real engine (local MLX embeddings): simulated labeled corpus seeds in, one question runs in three user states, three different answers come back with their reasons — then the continuity pack, then the wipe.

if the embedded player does not start, open the demo video directly.

// import old context later// import old context later

start with one memory first. old chats can wait — import is opt-in, previewed before anything enters memory.

• Claude Code sessionsconnector after install. sessions are not scanned yet.
• Codex sessionsconnector available later. sessions are not scanned yet.
• ChatGPT archivechoose an export file only when you want a preview of it.
• Claude app archivepreview threads first. nothing enters memory by default.

// what this is not// what this is not

this is a technical preview — not a broad consumer installer, not Pulse Cloud, not a ChatGPT Store or Claude Directory connector. it is the Claude Code-first path for technical friends, partners, and early reviewers. leaving is one command:

pulse memory wiped. quiet again.