Skip to main content

Automatic Capture

Logging observations by hand is useful, but the real value of Kindling comes from capturing context automatically as you work. Adapters hook into a tool's lifecycle, map its events to observations, and manage capsules for you.

Adapters at a glance​

AdapterCaptures
Claude CodeTool calls, file edits, commands, your prompts, subagent results — and injects prior context on session start.
VS CodeFile saves, manual selection logging, and editor session lifecycle.
OpenCodeSession events and tool activity, with secret redaction.
PocketFlowWorkflow node lifecycle and outputs, with intent inference.
CustomBuild your own on the Rust or TypeScript thin-client APIs.

See the full integrations matrix.

No adapter yet?​

Use the standalone path — kindling demo, kindling search, and kindling browse work without any IDE or agent integration:

Quickstart without Claude Code

The fastest path: Claude Code​

If you use Claude Code, the plugin gives you automatic memory in two steps.

First, make sure the kindling binary is on your PATH (see Install) — the capture hooks shell out to it:

kindling --version

Then add the marketplace and install the plugin:

/plugin marketplace add eddacraft/kindling
/plugin install kindling@kindling-plugins

From then on, every Claude Code session:

  1. opens a session capsule to track activity,
  2. injects prior context from previous sessions in this project,
  3. captures tool calls, commands, errors, and your messages, and
  4. closes the capsule when the session ends.

Hooks fail open — if the binary is missing or errors, they no-op and never block your session.

See the Claude Code adapter for the hook contract, the recall skill, the /memory slash commands, and configuration.

Capturing from your own code​

If you are building an integration rather than using an existing tool, capture through the SDK instead of an adapter:

Next steps​