server

What it is

@moku-labs/editor/server is the editor-server core. It runs on Bun: it uses Bun.serve and HTML imports. It has no opt-in plugins; all five are defaults.

A custom composition keeps the order: connectPlugin between hubPlugin and collectorPlugin, and collectorPlugin before pagesPlugin. Options are on Configuration.

files

The project-root sandbox: list, read, an atomic write with a version check, image captures, the project index and the computer's engine fingerprint. A file must match the allow globs and none of the deny globs.

API: list, read, write, writeBinary, readBinary, resolve, root, find, project, engine, refreshEngine.

hub

The websocket switchboard. It guards each upgrade with Host, Origin and the token, opens sessions, routes requests, fans out values, applies backpressure, and sends the hotReload and engine notifications. It keeps the tools page's selection and relays editor.select to it. In device mode it runs the device listeners (adb and LAN), the pairing and a ping for each phone's latency.

API: serve, token, sessions, fetch, websocket, addRoutes, guard, publish, closeAll, path, listenDevices, stopDevices, devices, listenLan, stopLan, addEditorMethods.

serve(options) wraps the game's Bun.serve options: it forces 127.0.0.1, merges the game's routes, the routes from addRoutes and {path}/ws, and adds the websocket handler. Call it once, after start(). addEditorMethods registers another plugin's editor methods, such as connect.*, for tools sockets only.

connect

Connect a phone from the tools page. It turns device mode on and off on request, keeps the device directory (editor.devices: phones adb lists, pairings asking, linked devices), confirms a pairing in the page, and for a phone by wire reads CDP over adb forward and the wired telemetry (editor.deviceTelemetry, once a second).

The editor methods answer only tools sockets. Errors: port_in_use when another process holds the device port, no_lan, not_owner when device mode belongs to moku-editor perf, no_ticket.

collector

Device logs on the computer: one JSONL file per phone log, adb reverse, heat and system frames while device mode is on, a wired phone's telemetry lines while it records, and the route of perf mark. On a dev server it is idle. It houses the summary and compare of moku-editor perf.

API: sessions, mark, adb, settled.

pages

Serves the prebuilt tools page with its boot JSON, its assets, and the hello and hmr routes. It is the home of the moku-editor bin, of moku-editor mcp and of moku-editor perf.

API: routes, attachServer, hotReload, setHotReload, attachPerf.

moku-editor e2e gives each spec file a fresh bin, because Bun's dev server degrades after many hot reloads in one process. A run holds .moku/e2e.lock, so two runs never overlap.

Events

Payloads are on Events.