Skip to main content

Crate speccoder_web

Crate speccoder_web 

Source
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§

Shared
The host’s state.
Started
A started host.

Enums§

RecvError
Why reading Events failed: fell behind (Lagged) or the host ended. An error returned from the recv function on a Receiver.

Functions§

router
The routes.
serve
Serves the project at root on port (0: any free one) until the process ends; ready is told the address once it listens.

Type Aliases§

Events
The host’s events as a shell in the same process reads them.