> For the complete documentation index, see [llms.txt](https://docs.codna.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codna.ai/concepts/languages.md).

# Language support

Codna has two language surfaces. Which one applies depends on the feature.

## Repository intelligence — 250 languages

Understanding a repository, localizing an issue, and building an evidence bundle run on the Algenta engine's repository intelligence, which spans **250 languages**. This drives `codna triage`, the localization step in `codna fix`, and `codna review --triage`. It's server-side; there's nothing to configure.

## On-device memory — the local extractor

Local code memory (`codna_recall` and the `.codna-memory` index — see [Code Memory](/concepts/memory.md)) uses its own extractor, which runs on your machine and supports a focused set of languages:

* **Python** — via the standard-library `ast`.
* **Everything below** — via one generic tree-sitter walk:

| Language   | Extensions                       |
| ---------- | -------------------------------- |
| JavaScript | `.js` `.jsx` `.mjs` `.cjs`       |
| TypeScript | `.ts`                            |
| TSX        | `.tsx`                           |
| Go         | `.go`                            |
| Rust       | `.rs`                            |
| Java       | `.java`                          |
| C          | `.c` `.h`                        |
| C++        | `.cc` `.cpp` `.cxx` `.hpp` `.hh` |
| C#         | `.cs`                            |
| PHP        | `.php`                           |
| Ruby       | `.rb`                            |

The grammars ship with base `codna`, so local memory works across all of these with no extra install. A missing grammar skips that language rather than erroring.

{% hint style="info" %}
Working on a repo with `triage`/`fix`/`review`? That's the 250-language engine. Building or querying `.codna-memory` (e.g. `codna_recall`)? That's the extractor above.
{% endhint %}

## See also

* [Code Memory](/concepts/memory.md) — how the local index is built and queried.
* [How It Works](/concepts/concepts.md) — the understand → localize → bundle → act flow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.codna.ai/concepts/languages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.