Skip to main content

Documentation Index

Fetch the complete documentation index at: https://solo-09d10f60.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Wake gate

The wake gate is the worker-side reliability check for long-running agent jobs. It exists because an agent session ending is not the same as the machine being idle.

​
What it observes

The code models process snapshots, process info, telemetry samples, run records, and gate callbacks. Configuration supports sample_interval_sec, idle_sustain_sec, CPU and GPU idle thresholds, VRAM delta thresholds, workload profiles, and stale-project process reaper settings. Supported workload classes in the config model are inference_eval, training, control_plane, and agent_harness.

​
Gate idea

A run should only advance when relevant processes are gone or stale-safe, and telemetry has remained under configured thresholds for the sustain window. This avoids advancing the queue while a detached worker process still consumes resources.

​
Callback behavior

When the gate is satisfied, the app can send a completion callback to completion_callback_url using completion_callback_token. Deprecated n8n_* config aliases exist for older private prototypes, but new docs and configs should use completion_callback_*.

​
Stale process reaper

The reaper can identify stale project processes by command markers such as llama-cli, llama-server, vllm, and sglang. Keep the marker list conservative. Do not add broad substrings that could terminate unrelated user processes.

​
Operator guidance

Tune thresholds per workload, use dry-run dispatch and preflight endpoints first, keep worker tokens distinct where practical, and treat wake-gate evidence as operational evidence rather than scientific validation of generated results.