Updated: best for, features, integrations, limitations, sources, summary, use cases, walkthrough
See recorded changes
bestForBefore: ["Developers and teams wanting to enforce architectural rules and prevent unintended structural changes."]
After: ["Developers and teams wanting to enforce architectural rules and prevent structural regressions in code changes."]
featuresBefore: ["Detects dependency cycles introduced by code changes."]
After: []
integrationsBefore: []
After: ["Integrates with AI coding agents such as Claude Code, Codex, and GitHub Copilot via MCP protocol."]
limitationsBefore: []
After: ["Requires local installation and runs on the user's machine; no cloud or model-based processing."]
sourcesBefore: [{"url":"https://enola.tech/","label":"enola — architectural regression testing for AI-assisted development"}]
After: [{"url":"https://enola.tech/","label":"enola — architectural regression testing for AI-assisted development"},{"url":"https://enola.tech/docs/","label":"enola docs: install the MCP server and connect your agent"}]
summaryBefore: "Enola is a local CLI and MCP server tool for architectural regression testing and change-impact analysis that runs on your machine without uploading data. It maps your codebase before and after changes to detect structural regressions such as dependency cycles and layer violations, reporting only the changes introduced and failing only the rules you choose."
After: "Enola is a local CLI and MCP server tool for architectural regression testing that detects dependency cycles, layer violations, and unintended change spread in codebases. It compares the architecture before and after code changes to report only the structural regressions introduced by the change, enforcing user-defined structural rules."
useCasesBefore: ["Architectural regression testing to catch structural regressions before code merges."]
After: ["Architectural regression testing to catch structural regressions before code merges.","Automate architectural regression checks integrated with coding agents and CI pipelines."]
walkthroughBefore: ["Run 'enola check' to compare architecture before and after a change, reporting regressions and failing on declared policies.","Use 'enola --explain' to generate an architecture snapshot without setup or baseline."]
After: ["Maps the codebase before a change to create a baseline architecture snapshot.","During a change, provides exact answers about dependencies and impact to the coding agent.","After the change, rebuilds the graph, compares it with the baseline, and returns new findings and regressions."]