Governance across AI coding models and agent frameworks
Mneme works across frontier, open-weight, and self-hosted AI coding systems by enforcing architectural decisions before generation.
This page describes compatibility, not partnership. Where a native, documented integration exists, it is linked through to /integrations/. Everywhere else, Mneme is designed to operate alongside the tool at the file-write or context-injection seam — harnesses coordinate execution, Mneme enforces architectural intent, and they run side by side. The argument in full: Harness Engineering Still Needs Governance.
Model providers
Mneme HQ is model-agnostic. Governance operates at the seam where the agent reads context and writes to disk, so it does not care which model produced the tokens.
OpenAI
GPT-class models via the OpenAI API and OpenAI-compatible endpoints.
Anthropic
Claude models via the Anthropic API and Claude Code's native runtime.
Google Gemini
Gemini models accessed via Google AI APIs and compatible runtimes.
GLM
GLM-class models served through hosted or self-hosted inference.
Qwen
Qwen models via OpenAI-compatible inference endpoints.
DeepSeek
DeepSeek-class models in hosted and on-prem deployments.
Mistral
Mistral-family models, including instruct and code-tuned variants.
Llama
Llama-class models served via vLLM, Ollama, Together, Groq, and similar runtimes.
Nous Hermes
Nous Research's open-weight Hermes models accessed via hosted or self-hosted inference. Mneme is model-agnostic; the decision corpus is injected at the runtime seam regardless of which Hermes variant the agent is running.
Coding agent ecosystem
Mneme is built to operate alongside the coding agents engineering teams already use. The governance layer can supply decision context to any agent that exposes hooks, file-system access, or a system-prompt seam — and can validate outputs at the CI boundary.
Claude Code
Hook-level enforcement via SessionStart, PreToolUse, and PostToolUse. One of the three documented native integrations.
Cursor
Rules export from the Mneme decision corpus into Cursor's rules system. One of the three documented native integrations.
GitHub Copilot
Designed to support governance alongside Copilot in the editor and in Copilot-driven CI workflows.
OpenHands · OpenDevin
Works across open-source autonomous coding agents that expose tool-use boundaries.
Aider
Compatible with Aider's repo-aware editing flow; decisions surfaced through context injection.
Cline
Designed to support Cline's autonomous coding loops in VS Code-compatible environments.
Roo Code
Works alongside Roo Code's agent surface for governance across its editing and execution paths.
Grok Build CLI
xAI's CLI coding agent. No documented native integration today; designed to be governable at the file-write boundary like other CLI agents — the architectural corpus stays enforceable at the CI gate regardless of which agent produced the diff.
Mistral Vibe
Mistral Vibe brings terminal-native agents, IDE extensions, async workflows, codebase-aware context, and custom model training into enterprise coding workflows. Mneme sits beside that execution layer by turning architectural decisions into enforceable constraints before agent-generated changes become drift.
Devin
Devin executes — plans, edits, runs commands, opens PRs autonomously across repos. Mneme preserves architectural intent across that execution: ADR-derived constraints, deterministic retrieval, hook and CI enforcement that holds across whichever agent ran.
Claude Marketplace
The Claude Marketplace surfaces partner products across generation, memory, orchestration, and review. Mneme operates one layer above as the architectural governance layer that runs before generation and at every execution boundary.
Google Antigravity
Antigravity coordinates autonomous coding agents across editor, terminal, and browser. Mneme works alongside agent-first development environments by providing repo-native architectural governance, ADR retrieval, and deterministic checks.
Agent frameworks
For teams building custom agents, Mneme is designed to plug into common orchestration frameworks as a context source and a validation step. The governance corpus is the constant; the framework choice is operational.
LangGraph
Compatible as a context provider node and a post-step validator in LangGraph-defined flows.
AutoGen
Designed to support AutoGen agent groups by feeding shared decision context across roles.
CrewAI
Works alongside CrewAI crews as a governance layer that all crew members defer to.
Semantic Kernel
Compatible with Semantic Kernel pipelines as a plugin-level constraint and context source.
OpenAI Agents SDK
Designed to support Agents SDK builds via tool-call interception and structured guardrails.
Workspace execution surfaces
Workspace platforms are becoming agent execution environments — places where agents don’t just retrieve context but read, write, search, and trigger workflows. As the boundary between knowledge and execution collapses, governance extends beyond code generation into these operational surfaces.
Notion
Notion is evolving into an agent execution environment — not just documentation, but a surface where agents read, write, search, and trigger workflows. Governance for ADR ingestion, decision corpus import, and invariant preservation across workspace mutations is on the roadmap.
Execution & deployment environments
Mneme runs where engineering teams already work — the laptop, the AI-native terminal, the CI runner, the self-hosted platform — without requiring a hosted control plane.
Local developer workflows
Runs alongside the developer's editor and CLI agents; governance enforced before the file is written.
Warp
Works alongside Warp’s AI-native terminal and autonomous execution workflows. Warp accelerates how teams run agents and orchestrate tasks; Mneme preserves the architectural invariants underneath those execution loops.
CI/CD pipelines
Compatible with standard CI runners as a pre-merge governance check on AI-generated diffs.
GitHub Actions
mneme check on every PR diff. One of the three documented native integrations.
Self-hosted environments
Designed to support air-gapped and on-prem deployments with self-hosted inference.
Enterprise development platforms
Can operate alongside enterprise IDE platforms and internal developer platforms (IDPs).
The governance layer
However the upstream choices are made — whichever model, whichever agent, whichever framework — the governance layer is the constant the codebase is protected by.
Cursor · Claude Code · Copilot
LangGraph · AutoGen · CrewAI
pre-generation enforcement
review · merge gates
Models change. Agents change. Frameworks change. The decision corpus is what survives the swap.
Architectural governance must persist.
Mneme HQ is built to be the layer that does not have to be re-chosen every time a frontier model, coding agent, or framework gets replaced.
Get started
Compatibility statements above describe what Mneme HQ is designed to support and operate alongside. They do not imply official partnerships or vendor-blessed integrations. Where a native, documented integration exists, it is linked to from /integrations/.
Why this list is broad on purpose: see Model-Independent Governance — the design property that lets Mneme produce the same verdict at every enforcement surface regardless of which model or harness generated the work — and the worldview essay Models Are Temporary. Architectural Intent Is Not.