Free tier available. See plans →
/languages
Maguyva supports 229+ languages and text-based technologies, but not every repo surface needs its own guide. This hub covers the stacks where structure, dependency analysis, and cross-file context materially change how safe an AI-assisted edit will be.
Coverage snapshot
Grouped from the full compatibility manifest so the snapshot reflects all 229 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
Growing coverage
Maguyva supports 229+ languages today. Detailed guides are added as extraction quality reaches the bar — real AST parsing, symbol resolution, and dependency mapping, not just syntax highlighting.