DraftLumen Protocol v0, revision 25 (frozen snapshot)Not stable. Breaking changes expected.SourceReport an issue

Lumen Protocol v0, revision 25 (frozen snapshot). © Moonbase 2090 LLC. Licensed under CC-BY-4.0. Report security issues privately via GitHub private vulnerability reporting or [email protected].

Prior art (informative)

SystemLumen borrowsLumen differs
Kitty graphicsImage IDs, chunked transfer, placement kept apart from dataImages are first-class blocks, not cell overlays sent through APC escapes
iTerm2 inline imagesSimple inline images with size hintsNo base64 inside OSC; framed binary payloads instead
Warp blocksCommand plus output as one block that can be selected or foldedBlocks are part of the protocol. Authority frames come only from terminal-owned shell integration; any program can emit inert blocks as unverified output
NotcursesPlanes, compositing, capability detectionThe terminal does the layout; the application does not draw cells
DomTermTerminal as a document; prompt, input and output marks; foldingNo DOM or web engine; a smaller typed schema
JupyterTyped cells, MIME bundles, kernel and front-end splitStreams in real time over a PTY-like channel, not notebook files
Arcan TUIClean break from VT; structured client APIKeeps VT as a native grid block instead of dropping it
OSC 133Prompt, input, output and exit-code semanticsBecomes structured block events sent only as authenticated frames by terminal-owned shell integration. OSC 133 inside grids is visual decoration only