VTX
The terminal, continued.
VTX is a wire protocol for consoles. One connection carries a terminal grid, application components and an AI agent's questions, to a native client, a browser or a plain terminal.
- uri
- vtx://ops.example.net/fleet
- port
- 22100 tcp+udp, or 443
- alpn
- vtx1-d03 · vtxq1-d03
- ws
- /.well-known/vtx/fleet · vtx1-d03
01 01 0C A1 65 62 79 74 65 73 1A 00 01 00 00
- 01
- Channel ID 1 (scene)
- 01
- Frame Type 0x01, CREDIT
- 0C
- Length 12
- A1
- CBOR map, 1 pair
- 65 62 79 74 65 73
- "bytes"
- 1A 00 01 00 00
- 65536
examples/vectors.json and checked against the core specification, Section 3.One op stream, any client
An application writes scene operations as JSON lines. The server sends them as CBOR frames, and the client decides how they look. A client without the component catalog gets the server's text rendering instead, and the application cannot tell the difference.
- {"op":"begin"}
- {"op":"open","id":"ops","type":"region","title":"Agent fleet","catalog":"tag:vtx.foundation,2026:vtx/catalog/core/1"}
- {"op":"data","region":"ops","path":"/fleet","value":{"running":2,"waiting":1,"load":[0.21,0.34,0.62,0.48,0.55]}}
- {"op":"open","id":"title","type":"heading","parent":"ops","text":"Agent fleet","level":1}
- {"op":"open","id":"summary","type":"text","parent":"ops","role":"muted","text":{"fn":"formatString","template":"{running} running, {waiting} waiting","args":{"running":{"bind":"/fleet/running"},"waiting":{"bind":"/fleet/waiting"}}}}
- {"op":"open","id":"top","type":"stack","parent":"ops","dir":"h","gap":2}
- {"op":"open","id":"health","type":"status","parent":"top","state":"warning","text":"1 agent waiting for approval"}
- {"op":"open","id":"cpu","type":"progress","parent":"top","value":0.55,"label":"Fleet load"}
- {"op":"open","id":"trend","type":"chart","parent":"top","kind":"spark","series":[{"name":"load","values":[0.21,0.34,0.62,0.48,0.55]}]}
- {"op":"open","id":"agents","type":"table","parent":"ops","cols":[{"key":"name","label":"Agent"},{"key":"state","label":"State","kind":"status"},{"key":"load","label":"Load","kind":"progress","align":"end"}],"sort":{"key":"state","dir":"desc"},"select":"one","activate":"inspect"}
- {"op":"rows","id":"agents","rows":[["build-07","warning",0.62],["index-02","ok",0.38],["mail-11","ok",0.09]]}
- {"op":"close","id":"agents"}
- {"op":"open","id":"facts","type":"kv","parent":"ops","items":[["Region","eu-west"],["Agents",3],["Updated",{"fn":"formatDate","value":"2026-10-11T03:53:00Z","style":"short"}]]}
- {"op":"open","id":"events","type":"log","parent":"ops","max":500,"follow":true}
- {"op":"commit"}
- {"op":"append","id":"events","lines":["03:53:11 build-07 waiting for approval: systemctl restart nginx"]}
- {"op":"rows","id":"agents","rows":[["build-07","ok",0.41]],"at":0,"replace":1}
- {"op":"patch","id":"health","set":{"state":"ok","text":"All agents running"}}
- {"op":"data","region":"ops","path":"/fleet/waiting","value":0}
Agent fleet
2 running, 1 waiting
| Agent | State ▾ | Load |
|---|---|---|
| build-07 | warning | 62% |
| index-02 | ok | 38% |
| mail-11 | ok | 9% |
- Region
- eu-west
- Agents
- 3
- Updated
- 11 Oct 2026, 03:53
Agent fleet ─────────── 2 running, 1 waiting [WARN] 1 agent waiting for approval [######----] 55% Fleet load load ▁▃█▆▇ 0.21–0.62 Agent State Load build-07 [WARN] 62% index-02 [OK] 38% mail-11 [OK] 9% Region: eu-west Agents: 3 Updated: 11 Oct 2026, 03:53
Agent fleet
2 running, 0 waiting
| Agent | State ▾ | Load |
|---|---|---|
| build-07 | ok | 41% |
| index-02 | ok | 38% |
| mail-11 | ok | 9% |
- Region
- eu-west
- Agents
- 3
- Updated
- 11 Oct 2026, 03:53
03:53:11 build-07 waiting for approval: systemctl restart nginx
Agent fleet ─────────── 2 running, 0 waiting [OK] All agents running [######----] 55% Fleet load load ▁▃█▆▇ 0.21–0.62 Agent State Load build-07 [OK] 41% index-02 [OK] 38% mail-11 [OK] 9% Region: eu-west Agents: 3 Updated: 11 Oct 2026, 03:53 03:53:11 build-07 waiting for approval: systemctl restart nginx
Three kinds of program, one wire
Terminal programs run unchanged.
The server runs vim, htop or bash on a pseudo-terminal and sends the screen as cell runs on a grid, with styles, links, custom glyphs and the cursor.
$ vtx-status --fleet build-07 waiting see runbook
Agents ask. The client draws the question.
Approvals appear in the trusted zone, which no server content can draw into or imitate. A high-risk request can require a passkey.
systemctl restart nginx
An application is JSON lines.
No HTML and no build step. A program writes lines on stdout or a WebSocket, and the server turns them into frames. These lines produced the approval above.
{"kind":"claim","name":"Fleet agent","color":"#3BB58E"}
{"op":"open","id":"ops","type":"region","title":"Agent fleet"}
{"op":"open","id":"status","type":"status","parent":"ops","state":"pending","text":"Waiting for approval"}
{"kind":"approval","id":"apr-0001","title":"Restart nginx on web-03","command":"systemctl restart nginx","risk":"high","uv":true,"expires":300}
Status
Beta draft d03, revised 16 November 2026. The core has been feature-complete since d02. The wire format freezes once:
- independent implementations interoperate
- beta deployments have measured flow control and the transports
- an outside security review has been answered
- IANA has registered the port, ALPN IDs, WebSocket subprotocols and URI scheme
What exists today:
- The definitions bundle: CDDL, JSON Schemas and examples, checked by its validator (2564 checks)
- Conformance cases exported from the bundle: varints, frames, payloads and the text form
- Two independent wire codecs, in Rust and TypeScript, that pass every case
- A server for the core session layer over TLS and WebSocket, and a test probe whose recorded sessions pass the bundle's trace checker
- Applications on the application interface over stdio, with the scene checked and kept on the server
- Fallback rendering of the core catalog for clients without it, and
vtx, a terminal client that uses it