> man languages
Maguyva supports 285+ languages and text-based technologies, but not every repo surface needs its own guide. This hub covers the stacks where structure and cross-file context materially change how safe an AI-assisted edit will be, with graph-aware dependency analysis where available.
Coverage snapshot
Grouped from the full compatibility manifest so the snapshot reflects all 285 supported languages and text-based technologies. Start with the featured guides below, then use the full compatibility page when you need the entire long tail.
Polyglot reality
Most production repos blend app code, tests, build scripts, config, SQL, and infra. Language coverage is what keeps agent context from dropping across file boundaries.
Legacy leverage
Older languages are where broad support becomes a modernization tool. Dependency analysis matters more when nobody wants to touch the code.
Quick answers
Each guide covers what Maguyva extracts, what your agent can query, and where the coverage edges are — for your specific stack.
Featured guides
Guides for modern application work, mixed-runtime repos, infrastructure code, and legacy modernization.
Useful when Python codebases sprawl across services, scripts, type stubs, and operational glue.
Extensions
.py, .pyi, .pyw
Relevant when your repo mixes app code, libraries, API clients, tests, and config across multiple packages.
Extensions
.cts, .d.ts, .mts, .spec.ts, +3 more
Useful when a repo mixes CommonJS, ESM, task scripts, tests, and older application code.
Extensions
.cjs, .js, .mjs, .spec.js, +2 more
A good fit for service-heavy repos where handlers, packages, and operational code need to stay easy to trace.
Extensions
.go
Relevant when you want AI assistance in Rust without losing the structural guardrails that make Rust worth using.
Extensions
.rs
Useful when the repo is full of Spring services, internal frameworks, and code that has survived several organizational eras.
Extensions
.java
A good fit when .NET repos have grown large enough that safe AI assistance depends on real structure.
Extensions
.cs, .csx
Relevant when a PHP codebase is still shipping revenue but nobody wants an agent freelancing through it.
Extensions
.php, .php3, .php4, .php5, +2 more
Useful when infrastructure code is part of the repo context and not something the agent should hand-wave past.
Extensions
.tf, .tfvars
This is where broad language support stops being a stat and starts becoming a modernization tool.
Extensions
.cbl, .cob, .cpy
For numerical code that outlived its authors, a call graph is the first piece of documentation.
Extensions
.f, .f03, .f08, .f90, +3 more
Before an S/4HANA move, you need to know what your custom code actually depends on.
Extensions
.abap
Ada was built for systems that must not break. Changing them deserves the same care.
Extensions
.ada, .adb, .ads
Delphi and Free Pascal applications run for decades. Understanding them should not take that long.
Extensions
.pas, .pp
The Perl that still runs your billing, reporting, or deploy scripts deserves better than grep.
Extensions
.perl, .pl, .pm, .pod, +1 more
Kotlin hides a lot of wiring in receivers and lambdas. The graph puts it back.
Extensions
.kt, .kts
In Swift, behaviour lives in protocols and extensions. An agent needs to see both.
Extensions
.swift
Ruby reads like prose. The dependencies behind it still need a map.
Extensions
.gemfile, .gemspec, .rake, .rakefile, +2 more
In C, the call graph is the architecture. An agent should read it before it edits.
Extensions
.c, .h
C++ hides the real call target behind namespaces, overloads, and virtual dispatch. The graph helps an agent find it.
Extensions
.c, .c++, .cc, .cpp, +6 more
Scala packs a lot of meaning into little syntax. The graph unpacks it.
Extensions
.sc, .scala
Flutter apps grow wide fast. The graph keeps the wiring visible.
Extensions
.dart
Lua builds objects out of tables. The graph shows which tables became classes.
Extensions
.lua
Analysis code outgrows its first script. The graph shows what depends on what.
Extensions
.r, .rmd, .rnw
Automation estates sprawl across scripts. The graph shows which function runs what.
Extensions
.ps1, .psd1, .psm1
Build logic is code too. The graph treats it that way.
Extensions
.gradle, .groovy, .jenkinsfile
Elixir's structure lives in macros. The graph reads them as structure.
Extensions
.ex, .exs
Haskell's types say a lot. The graph shows who relies on them.
Extensions
.hs, .lhs
Growing coverage
Maguyva supports 285+ languages today. Detailed guides are added as extraction quality reaches the bar — real AST parsing and symbol resolution, not just syntax highlighting.