HTTY's ecosystem is taking shape.

This site is a placeholder for the HTTY specifications, reference implementations, integration libraries, and developer tools that make terminal-native application sessions practical.

Today, the HTTY stack spans protocol framing, HTTP/2 adaptation layers, JavaScript and Ruby implementations, and a browser-like terminal client. This page is the initial map.

Core Specifications

protocol-htty defines the terminal-safe framing layer that carries an opaque session byte stream over DCS packets.

protocol-http2 provides the HTTP/2 wire semantics that HTTY transports when the session speaks plaintext h2.

Ruby Integration

async-htty adapts HTTY streams into Async-compatible HTTP/2 connections so Ruby applications can expose middleware over a terminal session.

This is the layer that connects transport framing to request and response handling.

JavaScript Runtime

@socketry/htty implements HTTY transport, client, and server primitives for Node.js and browser-adjacent tooling.

It currently powers the demo sessions and end-to-end flows used by Chimera.

Interactive Client

Chimera is the browser-like terminal environment that turns HTTY packets into attached surfaces and tabbed session views.

It demonstrates the user experience HTTY is designed to unlock.

Ecosystem Roadmap

Publish a compact overview of the HTTY transport model and packet types.
Document the layering between protocol-htty, protocol-http2, async-http, and async-htty.
Link reference implementations and runnable examples for Ruby and JavaScript.
Describe client behavior and attached-surface semantics as Chimera evolves.

Current Projects

protocol-htty Transport framing over terminal side channels. protocol-http2 HTTP/2 wire semantics reused by the HTTY stack. async-htty Async integration for serving and consuming HTTY sessions. htty-js JavaScript transport, session, and server implementation. chimera Desktop client for surfacing HTTY-backed application views.