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.
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.
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.
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.
Deployment environments
Mneme runs where engineering teams already work — the laptop, 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.
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/.