Skip to main content

Module launch

Module launch 

Source
Expand description

firstpass launch <agent> [args…] — start a coding agent already pointed at this proxy.

The env-var swap is one line, so a subcommand that only exported it would be a convenience and nothing more. What it actually buys is the precondition: pointing an agent at a proxy that is not listening produces a connection error from inside the agent’s own error surface, which reads like the agent is broken rather than like the proxy is down. So this refuses to launch until /healthz answers, and says which of the two is wrong.

It also refuses when something answers that is not Firstpass. A 200 on /healthz only proves the port is held; whatever else is listening on 8080 during development will happily answer it. Handing an agent that address would route every request past the gate to a stranger that may well reply — a failure that looks like success, which is the worse one.

Uses exec on unix rather than spawning a child: the agent inherits this process’s PID and terminal directly, so job control, Ctrl-C, and raw-mode TUIs behave exactly as they do when the agent is run by hand. A wrapper process in between breaks all three.

Functions§

base_url
Resolve the proxy’s URL from the same variable the server binds on, so launch and up cannot disagree about where it is.
run
Run firstpass launch ….