Skip to content

Reference

gatOS has a friendly face, but its interfaces are proper contracts. This section is where paths, formats, units, gates, command timing, and sharp edges live.

NeedStart here
Read or write /simConventions, then Vessels and Controls
Query from another programHTTP or MQTT and serial
Automate a sequenceBatches and schedules
Compose a shot or play a clipCamera or Audio and display
Repaint a vehicle, part, or EVAVehicle and EVA paint
Change runtime behaviorConfiguration and mounts
Check what is ready for a flightStatus and limitations

These pages are the player-readable projection of the contract. The root SPEC_9P_FILESYSTEM.md is the exhaustive path-by-path source of truth; the MCP surface is separately documented in the MCP reference. MCP deliberately groups the model into logical resources and tools, so it is not a filesystem mirror.

Every /sim path is relative to the guest mount. Thus vessels/active/id below means /sim/vessels/active/id in a terminal and /v1/fs/vessels/active/id through the HTTP field mirror.