Skip to main content
pulse
Talk to founder
Developers · Capture via MCP

Capture AI conversations into Pulse.

Pulse absorbs the conversations you have with your AI clients so the things you and your team decide there don’t get stranded in private chat history. Manual capture is opt-in and explicit. You ask your AI client to “save this to Pulse” and it does. For Claude Code you can also enable an opt-in auto-capture path (a SessionEnd hook) that ingests finished sessions as AUTHOR_ONLY, visible only to you until you promote them. Cursor stores its chats in SQLite, so its history syncs via a manual export instead (npx cursor-history piped into the sync script).

How it works
  1. Generate a personal MCP capture token in Pulse at Settings → Integrations → MCP tokens.
  2. Paste the token into your AI client’s MCP config.
  3. Inside a conversation, say “save this to Pulse, tag it pricing-strategy.”
  4. Your AI client calls one of seven MCP capture tools.
  5. Pulse ingests the content as a Document, runs it through the standard extractor pipeline, and surfaces extracted decisions and commitments in Map, Ask, and entity pages.

Captured conversations appear at /app/captured for browsing.

Seven tools, seven intents
pulse_capture_conversation saves the full conversation. For brainstorming sessions, design discussions, anything where the whole arc matters.
pulse_capture_snippet saves a smaller piece (code block, paragraph, quote). For when only one slice of a long conversation is worth keeping.
pulse_capture_decision records a structured decision with rationale, alternatives, tradeoffs, and confidence. Creates a Decision entity directly, linked to an evidence Document with the full reasoning.
pulse_capture_commitmentrecords a promise someone made, with optional owner, recipient, and due date. Creates a Commitment entity tracked in the team’s commitment surface.
pulse_capture_failure_case records an incident the team should learn from, with pattern, root cause, and signals missed. Appears in Map under the Lessons tab.
pulse_capture_note saves a free-form note, optionally attached to an existing entity (decision, commitment, feature, person, topic, or customer).
pulse_suggest_skill suggests a repeating team procedure to be compiled into a Pulse Skill. Enters the review queue for admin compilation through the DRAFT → SHADOW → ACTIVE pipeline.
Client-specific setup
  • Claude Desktop → JSON config at claude_desktop_config.json, requires restart.
  • Cursor → JSON at ~/.cursor/mcp.json, reload via command palette.
  • Codex CLI → TOML at ~/.codex/config.toml, picked up on next invocation.
  • Drop-anywhere capture → no AI client at all: an HTTP endpoint for iOS Shortcuts / Share Sheet, plus a desktop watched folder.
Limits

100 captures per hour and 1,000 per day per token. 50 KB max per single capture (about 10,000 tokens). Demo workspaces are blocked entirely. If you hit the limits in normal use, get in touch and we’ll talk.