Module remote_runner

Structs§

RemoteWorkspace: Remote workspace handle carried on the tool execution context for runner-bound threads. Tools route file and shell operations through session with paths scoped under root (a path on the runner, not the local filesystem).
RunnerArtifactExportRequest
RunnerArtifactExportResult
RunnerCapabilities
RunnerCommandRequest
RunnerCommandResult
RunnerDestination
RunnerFileReadRequest
RunnerFileReadResult
RunnerFileWriteRequest
RunnerManifest
RunnerManifestEntry
RunnerMount
RunnerMountCapabilities
RunnerMountIntent
RunnerPortRequest
RunnerPortResult
RunnerSecretRef
RunnerSessionState
RunnerSnapshotRef
RunnerWorkspaceExecutionLeaseRequest: Bounds for an optional provider-owned lease that serializes one complete workspace tool execution. The runtime supplies a unique id and enforces the acquisition timeout locally; providers should also enforce both bounds at the remote execution boundary so a crashed runtime cannot orphan a lock.
ThreadRunnerBinding: Per-thread remote-runner binding chosen at thread creation. Native coding tools for a bound thread execute against this runner instead of the local filesystem; the destination config is persisted with the thread, so secrets must reach the provider through its environment, not this config.

RemoteRunnerProvider
RemoteRunnerSession
RemoteWorkspaceExecutionLease: Provider-owned serialization fence held around one complete workspace toolexecution. wait_lost must remain pending while the fence is authoritativeand is cancellation-safe: the runtime selects it against tool execution.release is called after every normal tool result or error, including afterwait_lost reports that the fence ended. Implementations must also failclosed when the guard or an in-progress release future is dropped (forexample, keep a remotely bounded lease alive until in-flight operations arequiescent or its server-side timeout expires).