Documentation
¶
Overview ¶
Command harnessnode is the harness packaged to run INSIDE a compute sandbox (a substrate actor, or any runtime). It serves a selected harness over the harnesswire gRPC Harness.Connect stream on :80 — the port the atenet mesh routes to — so the external agentsessions controller drives it remotely, exactly as it drives the in-process runtime/local harness over a unix socket. A separate HTTP /readyz on :8081 lets ResumeActor block until the harness is live (ActorTemplate readyz probe).
This is the substrate realization of the harness half of the step-6 dial path: the transport moves from a unix socket to atenet-router, which forwards to this port; the harnesswire server is unchanged.
Click to show internal directories.
Click to hide internal directories.