herdrdev /

Herdr

Live map
View repository
Snapshotmaster · 51b7064e

From host input through private sockets, persistent workspace state, pane-owned PTYs, agent detection, and per-client rendering.

Click a building or route
Choose a path

Cross the binary socket, focused PTY, terminal parser, server renderer, and host display.

System map14 components · 30 connections
130%
Herdr terminal workspace runtime architectureStart with the interactive loop, then compare the JSON automation path with remote attach and session restoration.RawInputEvent + termin…Hello | Input | Resize…ClientConnected | Clie…input event | app even…bytes + resize, spawn,…user input bytes + win…stdout/stderr bytes + …cells, modes, title, C…AppState + terminal sn…FrameData | TerminalFr…Welcome | Frame | Term…[u32 length][bincode S…ANSI bytes or locally …herdr.devFeedsSSH StdioBridgeVirtualRendererLauncher& host TTYThin TUIClientBinary GatewayHeadlessServerAppState& EventHubTerminalRuntime & PTYsCLI & AgentClientsJSON APIGatewayGhostty VT& DetectorShell &Agent ProcessSessionStorage
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

PTYA pseudo-terminal that lets Herdr host an interactive shell or coding agent as a child process.

How to study this repo

  1. 1
    Trace one keystroke

    Follow host input through ClientMessage, AppState, the pane PTY, Ghostty, and the per-client render stream.

  2. 2
    Compare both sockets

    Contrast the framed binary TUI protocol with the newline-delimited JSON automation API.

  3. 3
    Separate model from process

    Read snapshot and restore together to see why layouts persist while shells and PTYs restart fresh.