# GEML β€” a plain-text document format built to be edited in place, one section at a time **Category:** πŸ’» Developer Tools **Repository:** https://github.com/geml-spec/geml **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/geml-a-plain-text-document-format-built-to-be-edited-in-place-on ## Description One section in, one section out β€” on Markdown/GEML files, bad writes refused. ## Claude Desktop Quick Installation Heuristic fallback β€” verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low): ```json "mcpServers": { "geml-a-plain-text-document-format-built-to-be-edited-in-place-one-section-at-a-time": { "command": "npx", "args": ["-y","geml-a-plain-text-document-format-built-to-be-edited-in-place-on"] } } ``` ## Documentation & README [![MCP Toplist](https://mcptoplist.com/badge/io.github.geml-spec%2Fgeml.svg)](https://mcptoplist.com/server/io.github.geml-spec%2Fgeml)

GEML

# GEML β€” General Expressive Markup Language [![npm](https://img.shields.io/npm/v/%40geml%2Fgeml?label=npm)](https://www.npmjs.com/package/@geml/geml) [![MCP](https://img.shields.io/badge/MCP-supported-blue.svg)](https://modelcontextprotocol.io) [![CI](https://github.com/geml-spec/geml/actions/workflows/ci.yml/badge.svg)](https://github.com/geml-spec/geml/actions/workflows/ci.yml) [![GEML check](https://github.com/geml-spec/geml/actions/workflows/geml-check.yml/badge.svg)](https://github.com/geml-spec/geml/actions/workflows/geml-check.yml) [![spec: 1.0](https://img.shields.io/badge/spec-1.0-brightgreen.svg)](spec/GEML-spec.md) [![code: MIT](https://img.shields.io/badge/code-MIT-blue.svg)](LICENSE) [![spec license: CC BY 4.0](https://img.shields.io/badge/spec%20license-CC%20BY%204.0-lightgrey.svg)](spec/LICENSE-spec.md) *English | [δΈ­ζ–‡](https://github.com/geml-spec/geml/blob/HEAD/README_CN.md)* GEML is an **Agent-Native** fundamental markup format and protocol, designed for people and AI agents to read and write the same document.
**One format, two readers.** In agent-driven development and knowledge work, plain text and Markdown have no deterministic block boundaries: a program and a model trade the whole file in and the whole file back out β€” at best probing for it with line windows, and restating the original verbatim to rewrite it. Token cost grows with the length of the document, and the operation turns bloated. After a few rounds of rewriting, the copies excerpted elsewhere start to drift. **You can start without changing a thing.** `geml list`, `geml find` and `geml get` address the Markdown you already have β€” nothing is converted, no new files, your `.md` stays `.md`: ```sh geml list README.md # every section, as an address geml get README.md '#key-features' # read ONE section, not the file geml set README.md '#key-features' --body # write one section back geml replace README.md 'old text' 'new text' # swap a string, told which block held it ``` Only that section enters the agent’s context β€” a couple of KB, not the whole ~40 KB file. Need finer than a section β€” one block, one chart, one table? Let `.geml` stand in the middle ground: edit at that grain, and the `--to md` you ship never drifts from it. For people, it is plain text that reads clean; for agents, it is an addressable, verifiable, traceable, revertible **["Doc-as-a-Base"](https://github.com/geml-spec/geml/blob/HEAD/docs/MANIFESTO.md)**. --- **GEML is minimal.** It is plain text β€” still clean with no renderer in sight; one block syntax for the whole language; addressable, verifiable, referenceable structure, natively. Instead of a separate mini-syntax for each kind of content, GEML carries every kind in one container: the typed block. Code is a block. So are tables, diagrams, math, callouts, even metadata β€” and a run of prose can be one too (`=== text`), whenever you want it addressable. Extending it later is just as plain. The shape is the same every time, which makes the language easy enough to learn that it's hard to get wrong. ``` === code {#hello lang=python} print("hi") === ``` ```sh geml get doc.geml '#hello' # by name, just this block ``` Blocks have names so the verbs have somewhere to land β€” the full syntax is in [the format in 1 minute](#one-minute). **Contents:** [What it solves](#problems) Β· [Why now](#why-now) Β· [What's different](#whats-different) Β· [The format in 1 minute](#one-minute) Β· [A gift for programmers](#code-graph) Β· [Get hands-on](#hands-on) Β· [With an LLM](#with-an-llm) Β· [Maturity & versions](#maturity) Β· [The design](#challenge) Β· [Roadmap](#roadmap) Β· [Take part](#contributing) Β· [License](#license) ## What it solves ### Problems solved 1. **Context load and token bloat** * **Status quo**: data formats like JSON/XML carry heavy wrapper tags and syntax symbols; Markdown lacks strict structural metadata and a reference mechanism. * **Approach**: tuned markup density and syntax overhead, reading and writing only the target block β€” context cost no longer grows with document length, keeping **agent reads and writes lightweight**. 2. **AST-level precision and parsing determinism** * **Status quo**: unstructured text degrades over multiple rounds of LLM reads and writes β€” broken formatting, semantic drift, parsing hallucinations. * **Approach**: a deterministic grammar that maps directly to an abstract syntax tree (AST), so programs and LLMs perform atomic block-level create/read/update/delete. 3. **Document copy fragmentation** * **Status quo**: multi-agent collaboration and shared pipelines pass content around by copy-paste, leaving multiple disconnected copies. * **Approach**: **Single Source of Truth** by design β€” standardized module references and data binding eliminate redundant copies and version divergence. ### Key features #### 1. AST-level structured operations * Uniform node definitions; a document parses directly into a typed document tree (AST). * Agents pinpoint the target section, attribute or component; partial patches and idempotent updates replace whole-file rewrites. Writes land as byte splices with whole-document re-validation β€” the tree serves reading and validation, and every untouched byte is guaranteed unchanged. #### 2. Low-token reads and writes * What is saved is not markup characters β€” it is the part never read: `#id` hits one semantically complete block, and the rest never enters the context. * For the same semantics, markedly lower prompt-token cost: better model throughput, lower inference cost. #### 3. Single source of truth, modular references * Native cross-document, cross-fragment component references. * Change the source node once and every reference follows β€” no version skew. #### 4. Robust two-way reads and writes * One block shape for the whole language β€” easy to generate and hard to get wrong, a good match for mainstream LLM output distributions. * A strict validator with precise error locations and actionable repair feedback. ### Comparison | Dimension | Markdown | JSON / YAML | GEML | | :--- | :--- | :--- | :--- | | **Context cost (block-wise I/O)** | High (whole file in and out) | High (whole file + syntax noise) | **Minimal (only the target block)** | | **Precise AST operations** | Weak (no strict semantic nodes) | Strong | **Strong (built for agent reads and writes)** | | **Human readability** | High | Medium | **High** | | **Single-source references** | Unsupported | Needs protocol extensions | **Native (modular embeds)** | | **Write safety** | Weak | Medium | **Strong (a bad write is refused before landing + single-block revert)** | --- ## Why the LLM era needs a brand-new text format Because **both the producer and the consumer of a document have changed**. In traditional software engineering, a document was either a static explanation for people to read, or a serialized data file for programs. Today, people and AI agents collaborate on the same document at high frequency. When the agent becomes the document's "second reader and co-author", the old balance breaks for good: 1. **Context is scarce compute**: every whole-document read or write burns an agent's limited attention window and reasoning budget; 2. **Human–machine collaboration needs an isomorphic carrier**: people need to read it at a glance, agents need to read and write it precisely, block by block; 3. **Knowledge must have a single source of truth**: scattered prompts and copy-pasted Markdown are destined to decay with every iteration. Yet none of our existing text infrastructure was designed for this scene: * **Markdown (typeset for people)**: no stable structural blocks, no machine keys. To change one parameter, an agent must read and write the whole text β€” **wasting context budget** across multi-turn loops, and inviting drift in both format and meaning. * **JSON / XML (serialized for machines)**: full of wrapper syntax and structural noise β€” blocking natural human reading, while quietly eating expensive tokens in long contexts. * **Scratch memory and scattered files (no single source of truth)**: context is torn across chat history and Markdown copies everywhere; a copy is drift from the moment it is made, and version skew and hallucinated distortion follow. The root of all three failures is each tool's own virtue: Markdown's "never error, write anything" is what gives people their freedom to write β€” and exactly why a machine cannot trust the structure it reads back; JSON/XML's strict schema is what gives machines their certainty β€” and exactly why nobody writes prose in it. **The virtue is the defect, which is why patches cannot fix this**: bolting "a broken reference must fail the build" onto Markdown betrays its contract, and stripping the wrapper syntax from JSON denies its nature. When people and agents start co-writing the same text at high frequency, what is needed is not a compromise between the two poles, but a format that treats "readable by people" and "operable by machines" as **one design constraint from day one**. ### The answer: **["Doc-as-a-Base"](https://github.com/geml-spec/geml/blob/HEAD/docs/MANIFESTO.md)** GEML invents no heavy new runtime. Borrowing from the **[REST](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)** architectural style of Dr. Roy Fielding's dissertation, it gives plain-text documents one standard set of operational semantics: | Old pain | The matching capability (the four laws) | What it buys developers and agents | | :--- | :--- | :--- | | **Changing one spot means rewriting the whole text** | **The Law of Addressing** | Every block carries an `#id`; `get/set` reads and writes that block alone. **What is never loaded cannot be broken** β€” the context window stays yours. | | **Copies everywhere, all drifting** | **The Law of Projection** | `=== embed` evaluates dynamically instead of copy-pasting; one definition at the source ends the labor of syncing copies. | | **Bad formats / broken references pollute downstream** | **The Law of Validation** | References and syntax are checked at build time; **a bad write is stopped before it lands**, with no waiting for human review. | | **One bad edit forces a whole-file rollback** | **The Law of Rollback** | The companion `.gemlhistory` reverts **a single block atomically** β€” no tearing down the page; a lightweight version safety net for agents. | > **A document no longer needs just a format β€” it needs a set of verbs.** GEML keeps plain-text readability and adds deterministic block-level operations. > πŸ’‘ **Deep Dive:** > If you are interested in the dilemma of engineering documents in the LLM era and why we need to redesign a plain-text format from the ground up, read our full article on the blog: [**"Why Do We Need a New Text Format in the Era of LLMs?"**](https://geml-spec.github.io/geml/blog/2026/08/03/why-do-we-need-a-new-text-format-in-the-era-of-llms/) --- ## What's different about GEML GEML stays small on purpose β€” the thinking, what it refuses, and what is still open are in [how we thought about the design](#challenge). The four capabilities were established a chapter ago β€” addressing, projection, validation, rollback. This chapter is where each format lands against them, and where GEML draws its boundaries. ### How other formats compare Each of the four has mature solutions in its own field; what's unusual is meeting all four in one plain-text format: | Family | What the state really is | Addressable / referenceable | Projectable / embeddable | Verifiable | History / traceability | | :--- | :--- | :--- | :--- | :--- | :--- | | **Word / Docs** | Opaque state | ❌ No block-level keys; access via platform APIs | ❌ Copy-paste only | ❌ No checking at all | ⚠️ Platform server-side, not in the file | | **Markdown / AsciiDoc** | A stream of characters | ⚠️ Heading anchors or dialect ids; no read/write verbs | ⚠️ Dialect embeds (Obsidian `![[…]]`, `include::`) β€” break silently | ❌ Broken links fail silently | ❌ None in-format β€” external git required | | **JSON / XML** | Data serialization | βœ”οΈ (id / schema) | ⚠️ XML only (XInclude, external) | βœ”οΈ Via an external toolchain | ❌ None in-format β€” external git required | | **GEML** | **Plain text + block structure** | **βœ”οΈ A unique `#id` per block (referenceable natively)** | **βœ”οΈ `=== embed`: a reference is a lookup (native)** | **βœ”οΈ A build-time error** | **βœ”οΈ `.gemlhistory` next to the file (traceable natively)** | Item by item: [vs. CommonMark](https://github.com/geml-spec/geml/blob/HEAD/docs/comparisons/GEML-vs-CommonMark.md) Β· [vs. XML and JSON](https://github.com/geml-spec/geml/blob/HEAD/docs/comparisons/GEML-vs-XML-and-JSON.md) Β· [a 7-format capability matrix](https://github.com/geml-spec/geml/blob/HEAD/docs/comparisons/COMPARISON.md). Coexisting with Markdown: GEML is the **editing source of truth**, Markdown is the delivered artifact. Project one way with `geml --to md|html` and ship `.md` or `.html` as before. **Collaboration, not lock-in.** *(Projection is lossy: block ids and table-bound charts don't survive it.)* **Don't take the table's word for it β€” re-run it.** This is what I asked the model: > Based on your own experience editing the READMEs just now, describe the command steps you go through on a document (I saw you using grep and such), and whether you cache documents to save tokens β€” let's compare, and from that see which parts of GEML would actually earn their place. What came back: **[what one edit costs](https://github.com/geml-spec/geml/blob/HEAD/docs/benchmarks/addressing-cost.md)** and **[a real day replayed](https://github.com/geml-spec/geml/blob/HEAD/docs/benchmarks/mixed-toolchain.md)**. Paste the question to your own model and see what it tells you. PS: I am still trying to work out whether the upstream chain (who calls this) and the downstream chain (what it calls) that `codemap` produces can pin down functions and call sites β€” and change project code β€” the same way. I will post a report when I have one. ## The format in 1 minute ### Typed blocks **One shape, every type.** A block's basic syntax is `=== type [attributes]` … `===` (where attributes like `{#id .class key=val}` are optional) β€” only the `type` (and how its body is read) changes: ``` === code {lang=python} print("hi") === === note {.intro} Parsed prose with *emphasis* and a [[#budget]] reference. === === meta title = "Budget plan" === ``` A run of `=` (three or more) opens a block; an equal-length run closes it; longer fences nest inside shorter ones. A block that carries an `#id` can also close with the **labeled fence** `=== #id` β€” no fence-length counting, which makes long blocks much harder to get wrong (nesting still requires a longer outer fence: a same-length bare `===` in the body closes the block early, labeled or not). The type decides how the body is read β€” `raw` (verbatim: `code`, `diagram`, `math`, `table`), `flow` (parsed prose with inline markup: `note`, `text`), or `data` (one `key=val` per line: `meta`); `embed` carries no body at all β€” its `src=` names the block it stands for β€” and every block may carry an attribute object `{#id .class key=val}`, where a `.class` is a *semantic* label, never a styling hook. The full inline grammar (emphasis, links, `[[#id]]` auto-references, media, footnotes, inline `$math$`) is in the [spec](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec.md). ### Tables β€” two bodies, one model Write a table visually: ``` === table {#budget caption="Annual cost"} | Plan | Months | Rate | |-------|-------:|-----:| | Basic | 1 | 30 | | Pro | 2 | 30 | === ``` …or as data. A table holds the facts; a **`view`** over it derives the **computed columns** and the **summary row**: ``` === table {#fy25 format=csv header=1} Segment, Q1, Q2, Q3, Q4 Cloud, 8, 10, 12, 14 Platform, 5, 6, 7, 9 Services, 3, 4, 4, 5 === === view {#fy25-report src=#fy25 compute="FY [%.1f] = Q1 + Q2 + Q3 + Q4; n = 1" summary="Segment = 'Total'; FY [%.1f] = sum(FY); n = sum(n)"} === ``` *Both table forms describe the same model. The `FY` column and `Total` row are computed at build time, by the view:* | Segment | Q1 | Q2 | Q3 | Q4 | FY | n | |-----------|---:|---:|---:|---:|-----:|--:| | Cloud | 8 | 10 | 12 | 14 | 44.0 | 1 | | Platform | 5 | 6 | 7 | 9 | 27.0 | 1 | | Services | 3 | 4 | 4 | 5 | 16.0 | 1 | | **Total** | | | | | **87.0** | **3** | `compute` runs `+ - * / ( )` per row over columns; `summary` adds a foot row from the aggregates `sum / avg / min / max / count` (with arithmetic over them, e.g. weighted ratios); a trailing `[printf]` sets numeric display. `n` above is the row-count idiom β€” `count` tallies non-empty cells in one column, so a constant column summed is what counts rows. Tables can also pull their data from an external CSV via `src="https://raw.githubusercontent.com/geml-spec/geml/HEAD/regions.csv"`. > ❓ **Up for discussion:** should computed columns and the summary row stay? [Keep, freeze, or drop β€” say which](https://github.com/geml-spec/geml/discussions/19). ### Math ``` === math {#gauss caption="Gaussian integral"} \int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi} === ``` $$\int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi}$$ ### Diagrams & charts β€” host a DSL, or chart a table GEML never interprets a diagram body; it routes it to a pluggable renderer (an unknown `format` is a warning, body preserved): ``` === diagram {#flow format=mermaid caption="Review flow"} graph LR A[Draft] --> B{Review} -->|ok| C[Publish] === ``` ```mermaid graph LR A[Draft] --> B{Review} -->|ok| C[Publish] ``` A diagram can also **chart a table** β€” single source of truth, with the column references checked at build time and no data copied: ``` === diagram {format=geml-chart data=#fy25-report type=bar x=Segment y=FY} === ``` *Drawn from the `#fy25-report` view above β€” `FY` is a computed column, so the chart binds to the view that derives it, not to the base table:* ```mermaid xychart-beta title "FY by segment" x-axis [Cloud, Platform, Services] y-axis "FY" bar [44, 27, 16] ``` ### Data β€” a value, not just text Every block type names what it holds: `code` a region of code, `table` a grid, `math` a formula. `data` holds a **data value**, and it is where the data formats live β€” `json` (the default), `jsonl`, and `yaml` for a declared subset; `toml` reserved. Being typed means the body is read, not just displayed: a missing comma fails the build, `geml get --json` returns the value itself, and a chart can read it directly. ``` === data {#log format=jsonl} {"ts":"09:00","p95":41} {"ts":"09:10","p95":58} === ``` A `jsonl` body holds one record per line, which a program can blind-append at end-of-file. Records can also stay in their own file: `src=ops/latency.jsonl#L900-999` names the file and, optionally, a line window β€” so the log keeps being appended and tailed as before, while the document is its **verified, addressable, chartable view** of it. ### Embeds β€” a dynamic reference, not a copy One block can stand for another: in the same document by `src=#id`, across documents by `src=other.geml#id`. An embed is a **dynamic lookup** of the source at render time β€” change the source once and every embed follows; delete it and `geml check` fails the build on the spot. ``` === embed {src=#fy25} === ``` The body stays empty; the target lives in `src=`. Markdown can't show you the projection. To see it live: install the [browser extension](https://chromewebstore.google.com/detail/opmhfphgoidpnipphfgkhhjhmnmaenie), open the [raw link to sample.geml](https://raw.githubusercontent.com/geml-spec/geml/main/playground/sample.geml), and scroll to the **Transclusion** section β€” a same-document projection (`src=#roadmap`), cross-document projections, and even chained resolution (an embed pulls a chart, which itself binds to a table in another file) all render in place: nothing is written there, yet edit the source once and the projection follows. ## A gift for programmers β€” geml-code-graph To test GEML's expressive power and flexibility β€” and above all to see whether block-level bidirectional linking holds up β€” let's try it on a code graph, a familiar but demanding case for programmers: **your whole codebase's call graph, written as GEML.** `geml codemap build` lays the call graph out as a tree of GEML documents β€” every method an `#id` block, with `#calls` / `#called-by` edges both ways. The **downstream chain** (what a method calls) for troubleshooting, the **upstream chain** (who calls it) for the blast radius β€” all visible in a second; ![The method graph of geml-parser/render.ts: hovering RenderCtx.inline lights up its whole caller chain while everything else dims; clicking a node opens its source right beside the graph](https://raw.githubusercontent.com/geml-spec/geml/HEAD/docs/assets/codemap-render-ts.gif) ```sh npm i -g @geml/geml geml codemap build # --root defaults to . : detect languages -> index -> one merged graph in ./.geml-code-graph/ geml codemap serve # opens your browser on the graph ``` > [!NOTE] > **Requirements.** Node **22+** for the CLI (`npm i -g @geml/geml`). Everything > below is optional and used only where noted: [Joern](https://docs.joern.io/installation) > for non-TS/JS languages in the code graph, and Chrome for the > [viewer extension](https://chromewebstore.google.com/detail/opmhfphgoidpnipphfgkhhjhmnmaenie). > [!TIP] > **TS/JS** β€” zero setup: `build` fetches the scip indexer by itself. > **Java / C / Python / Go / Kotlin** β€” one extra download, [Joern](https://docs.joern.io/installation): unzip its release package and pass that folder to build, e.g. `--joern ~/joern/joern-cli` (`--joern C:\joern\joern-cli` on Windows), or put it on PATH and skip the flag. > Mixed front-end + back-end repo β€” everything merges into **one graph**. geml-code-graph is itself a diagram format β€” one line embeds it in any GEML document (`=== diagram {format=geml-code-graph src=.geml-code-graph/index.geml} ===`), and an optional per-commit hook (bundled with the Claude skill) rebuilds it as the code moves, so the graph doesn't drift. Scale is measured, not promised: on Apache Flink's codebase β€” **13,585 Java source files, ~81,000 methods, 266,821 call edges** β€” the plain-text *data tables* still open and query instantly, and you can grep any method name to trace its call chain. Reproduce it yourself: clone `apache/flink` and run `geml codemap build --joern …` at its root. ## Next β€” get hands-on now β–Ά **[Try writing GEML in the Playground](https://geml-spec.github.io/geml/playground/)** β€” edit on the left, rendered live on the right, and the build verdict flips red the moment a reference breaks. No install, nothing to read first. Then, in the order that suits you: 1. **See it render in your browser.** Install the **[extension](https://chromewebstore.google.com/detail/opmhfphgoidpnipphfgkhhjhmnmaenie)** and open a raw `.geml` link *(the raw file, not the GitHub blob page β€” that one is HTML)*: the **[GEML spec itself](https://raw.githubusercontent.com/geml-spec/geml/main/spec/in_geml_format/GEML-spec.geml)** (dogfood β€” the spec is a GEML document, rendered at scale), the **[showcase](https://raw.githubusercontent.com/geml-spec/geml/main/playground/showcase.geml)** (a computed table, four charts, a Mermaid flow, and math), or **[playground/sample.geml](https://raw.githubusercontent.com/geml-spec/geml/main/playground/sample.geml)** for the interactive code-graph. 2. **Run it locally.** `npm i -g @geml/geml` (Node 22+), then `geml check` a document, or point it at your own repo with `geml codemap build`. 3. **Set up Claude Code β€” one command.** `npx -y @geml/geml skill install` puts the authoring skill, the CLI and the MCP server in place, user-global, for every project. It edits no settings and installs no hooks. [Details](#with-an-llm). 4. **Read the grammar.** The **[full spec](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec.md)** (EN / [δΈ­ζ–‡](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec_CN.md)) is normative and short enough to read in a sitting. 5. **Or see it worked through, rule by rule.** **[GEML, illustrated](https://github.com/geml-spec/geml/blob/HEAD/docs/illustrated/README.md)** (EN / [δΈ­ζ–‡](https://github.com/geml-spec/geml/blob/HEAD/docs/illustrated/README_CN.md)) β€” eleven self-contained pages, one per block type, per profile, and for the CLI: GEML on the left, what the processor *actually* does on the right (`geml check` diagnostics, `geml list` addresses, `--to html` markup), each rule tagged with its source and status. ## Using GEML with an LLM The goal is one thing: your model **edits a block at a time, and verifies** β€” never re-reads and re-emits a whole file to change one paragraph. Getting there takes one step, and which step depends on what you use. ### Using Claude Code β€” run this ```sh npx -y @geml/geml skill install ``` It installs the authoring skill, the `geml` CLI and the MCP server, user-global, for every project. No `settings.json` edits, no hooks; re-run after an upgrade. *(Prefer plugins? `claude plugin marketplace add geml-spec/geml`, then `/plugin install geml@geml` β€” same skill, MCP server bundled.)* ### Using DeepSeek Harness β€” add this bundle The same setup, packaged as a dsh bundle β€” the geml MCP server plus the authoring and code-graph skills: ```sh dsh plugin --profile web add @geml/dsh-plugin # web = the profile dsh boots by default; use your own profile name if you run another ``` Listed on [dshmarket](https://dshmarket.com/p/geml-spec/geml--integrations-dsh-plugin/) and [awesome-dsh-plugin](https://awesome-dsh-plugin.com/p/geml-spec/geml--integrations-dsh-plugin/); source in [integrations/dsh-plugin/](https://github.com/geml-spec/geml/blob/HEAD/integrations/dsh-plugin/). ### Using Codex β€” install the plugin The same payload once more, packaged for Codex: both skills, the MCP server, and a `SessionStart` hook. Start Codex in a checkout of this repo and it shows up in `/plugins` (the marketplace source is committed at `.agents/plugins/marketplace.json`); to add it without cloning, the `git-subdir` entry is in [integrations/codex-plugin/](https://github.com/geml-spec/geml/blob/HEAD/integrations/codex-plugin/). Then say it once in a session, and the project has switched: > This project uses GEML as its base document format; generate other formats > from it as needed. ### Using anything else β€” paste this, then check the output A model with no skill to read needs the rules once. Paste the prompt below, and keep `geml check` as the gate on whatever it writes back β€” the CLI is `npm i -g @geml/geml` (Node 22+). > Write the document as GEML: every block is `=== type [attributes]` … `===` > ([the format in 1 minute](#one-minute) lists the types). Four rules are the > ones models get wrong: the closing fence is a `=` run of the *exact* opening > length, and a body containing `===` needs a longer outer fence; headings are > ATX `#` only, with no `---` frontmatter (metadata is `=== meta`); every `#id` > is unique and every reference (`[[#id]]`, `[text](#id)`, `[^id]`, `data=#id`) > must resolve; there is no raw HTML. The normative spec is > [`GEML-spec.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec.md). ### What it will do with it ```sh geml list doc.geml # CALL FIRST: every block, its address, kind, lines geml find "words" doc.geml # search block content -> an address, not a line number geml get doc.geml '#hello' # read ONE block (a heading id = its whole section) geml get doc.geml '#hello' --intro # a section cuts three ways: --head | --intro | --body geml set doc.geml '#license' --in template.geml#mit # replace that block, forking another geml add doc.geml --after '#intro' --in snippet.geml # insert a fragment (keeps its own ids) geml revert doc.geml '#plan' --rev -1 # roll ONE block back geml check doc.geml # validate only: diagnostics + exit code ``` Any section cuts three ways, on `get` and `set` alike: `--head` is the heading line, `--intro` what it says before its first subheading, `--body` everything under it β€” so `--body` always contains `--intro`, and equals it when there is no subheading. A section's opening can be edited without pulling its subsections into context. Every mutation is re-parsed before it writes and refused if it would break the document β€” which is what makes editing unattended safe. The rest of the verbs (`delete`, `rename`, `history`, `--to md|html|geml` conversion, addressing a block by type or content hash) are in the [parser README](https://github.com/geml-spec/geml/blob/HEAD/geml-parser/README.md). ### MCP Server A standard Model Context Protocol server ships with the package, so your agent edits **one block at a time** instead of rewriting whole files β€” on Markdown and GEML alike. It runs locally on Windows, macOS, and Linux; `--root` is the directory the server is confined to (use `.` or `${workspaceFolder}` to bind to the active project). **Claude Code** β€” one-command setup (installs skill, CLI, and MCP server): ```sh npx -y @geml/geml skill install ``` *(Or register manually via CLI: `claude mcp add --scope user geml -- npx -y @geml/geml mcp --root .`)* **Cursor** β€” add `.cursor/mcp.json` to your project: ```json { "mcpServers": { "geml": { "command": "npx", "args": ["-y", "@geml/geml", "mcp", "--root", "${workspaceFolder}"] } } } ``` *(Or in Cursor Settings β†’ Features β†’ MCP: name `geml`, command `npx -y @geml/geml mcp --root .`)* **Claude Desktop** β€” add to `claude_desktop_config.json`: ```json { "mcpServers": { "geml": { "command": "npx", "args": [ "-y", "@geml/geml", "mcp", "--root", "/absolute/path/to/your/docs" ] } } } ``` Then just ask for the change you want β€” "fix the Q3 row in the FY26 table" β€” and the agent addresses that one block. You never learn a tool name: each mirrors a CLI verb (`geml set` β†’ `geml_set`), so one vocabulary covers the terminal and the agent. Two guarantees make this better than letting a model rewrite the file: a write is parsed **before** it reaches disk and refused with its diagnostics if it would break the document, and every write first records a `.gemlhistory` revision β€” so a bad edit is both *prevented* and *undoable* (`geml_revert` restores one block, the rest of the file byte-identical). Paths stay confined to `--root`, which a client cannot widen. Point `--root` at a repository that has a code graph (`geml codemap build`) and the same server also answers "who calls this" β€” four read-only `geml_codemap_*` tools, one client entry instead of two. Every tool and option: [docs/mcp-guide.md](https://github.com/geml-spec/geml/blob/HEAD/docs/mcp-guide.md). ## Ecosystem and maturity GEML is a small, young spec β€” but a **stable** one: **`1.0`** is released and usable for real documents (this repo's own spec is one), with a strict conformance suite, a reference implementation that passes it **(versioned independently of the spec)**, and an open proposal process. There is **one** specification, and it is bilingual. The `.gemlhistory` sidecar is defined by the `geml-history/v1` **profile** β€” an application layer on top of the spec rather than part of it, which is also why it is MIT and the spec is CC-BY ([`LICENSE-spec.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/LICENSE-spec.md) says why): | Document | English | δΈ­ζ–‡ | |----------|---------|------| | The specification | [`GEML-spec.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec.md) | [`GEML-spec_CN.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/GEML-spec_CN.md) | | `geml-history/v1` profile | [`geml-history-profile.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/profiles/geml-history/geml-history-profile.md) | [`geml-history-profile_CN.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/profiles/geml-history/geml-history-profile_CN.md) | Every profile this project publishes: [`spec/profiles/`](https://github.com/geml-spec/geml/blob/HEAD/spec/profiles/README.md). ### Versions and compatibility - **Self-hosting** β€” [`GEML-spec.geml`](https://github.com/geml-spec/geml/blob/HEAD/spec/in_geml_format/GEML-spec.geml) is the specification written in GEML, required to parse clean on every test run. - **A [conformance suite](https://github.com/geml-spec/geml/blob/HEAD/geml-parser/test/conformance/)** is what holds separate implementations compatible. - **A reference implementation of the parser.** **1,300+** unit tests today, plus the conformance corpus, round-trip serialization and end-to-end CLI runs, with coverage CI-gated at β‰₯**95%** lines / statements / functions / branches. - **Forward compatibility is in the grammar.** A processor must degrade gracefully on constructs it does not recognize (spec Β§8.2), which is why adding a block type or a diagram format is **not** a breaking change. The type registry is open: an unregistered type name should contain a hyphen (`acme-invoice`), leaving hyphen-free names to future versions of the spec (Β§8.5). - **Claiming conformance.** An implementation may call itself *conformant to GEML 1.0* once it reproduces the conformance suite case for case (Β§8.5). No permission needed, and no sign-off from this repo. - **On the wire.** Extension `.geml` (version sidecar `.gemlhistory`), media type `text/geml`, or `text/vnd.geml` where a registered type is required β€” `text/geml` is not registered with IANA yet. - A fragment identifier on a `.geml` URL names the block bearing that id (Β§0.6) β€” which is not what `#tag` means on an HTML page. ## How we thought about the design ### What the design follows **It is plain text meant for people to read.** Fully readable with no renderer β€” which is why there is no raw-HTML escape hatch, and why a style may never change what a document says. **One primitive, a few models.** Every kind of content is the same typed block; extending the format means **registering a type, not inventing syntax**. The type says what it **becomes**: `meta` is key–value shared across the document, `code` is a region of code at a location, `data` is a data value, `table` is a grid waiting to be worked, `diagram` is a hosted external DSL, `embed` is a view onto a source of content **A reference is a window, not a navigation.** An HTML link navigates: the target is not in the document you are holding, so people copy it in anyway. What is being designed out is not dead links; it is the incentive to copy. *Cost: rendering may need to read several files, and must degrade gracefully when it can't.* **Prefer subtraction.** Where a rule breeds edge cases, the feature goes rather than the edge cases getting specified: no underscore emphasis, no setext headings, no indented code blocks, no raw HTML. The ambiguity is deleted at the source instead of enumerated in test cases. *Cost: some things you can write in Markdown you cannot write here.* **No broken windows.** Markdown's ethos is never to fail β€” render something. GEML's is the opposite: verified at build time rather than tolerated at render time. A dangling `#id` is an error with a non-zero exit. Stable ids, `geml check` and the diagnostic catalogue all follow from that one decision. *Cost: a document that "looks fine" can fail your build.* **A sidecar travels with the document without getting into it.** The `.geml` file is the source of content and stays deliberately small. Anything else is not pushed into it but points back at it β€” a version history in `.gemlhistory`, say β€” and deleting that leaves the document perfectly valid. *Cost: a convention, explicit or implied, and two files that travel together.* **The command line is built for an agent.** The fewest verbs that cover everything, kept orthogonal, with pipeable input and output and options that stay consistent across them. ### What it therefore refuses | Refused | Why | |---|---| | A diagram language of its own | External DSLs are hosted (Mermaid, Graphviz, D2, …); the format defines only the hosting protocol | | A raw-HTML escape hatch | Semantics stay portable, tied to no backend or renderer | | Setext headings / `---` frontmatter | ATX `#` only, so nothing collides with a thematic break | | A full spreadsheet engine | Per-row formulas and summary aggregates are enough; no cell addressing, lookups, or macros | ## Roadmap - [x] The GEML `1.0` specification, in English and Chinese, with a conformance suite β€” plus the `geml-history/v1` profile that defines the `.gemlhistory` sidecar - [x] Reference implementation `@geml/geml`: parser, CLI, block-level `.gemlhistory` tracking - [x] Official MCP server (`geml mcp`) for Claude Code, Cursor, Codex and other MCP hosts - [x] codemap β€” a whole codebase's call graph, written as GEML - [x] Ecosystem integrations: VS Code highlighting and reference checking, tree-sitter, Obsidian, Logseq (two-way sync against a live DB graph), the browser viewer, a GitHub Action, LangChain / LlamaIndex, and the agent-harness plugins β€” Claude Code, Codex, Grok, DeepSeek Harness, plus root manifests for Gemini CLI and Kimi Code - [ ] The Logseq plugin listed in the Logseq marketplace ([PR #893](https://github.com/logseq/marketplace/pull/893)) and the Grok plugin listed in `xai-org/plugin-marketplace` - [ ] The VS Code extension on the Marketplace - [ ] Parsers in other languages (Rust / Python) β€” the spec and the conformance suite are public, so community implementations are welcome; we are glad to help line them up --- ## Take part GEML is `1.0`, but "stable" means **the rules already there won't shift under you**, not that the design is settled. There is exactly **one implementation** so far, and **one set of opinions** behind the spec. Your thinking can still change the spec itself. If you want a hand in it: **Come argue about these**: - [Should the format keep computed columns and summary rows?](https://github.com/geml-spec/geml/discussions/19) - [If styling is supported, how should it be designed?](https://github.com/geml-spec/geml/discussions/17) - [Is the GEML history file a made-up need?](https://github.com/geml-spec/geml/discussions/18) - [`--view` reads through an embed. Flag, or its own verb?](https://github.com/geml-spec/geml/discussions/21) Or **claim a piece**: | Gap | Where it stands | What it takes | |---|---|---| | **Skill installation for more agent tools** | Gemini CLI, Qwen Code and AGENTS.md are installed by detection already; the MCP server works with any client | Add the rest the same way: **Cursor**, **GitHub Copilot**, **Cline** β€” their rule-file conventions move fast, so check the current docs before writing one in | | **How well the primer holds on other models** | Only exercised on Claude | Have GPT / Gemini / a local model each write a batch of GEML from the primer, count how many pass `geml check` first time, and report the rules they keep getting wrong β€” those are the ones the primer should name | | **Deeper Obsidian integration** | Renders, but not in the community store yet | Editing at the CodeMirror layer and seamless two-way rendering, plus the store submission itself. Wants someone who knows the Obsidian API. | | **The viewer on other browsers** | Chrome works | Firefox / Safari ports. | | **Packaging the RAG integrations** | LangChain / LlamaIndex are reference implementations | Publishing to PyPI; and wiring up other frameworks (Haystack, DSPy, …). | - **Write a second implementation of the spec** β€” a new GEML parser in whatever language you like ([how to write a parser](https://github.com/geml-spec/geml/blob/HEAD/docs/WRITING-A-PARSER.md)) - **Finding the places where the spec is ambiguous is itself the contribution**, whether or not that parser ever ships. Or **propose something new**: - A GEP: the proposal, the spec edit and the conformance cases land together ([process](https://github.com/geml-spec/geml/blob/HEAD/spec/proposals/README.md)) Or **put it to use**: | Scenario | Where | State | |---|---|---| | **From the command line** β€” validate, convert, edit by block, version history, all in one command | [`@geml/geml`](https://www.npmjs.com/package/@geml/geml) (source [`geml-parser/`](https://github.com/geml-spec/geml/blob/HEAD/geml-parser/)) | Available | | **Read it in the browser** β€” open any raw `.geml` link and it renders in place: computed tables, charts, Mermaid, math, with diagnostics as a banner | [Chrome Web Store](https://chromewebstore.google.com/detail/opmhfphgoidpnipphfgkhhjhmnmaenie) Β· [source](https://github.com/geml-spec/geml/blob/HEAD/integrations/geml-viewer/) | Available | | **Let an agent edit by block** β€” an MCP server; the agent changes one block instead of rewriting the file, and every write is validated before it reaches disk | [`docs/mcp-guide.md`](https://github.com/geml-spec/geml/blob/HEAD/docs/mcp-guide.md) | Available | | **Use it from DeepSeek Harness** β€” the geml MCP server plus the authoring and code-graph skills, one installable bundle | [`@geml/dsh-plugin`](https://www.npmjs.com/package/@geml/dsh-plugin) Β· [dshmarket](https://dshmarket.com/p/geml-spec/geml--integrations-dsh-plugin/) Β· [source](https://github.com/geml-spec/geml/blob/HEAD/integrations/dsh-plugin/) | Available | | **Use it from Codex** β€” the same payload again: both skills, the MCP server, and a `SessionStart` hook, installable from `/plugins` | [`integrations/codex-plugin/`](https://github.com/geml-spec/geml/blob/HEAD/integrations/codex-plugin/) | Available from this repo; not in the public plugin directory yet | | **Use it from Grok** β€” the same payload once more: both skills and the MCP server | [`integrations/grok-plugin/`](https://github.com/geml-spec/geml/blob/HEAD/integrations/grok-plugin/) | Available from this repo; the `xai-org/plugin-marketplace` PR is not opened yet | | **Sync a Logseq graph to plain text** β€” a Logseq 2.0 DB graph as continuously synced GEML files, addressable and git-friendly, with `restore` as the way back | [`@geml/logseq-sync`](https://www.npmjs.com/package/@geml/logseq-sync) Β· [source](https://github.com/geml-spec/geml/blob/HEAD/integrations/logseq/) | Watcher on npm; the plugin installs from a release zip β€” the marketplace listing ([PR #893](https://github.com/logseq/marketplace/pull/893)) is not merged yet | | **Turn a codebase into a document** β€” the whole call graph as a tree of GEML documents, browsable | `geml codemap build` ([design](https://github.com/geml-spec/geml/blob/HEAD/docs/design/specs/geml-codemap/DESIGN-geml-code-graph.md)) | Available | | **Write it in your editor** β€” syntax highlighting + build-time reference checking | [`integrations/vscode/`](https://github.com/geml-spec/geml/blob/HEAD/integrations/vscode/) | Built β€” install from source; not on the Marketplace yet | | **Render it in Obsidian** β€” the reference parser + the viewer's renderer, the same code path as the web | [`integrations/obsidian/`](https://github.com/geml-spec/geml/blob/HEAD/integrations/obsidian/) | Built, not in the community store | | **Feed a RAG / agent framework** β€” block-level loaders (one chunk per block, carrying `block_id`) + agent editing tools | [`integrations/langchain+llamaindex/`](https://github.com/geml-spec/geml/blob/HEAD/integrations/langchain+llamaindex/) | Reference implementation | | **Try it without installing anything** β€” edit on the left, live render on the right | [Playground](https://geml-spec.github.io/geml/playground/) | Available | Three files to read first: [`GOVERNANCE.md`](https://github.com/geml-spec/geml/blob/HEAD/GOVERNANCE.md) for how decisions get made, [`CONTRIBUTING.md`](https://github.com/geml-spec/geml/blob/HEAD/CONTRIBUTING.md) for how to send work, and [`CODE_OF_CONDUCT.md`](https://github.com/geml-spec/geml/blob/HEAD/CODE_OF_CONDUCT.md) for the one rule about people β€” disagree with the design as sharply as you like, not with the person. ## Repository layout ``` spec/ The specification as .md (EN / δΈ­ζ–‡) and the CC-BY spec license, with profiles/ (application layers β€” geml-history, geml-codemap, geml-style, geml-form) and proposals/ (GEPs), both MIT spec/in_geml_format/ The dogfood: the specification written in GEML, with its .gemlhistory sidecar geml-parser/ Reference parser, renderer, CLI + codemap toolkit (TypeScript, Node 22) integrations/ Everywhere GEML plugs in: geml-viewer (browser extension), geml-check-action (CI), vscode, obsidian, logseq (two-way vault sync + the watcher), tree-sitter (brief), langchain+llamaindex (RAG loaders), windows-icon (Explorer file icons), and the agent-harness plugins β€” claude-plugin, codex-plugin, grok-plugin, dsh-plugin .agents/, .claude-plugin/ Plugin marketplace manifests, so the plugins show up from a checkout (Codex `/plugins`, Claude Code `/plugin`) playground/ In-browser playground (+ a live geml-code-graph of this repo) docs/ Guides, design notes, comparisons/ (COMPARISON + vs-CommonMark + vs-XML-and-JSON), assets (logos, used by the Pages site below), and an example .geml to render .claude/skills/ Claude skills: GEML authoring, and the code graph .github/ CI + geml-check workflows, MCP registry publish, and issue templates (bug, GEP, new implementation) site/ The geml-spec.github.io/geml Pages site: a project homepage (index.md) plus a Jekyll blog (blog/, posts in _posts/) β€” the long-form "why a new format" article (EN / δΈ­ζ–‡) lives there as its first post. `cd site && bundle exec jekyll serve` builds it locally; .github/workflows/pages.yml builds and deploys it (grafting in playground/ as static output) on push to main. ``` ## License & governance **Code is MIT** ([`LICENSE`](https://github.com/geml-spec/geml/blob/HEAD/LICENSE)): everything in this repository β€” `geml-parser/`, all of `integrations/`, `playground/`, `.claude/skills/`, the GEPs in `spec/proposals/` β€” except the specification documents. **The specification documents are CC-BY-4.0** ([`LICENSE-spec.md`](https://github.com/geml-spec/geml/blob/HEAD/spec/LICENSE-spec.md), which lists them exactly): `spec/GEML-spec*` and `spec/in_geml_format/*`. There is one specification; the profiles under `spec/profiles/` are application layers and are MIT. A spec is not software, so anyone may build a conformant implementation without permission β€” and call it *conformant to GEML 1.0* once it passes the [conformance suite](https://github.com/geml-spec/geml/blob/HEAD/geml-parser/test/conformance/). **Using the name.** You need no permission to implement GEML, to name an implementation after the format (`geml-rs`, `pygeml`, a `geml` package on your language's registry), or to state that your tool reads and writes GEML. Two requests, neither of them a legal restriction: call an implementation *conformant to GEML 1.0* only once it passes the conformance suite, and don't imply that this project wrote, endorses, or maintains it. Attribution for the specification text itself is what CC-BY-4.0 already asks for.