Gateway agent
Receives human requests, starts supported task cards and returns their results. Monitoring and scientific adjustment run as separate cards; the gateway is not itself the stationary lock or an optimizer.
Before starting
The selected provider CLI and authentication must be available to the service user. Select an execution profile or provider, model and supported effort. Starting or reconnecting this card does not restart a laser lock.
Connections and history
A card keeps a separate conversation per provider. Reconnecting resumes that conversation. The UI names the role Gateway agent. Stable routing IDs remain available in technical details and archived records. A session in history is not proof that its worker is currently running.
How to use it
Use the agent-request card or the shared native terminal/Web connection. OpenCode uses the same authenticated server and conversation; Claude and Codex request Remote Control where supported. The connection status, not the setting alone, confirms availability.
Measurements and authority
This card does not directly acquire a waveform or drive an output. Its scoped tools read the assigned laser, submit registered operations and inspect owner-confirmed results. Safety changes still require exact human approval. Agent replies and provider claims do not prove that hardware changed.
Failures and records
Failures use the gateway and configured Teams notification card. Questions and verified recovery are shown in Failure history and agent questions. Session history, request outcomes and PDF reports are kept in the laser data directory; shared code remains read-only.