Integrations

Architectural drift prevention across your AI coding stack

One decision corpus, enforced at three layers: agent hooks, generated editor rules, and a deterministic CI gate. Every integration below is labelled with its real support level.

01

Enforcement — native and validated

A shipped adapter checks proposed changes against the decision corpus before they reach disk. Maintained code, tests on main, published evidence.

Native · Shipped

Claude Code

PreToolUse hook blocks violating Edit, Write, and MultiEdit calls before they reach disk.
Native · Shipped

Claude Agent SDK

Injects relevant decisions when a task starts; checks proposed mutations before they land.
Native · Shipped

Google Antigravity

Pre-tool adapter gates Antigravity’s file-mutation tools through the same engine. Tested on IDE 2.8.1.
Validated compatibility

Paperclip

Unmodified Mneme enforced under both Paperclip transports — CLI and ACP. No adapter required.
Native · Shipped

Codex CLI

Pre-execution enforcement for native apply_patch mutations, with a Stop whole-file audit covering shell and script-driven writes. Validated 10/10 against Codex CLI 0.149.1.
02

Propagation — rules export and CI gates

The same corpus carried into tools without a runtime adapter: generated editor rules, and a deterministic gate in pipelines you own.

Rules export

Cursor

Generate conflict-resolved Cursor Rules from the corpus with one command.
CI gate

GitHub Actions

Run mneme check against every PR diff with a reference workflow you own.
CI gate

GitLab CI

The same deterministic gate, native to merge requests.
Corpus workflow

ADR Import

Bring your existing ADRs into the enforcement corpus in one command.
03

Host environments

No dedicated adapters. Governance reaches these tools through the layers above — an underlying supported agent, generated rules, or CI.

Host environment

VS Code

Hosts Claude Code sessions; governed by the PreToolUse hook, no extension needed.
Host environment

GitHub Copilot

No hook API. Covered by the CI gate and the rules export.
Host environment

JetBrains IDEs

Covered by the corpus and the CI gate, regardless of IDE.
Host environment

Warp

No adapter. Governance applies via underlying agent hooks or a CI gate on the diff.
04

Experimental and planned

Nothing here ships today. Experimental means code exists behind a PR or validation is incomplete; planned means design work only.

Experimental

OpenCode

Plugin-hooks approach under evaluation; no production plugin. Compaction experiment: NULL verdict.
Experimental · PR #314

Kiro

Bounded PreToolUse hook adapter, contract-tested, pending review and merge.
Middleware POC planned

Deep Agents

Mneme as custom middleware around filesystem and tool execution: pre-mutation blocking, change reconstruction, subagent propagation.

Planned

n8n

Governance checks for AI-driven workflow automation.

Works alongside — Perplexity Enterprise turns research rationale into enforceable decisions · Microsoft Agent Forge pairs an autonomous workflow substrate with deterministic governance. Research and ecosystem tools, not Mneme integrations.

Every layer reads the same file: .mneme/project_memory.json. Install with pip install mneme-hq, scaffold with mneme init, and wire the layer that fits your stack. The architectural argument: governance across heterogeneous AI coding agents. Standards alignment: MCP, AGENTS.md, NIST CAISI.