Local Mission Control

Open the console

Start KSP and wait until Telemachus reports ready. On the same computer, open the loopback URL below. The page should go offline when the game or local data link stops.

http://127.0.0.1:8085/telemachus/

Public site vs local console

ksp.kodydennon.com hosts documentation, access control, releases, and downloads. 127.0.0.1:8085 hosts live mission data. They intentionally use different origins, trust boundaries, storage, and availability states.

Connection state

Health reports whether the game data source is available. Snapshot data includes current vessel state plus available integration capabilities. A disconnected RemoteTech route is not the same as the local HTTP server being unavailable; Mission Control displays both states separately.

Command safety

Commands use versioned /api/v2 endpoints, explicit identifiers, validation, and no-store responses. High-impact operations should require an in-game confirmation or an elevated local operator session. The beta console does not accept arbitrary legacy Telemachus query expressions.

Console workspace

The command center groups vessel identity, flight state, route health, constellation service, science readiness, alerts, and operator actions. Panels share one bounded snapshot so values describe the same simulation instant.

A panel that cannot source a value displays unavailable with a reason. It never substitutes zero, stale history, or a fabricated local value without marking it.

Refresh and offline behavior

Fast-changing flight values update more often than topology, science inventory, or catalog metadata. The adapter coalesces requests and stops polling when the page is hidden.

When KSP exits, the heartbeat expires and the page enters Offline. Last-known values may remain visible for context but are timestamped and visually separated from live data.

Second-device use