Project hosts
Project host software and daemon lifecycle
Understand runtime software, managed daemons, reconcile, upgrades, drift, and rollbacks.
What the Runtime tab is for
The host Runtime tab explains what software the host wants to run, what is actually installed, and what managed daemons are currently doing. It combines cluster defaults, host-specific overrides, host telemetry, reconcile state, and daemon rollout state.
There are two related surfaces:
- Runtime software: versions for project-host, project bundle, and tools.
- Managed daemon components: local daemons such as project-host services that can be restarted, reconciled, rolled forward, or rolled back.
Bootstrap and software lifecycle
Bootstrap prepares the host. Software lifecycle then keeps the host aligned with desired state. The lifecycle reports summary status, drift count, last reconcile result, active reconcile work, and errors.
Drift means the host's observed state does not match desired state. It may be normal during an upgrade or after changing versions, but persistent drift means the host needs reconcile or investigation.
Reconcile and upgrade
Reconcile asks the host to repair or align installed software and daemon state with the desired configuration. It is the first action to try when the host reports drift but the desired versions are already correct.
Upgrade changes desired versions and then queues lifecycle work. Newly started projects use the upgraded project bundle and tools. Project-host daemon upgrades may briefly reconnect browser and proxy traffic, so they should be scheduled with care.
Daemon lifecycle
Managed daemons have desired versions, installed versions, running versions, health, rollout phase, and sometimes rollback hints. A daemon can be pinned by a host-specific override or inherit the cluster default.
If a daemon is disruptive, prefer maintenance windows. If a desired version is not installed yet, setting it queues reconcile work. Refresh the Runtime tab to watch rollout, health, rollback, and repair state.
Agent notes
For deep inspection, use host runtime and deployment commands in addition to the browser tab. Look for version drift, failed reconcile, daemon health, rollout phase, and host-specific overrides. Do not treat project bundle, project-host daemon, and tools as the same artifact; they affect different parts of the runtime stack.