What’s new.

Packages and symbols now carry the documentation already in your code: Go package comments, Python package docstrings, Java package-info Javadoc, Rust //! docs, and doc comments in Rust, Kotlin, Scala, Swift, Dart and C/C++. A new docs.jsonl file holds every comment in full, ready for a search tool to index.

enola flows lists a program's entry points (served routes, main, commands, MCP tools) and follows each one through everything its calls reach, ranked by reach. Ask for one flow with --show, or for every flow that reaches a symbol with --through. v0.4.31 added Python argparse and click commands, TypeScript MCP tools and Kotlin Compose.

enola impact lists everything that depends on a symbol, type or module, grouped by how far away it is. Give it a file straight from a diff and it starts from every symbol the file declares. It runs from a shell, so a pre-commit hook, a CI step or a review bot gets the same answer a coding agent does.

enola impact path/to/changed_file.go --list

A link between repositories used to say only that one service calls another. Now a client call names the function that makes it and the route it lands on, and that route names the function that handles it, across TypeScript, Kotlin, Swift, Java, Dart, Python, Go, Scala and PHP. Python services show up as callers for the first time.

One plugin install registers Enola's MCP server, its session hooks, and two skills: one that sends architecture questions to the right tool, and one that checks for the Enola CLI and helps install it. The CLI still needs to be on your PATH.

The three analyzers that used to ship only in a licensed build are now part of the open-source engine, with no licence check or feature flag. They appear in enola --explain, the dashboard and enola check, taking Enola to 22 MCP tools and 22 explainers.

Run Enola on a folder that holds several Git repositories and it analyzes them together as one cluster, with no configuration. If your team wraps HTTP calls in its own client, you can now describe that wrapper, so its calls count in route coverage and cross-repository links.

Enola is on PyPI, with prebuilt packages for Linux, macOS and Windows, published automatically from each release.

pip install enola

Enola reads GraphQL on both sides: servers such as Apollo Server, GraphQL Yoga, NestJS, graphql-ruby and Hasura, and clients such as Apollo Client, Relay and urql. It matches each client operation to the server field it calls, and reports schema operations that nothing calls.

enola constraints init binds ready-made conventions, such as layered, ports-and-adapters and the Rails conventions, to the directories your repository actually has, and tells you what it could not bind. Rules can now also be written as Ruby sentences, which Enola reads but never runs. Angular is now read the way the framework works: decorators, dependency injection, routes and templates.

AsyncAPI contracts and Kafka producers and consumers in Go, TypeScript and Scala now link up the way HTTP routes and their clients do, across repositories too. A channel nobody produces or consumes, or messaging code with no declared contract, now shows up as a finding.

Declare which parts of your system may depend on which, in files that live beside the code. Enola checks every rule against the measured graph and can fail CI on a breach. enola plan tells you which rules govern a change before you make it, and enola constraints mine suggests rules from patterns your code already follows, for you to review.

Three new ecosystems in two days. Enola reads a whole .NET solution (C#, F#, VB.NET, Razor and XAML), including project references, EF Core storage and dependency injection. Scala comes with Play, Pekko and http4s routes, and Dart and Flutter with widgets, navigation and outbound calls.

Enola now records your architecture over time. enola blame finds the revision where a module, dependency or finding first appeared, and enola log --backfill builds that history from your existing Git commits.

enola check compares a change with a pinned baseline and reports only the structural regressions it introduced, with exit codes CI can act on. With agent hooks installed, a coding session is checked the same way when it ends.

Linking several repositories used to work only inside a coding-agent session. Now a config file can name a cluster of repositories, so a CI job or a developer at the terminal gets the same cross-repository links. TypeScript backends built on NestJS, InversifyJS, Express and Fastify now contribute their server routes, so calls to them resolve.

When Enola's MCP server starts, it also serves a read-only dashboard on a local port that refreshes itself. It shows your services and the links between repositories as a diagram, the findings grouped by kind, and where each snapshot came from. enola --help and enola --list arrive in the same release.

Enola reads Rust: functions, structs, enums, traits and their implementations, calls, and use dependencies resolved across the crates of a Cargo workspace.

enola upgrade finds the latest release, downloads the build for your platform, checks its checksum and replaces the binary in place.

enola upgrade

RPCs declared in .proto files become routes, bound to the Go handlers that serve them. Clients using grpc-go and connect-go in Go, and grpc-web and connect-es in TypeScript, link to the services they call.

Take a snapshot on two commits or branches and Enola shows how the structure changed between them. The same release adds C, alongside the existing C++ support.

Enola reads Vue single-file components and composables, and turns Nuxt's file-based routing into routes, so pages/users/[id].vue becomes /users/[id]. PHP joins too, with classes, functions, dependencies and WordPress detection.

Five new checks point at the places that tend to hurt: god classes, call-graph hotspots, deep dependency chains, large public surfaces and complexity outliers. enola --explain now reports them next to its cycle and layer analysis.

An install script for Linux, macOS and Windows that detects your platform and verifies its download. Swift moves to a real syntax-tree parser for SwiftPM and Xcode projects, and outbound HTTP calls from Kotlin (Retrofit), Swift (URLSession) and TypeScript (fetch) now appear in the graph.