Expand description
speccoder’s web interface: a host on 127.0.0.1 that serves the interface — embedded in the binary — and an API over speccoder’s own payloads. The page, a browser tab or the desktop window, holds no logic of its own: what it shows and offers comes from the runtime, as for the CLI.
Modules§
- jobs
- What the host runs for the page: one job at a time — a planning skill, a run, a planning commit, a decision on a task. A job’s progress, and the calls and questions that need the person, go to the page as events; the page’s answers come back here and reach the waiting job. Nothing about a run changes: it is journaled, decided and committed as from the CLI.
- security
- Who may talk to the host. Loopback is not access control: any local process and any web page can reach 127.0.0.1. So:
Structs§
- Root
- The project a host serves: bound at most once (one host per project). A host started outside a project serves the welcome until the person creates, opens, clones or tries one.
- Shared
- The host’s state.
- Started
- A started host.
Enums§
- Recv
Error - Why reading
Eventsfailed: fell behind (Lagged) or the host ended. An error returned from therecvfunction on aReceiver.
Functions§
- router
- The routes.
- serve
- Serves the project at
rootonport(0: any free one) until the process ends;readyis told the address once it listens. Outside a project the host serves the welcome until it is bound to one.
Type Aliases§
- Events
- The host’s events as a shell in the same process reads them.