The/Plugins

The core is small. Everything else is a plugin.

File formats, highlighting, themes and tools attach on top of the core through an API in plain C ABI. Build 0.4.3 ships eight plugins — they double as the reference for your own.

Open the SDK Download The

Txplaintextbundled

The base text format: gigabyte files, modes, encodings.

Mdmarkdownbundled

Markdown preview with Mermaid diagrams in the embedded web engine.

Cscsvbundled

CSV and TSV table mode: rainbow columns, pinned header, large line numbers.

Jsjsonbundled

JSON highlighting and structure.

Cpcppbundled

tree-sitter highlighting and smart indentation for C and C++.

Clclangdon demand

Language intelligence over LSP: C/C++ diagnostics, Unreal Engine project support.

Rgripgrepbundled

Project-wide search with results grouped by file.

Gtgitbundled

Change markers, Source Control, per-hunk staging, diff and inline peek (libgit2).

clickable plugin pages will arrive with the catalogue — this is the list from build 0.4.3

management

Switched on with a toggle, no core rebuild.

A plugin attaches to a shipped build of The — no recompiling the editor.
Heavy integrations (clangd, for example) are off by default and enabled on demand.
The core knows nothing about the GUI: a format plugin drags in no interface dependencies.

Plugins— editor

PluginsSettings

Txplaintext text files

Mdmarkdown preview + mermaid

Cscsv table mode

Cpcpp tree-sitter, indentation

Clclangd diagnostics over LSP

Gtgit markers, diff, staging

main↑2✓0⚠07 of 8 enabled

no core rebuildC ABI v1

your own plugin

The API is plain C, not C++.

The boundary between core and plugin is described in terms of C ABI. A boring decision with large consequences: an extension built by a different compiler, or written in a different language, keeps working.

SDK and plugin template Docs

Compatibility across compiler builds
Languages: C, C++, and anything that speaks C ABI — Rust, for example
Extension kinds: formats, highlighting, themes, tools
A ready project template inside the SDK

planned, not now

A plugin store, licensing for third-party extensions and a WASM sandbox for foreign code are plans for after the public release. There are no dates and no prices. For now plugins are installed by hand, and you should only trust the ones whose source you have read.