How do I install Twiceshy?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Twiceshy need an API key?

No required environment variable is listed on this record.

Twiceshy

by app.twiceshy

Experience memory for coding agents: validated traps, fixes and dead-ends at decision time.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL

https://api.twiceshy.app

Provider

Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code

claude mcp add --transport http app.twiceshy-twiceshy https://api.twiceshy.app

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "app.twiceshy-twiceshy": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.twiceshy.app"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Twiceshy?: Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Twiceshy need an API key?: No required environment variable is listed on this record.
What transport does Twiceshy use?: Twiceshy is reached over HTTP.
When was Twiceshy last checked?: Last checked 2026-10-16. Experience memory for coding agents: validated traps, fixes and dead-ends at decision time.

twiceshy

Once bitten, twice shy.

A self-hosted service that feeds hard-won engineering experience — issues, dead-ends, root causes, validated fixes — to LLM coding agents at decision time, so they stop repeating known mistakes on autopilot. Records are git-backed and provenance-aware; automatic retrieval applies a relevance floor so a weak match can return nothing.

Hosted alpha

The hosted instance runs at twiceshy.app — self-serve tokens, remote MCP endpoint https://api.twiceshy.app/. External contributions require a signed CLA before merge (ADR-0002).

How it works (the locked architecture)

Source of truth: git-backed markdown experience records (YAML frontmatter
- narrative) — format in docs/SCHEMA.md. The corpus is a separate versioned data product (twiceshy-corpus, ADR-0021); the engine ships a small frozen fixture (internal/testcorpus/) for tests.
Index: one derived, always-rebuildable SQLite file (FTS5 plus cached, pure-Go dense vectors for pull retrieval).
Retrieval: fingerprint-exact → BM25 → dense (RRF), stack-fingerprint filtered, hard cap k≤3 with a relevance floor — below it, nothing is injected.
Channels: push (Claude Code hooks → trap cards), pull (MCP tools over streamable HTTP), index (generated one-liners).
Trust: agent-proposed records are quarantined; promotion = sandbox fail-to-pass validation + human PR review. A new record IS a pull request.
Doctors: background jobs that dedup, staleness-check, re-execute repros (CI for memories), decay, and abstract.

Full rationale: docs/research/EXPERIENCE_SERVICE_RESEARCH.md and docs/adr/ADR-0001-architecture.md.

Status

The core service is available as a hosted alpha. For the canonical snapshot of what ships now and the current roadmap, see docs/NEXT_FEATURES.md; deployment and operating details live in docs/DEPLOY-public-alpha.md.

Development

make ci    # lint + race tests + coverage floor — what CI runs

See docs/CONVENTIONS.md and docs/CONTEXT.md first.

License

AGPL-3.0-only. Contribution and corpus licensing: docs/adr/ADR-0002-licensing-strategy.md.