Get started

Useful memory.
On your terms.

Install the client, start privately, then choose your coding-agent integration. Google sign-up is optional. Woodwide beta corrections and checks are unlimited; your model provider may charge for extraction.

01 / Get the client

Versioned downloads

Release 0.1.0

Install the client, then choose your setup

Download the client bundle below and check its SHA-256 before opening it. Follow this version’s guide for the supported platforms and exact installer steps; no source checkout is required for the packaged path.

Open release 0.1.0 install guide

Client bundle

woodwide-0.1.0-node.tar.gz

Download client bundle

SHA-256

0fceecedf6e30b2c565c7cb93325d3ca689417813d26c179870174bcedf69b4d
Check this download with Node.js

Run in the directory containing the downloaded file, before extracting or executing it. A matching checksum detects a changed file; it is not a signature or a security audit.

Verify client bundle
node --input-type=module -e "import fs from 'node:fs'; import {createHash} from 'node:crypto'; const actual=createHash('sha256').update(fs.readFileSync(process.argv[1])).digest('hex'); if(actual!==process.argv[2]){console.error('SHA-256 mismatch. Do not install.');process.exit(1)} console.log('SHA-256 matches.');" 'woodwide-0.1.0-node.tar.gz' '0fceecedf6e30b2c565c7cb93325d3ca689417813d26c179870174bcedf69b4d'

Client installed? Continue with private setup ↓

Download, verify, inspect, then install. Do not pipe a download directly into a shell. The client is the starting point for CLI setup; the Claude Code plugin is an alternative integration, not an additional required install. Use either Claude Code settings hooks or the plugin for the same events, not both.

02 / Start privately

Start account-free

Complete the release install guide first. Once woodwide is available in your terminal, initialize private memory without hooks or extraction:

Installed client · private setup
woodwide init --local --no-install --extract false
woodwide memory

This local initialization does not create an account, install hooks or enable extraction. Sharing and benchmark telemetry are off. An empty memory list is expected before your first successful extraction.

Developer fallback: build an existing source checkout

These commands require the root of an existing Woodwide source checkout and Node.js 22.5 or later. They do not download the source. Dependency installation and the build may access the network; this is not an offline install.

Developer fallback · repository root
node --version
npm install
npm run build
node packages/cli/dist/main.js init --local --no-install --extract false
node packages/cli/dist/main.js memory

Keep the full node packages/cli/dist/main.js prefix when using this checkout. Where installed-client examples below begin with woodwide, substitute that full prefix. Keep the built client location stable after installing hooks.

Enable extraction deliberately

For Codex sessions, automatic extraction uses your authenticated Codex CLI. For other sessions it uses the Anthropic API when configured, otherwise Claude CLI; automatic API failure may fall back to Claude CLI. OpenCode and Gemini backfill do not necessarily reuse the session’s original provider.

Processing disclosure

Backfill sends a redacted session digest to the configured cloud provider. It may use subscription or API quota. Redaction is imperfect; provider data terms still apply. It is not on-device inference.

Optional extraction · Codex sessions
woodwide config set extraction_enabled true
woodwide backfill --harness codex --days 14 --limit 5
woodwide memory

Run backfill in an interactive terminal and review its confirmation before proceeding. Use --harness claude-code, opencode or gemini-cli for the corresponding session source. Provider authentication and the relevant CLI or optional API dependency must already be available.

Read and export existing memory · no inference
woodwide memory "repeated build failure"
woodwide memory --export ./woodwide-notes

The CLI’s memory --show option reads a local ID from the listing. Canonical JSON and readable Markdown live under ~/.woodwide/playbooks/, or your configured WOODWIDE_HOME. Exported copies do not update themselves after a redaction-rule change.

03 / Connect an agent

Connect your coding agent

After local setup, install only the integration you intend to use. Hook commands refer to the client location: keep it stable and reinstall/review changed definitions after an upgrade.

Verified on 8 September 2026: Codex CLI 0.153.4 on macOS and Ubuntu, local JSON/Markdown retention, shared correction recall in both directions, secret-guard checks and real elapsed-time offer expiry. Node 22.5 launcher compatibility was also tested. These are controlled synthetic tests, not a benchmark of real-world fix quality.

Install the Codex hooks
woodwide install codex
woodwide doctor

Codex: review before you trust

Open /hooks in Codex, inspect the exact Woodwide commands, then trust the definitions you approve. Repeat this review when definitions change. Do not write trust hashes or bypass review.

Hooks are enabled by default unless [features].hooks=false. Installation alone does not activate an untrusted hook. Check that the definitions are trusted and enabled in Codex; the doctor command lists installation details, not your approval.

Claude Code

Choose settings hooks, then restart Claude Code. Alternatively follow the plugin guide accompanying your client. Do not enable both for the same events.

Claude Code settings hooks
woodwide install claude-code

OpenCode

Install the OpenCode plugin and restart OpenCode. Extraction provider selection is separate from the provider that ran the original session.

OpenCode plugin
woodwide install opencode

Gemini CLI / MCP

Use transcript backfill for Gemini sessions; live hooks are not available. MCP provides memory and network tools; its guard only protects operations when the host calls and enforces it.

Start MCP over stdio
woodwide mcp

Suggestions that keep you moving

Manual mode is the default: one optional playbook offer, no pause in agent work and no reply required. An unanswered offer expires after 60 seconds unless you interact with that specific suggestion before it expires. Unrelated chat or tool activity does not extend it; silence is not acceptance.

Asking to show an offer keeps it available for that workflow. Viewing is not acceptance and does not mark the task successful.

Prefer fewer confirmations?

Enable auto_consume to accept eligible, screened guidance in the current task without another Woodwide confirmation. It is off by default, and your choice is saved until you change it.

Enable auto-consume · optional
woodwide config set auto_consume true
Disable auto-consume · return to manual mode
woodwide config set auto_consume false

Auto-consume does not launch a headless agent or subagent, or grant permission to use tools, make destructive changes or upload data. Offer expiry leaves secret-guard and correction-capture settings unchanged. Read the guidance boundaries.

04 / Optional network

Add shared lessons when you choose

Local memory works without signing in. When available, Continue with Google opens the Woodwide account service for sign-up and account management. Keep API keys private: do not paste them into this website or put them in a URL.

Sign in with Google and create a CLI key on the account page. Connect it in your terminal using the hidden prompt below. Login enables network recall; publishing and telemetry keep their own settings and start off.

Connect your account · hidden key prompt
woodwide login --no-browser

Paste the key only into that hidden prompt. Network recall sends a task/error query and stack context. Before publishing, review the proposed generalized playbook and the processing and retention boundaries. Sharing is never required for free-beta corrections or checks.

05 / Keep control

Separate switches. Readable copies.

Disconnect Woodwide network access · keep local memory
woodwide network off

This stops Woodwide server requests. Reading existing local summaries stays available. Model-provider extraction is controlled separately.

Stop extraction and telemetry · retain memory
woodwide config set extraction_enabled false
woodwide config set telemetry false

For a connected account, turning sharing off stops publishing; it may send the updated preference to the configured server. Telemetry is a separate control.

Stop publishing
woodwide share off

Choose review mode before publishing. The CLI’s review command can approve uploads; it is not just local reading.

Require review before publishing
woodwide config set upload_mode review
Remove installed hooks
woodwide uninstall all

This removes installed settings hooks/plugins managed by that command; remove an independently installed Claude Code plugin through its own installation mechanism. It does not delete local summaries, stop manually invoked processing, erase uploads or remove downloaded client files.

Troubleshooting

No summaries after backfill?

Check the selected harness, date window and extraction setting. A session may be too short, already processed, unavailable or rejected by screening. Use the CLI’s doctor and status diagnostics below. An empty list means no summaries are available yet.

Extraction or queue processing stopped?

Use the CLI’s doctor command to inspect worker lock PIDs. Only after confirming a worker has stopped should you remove its specific stale lock. Retain queue and batch files; then use the CLI’s process-queue command to resume queued work. Do not remove a live worker’s lock.

A provider call fails?

Check provider login, availability and quota. Codex extraction supports the standard authenticated provider and does not retain custom provider configuration. A Codex failure is not silently rerouted to Anthropic.

Check installation and memory status
woodwide doctor
woodwide status