landmine

Website and docs: landmine.tech · For AI agents: llms.txt · Cite: CITATION.cff

_{A real Claude Code session, replayed from its transcript (docs/e2e). Full 50-second video: landmine.tech/media/landmine-demo.mp4 · 68-second launch video: YouTube.}

Your coding agent is about to write await db.$client.end(). Your lockfile pins drizzle-orm 0.36.0, an open GitHub issue filed against exactly that version says this call is broken, and a stranger in the thread posted the way around it.

landmine stops that edit once, hands the agent the issue and the quoted workaround, and then lets the retry through.

• landmine scan.
  • Reads your lockfiles and finds the open GitHub issues that name the exact version you pin.
  • Checks every hit and works out which code symbols each issue is about.
  • Picks the most useful workaround from the comments.
  • Writes everything to .landmine/index.json.
• landmine install. Adds a pre-edit hook (or plugin) for the coding agents it finds in the project: 20 agents, from Claude Code, Codex and Cursor to OpenCode, Kilo Code, Cline, Windsurf, Copilot and Antigravity (see Supported). Agents without a pre-edit hook get a rules section, an Agent Skill and the MCP server instead.
• landmine cards (optional). A model reads each issue thread once and writes a trigger card: the API, the extra conditions that make the bug fire, and the workaround. The hook then checks cards offline. It never calls a model.
• landmine mcp. An MCP server the agent can query on demand ("is this error a known bug in the version we pin?"). There is also a hosted one at https://landmine.tech/mcp, with nothing to install, for any exact npm or PyPI version.
• The hook. It runs before each edit, offline. It took 0.11 s per call on our test machine, including Node startup, with a 149 KB index that has trigger cards. It pauses an edit only when two things are true:
  • the edit uses a symbol from one of those issues
  • the file also matches the issue's specifics: an option it names, a sibling API, or the database driver

Context7 serves docs, not bug reports. GitHub's MCP server can search issues when your agent thinks to ask, and its dependency checks cover vulnerabilities only. Neither reads your lockfile, matches open bugs to your pinned versions and the symbols you're editing, or steps in before the edit.

What we measured (Benchmark). On 21 held-out traps built from bugs filed after the model's training cutoff:

• Unaided: Claude Sonnet 5.5 passed 86% (72/84).
• **With the `land

... View full README on GitHub