Governance for the tools you already use
Mneme HQ fits into AI editors, CI pipelines, and agent runtimes — enforcing architectural decisions at every stage of the generation workflow.
Mneme HQ is the governance layer above your AI coding stack, not a replacement for the tools in it. Each integration connects Mneme's enforcement engine to a different point in your development workflow.
Governing Claude Code Workflows
Hook-level enforcement for every Edit, Write, and MultiEdit Claude Code attempts. Violations block before they reach disk — no PR required.
Mneme HQ + Cursor
Keep architectural decisions in Mneme's structured corpus. Export to Cursor Rules for every session — one authoritative source, two surfaces.
Architectural Governance in GitHub Actions
Run Mneme's enforcement checks against every PR diff. Block merges that violate architectural decisions — a second enforcement layer after generation.
Copilot
Governance for GitHub Copilot suggestions in VS Code and JetBrains. Enforce architectural decisions at the suggestion layer.
VS Code
Mneme HQ inside VS Code — governing Claude Code and Copilot sessions from a unified decision corpus.
GitLab CI
Architectural governance gate for GitLab CI pipelines. Block merge requests that violate recorded decisions.
JetBrains
Mneme HQ for IntelliJ, PyCharm, and WebStorm — enforcing architectural decisions inside JetBrains AI Assistant sessions.