AgentNexus added scoped runtime diagnostics to the workspace lifecycle panel so operators can see health proof, copy the full instance URL, and jump to the exact AgentC Runtime Control surface they need.
Status
Lifecycle proof added
Category
Runtime
Date
May 11, 2026
Read time
3 min read
Impact
Teams running managed AgentC Runtime or Hermes agents can diagnose health, gateway status, logs, and generated config faster without leaving the deployment lifecycle context.
What changed
The Runtime lifecycle card now keeps the high-level AgentNexus deployment status while adding a health proof block with health path, last check, config hash, image reference, and full instance URL copy.
For active AgentC Runtime deployments, the same card still links directly to AgentC Runtime Control chat, overview, logs, and config views. Hermes deployments show the runtime-aware health proof and API-style launch surface.
The AA plan rail now changes based on runtime state, and Command Center groups read-only, confirmation-required, and release-verification commands. It remains a read-only inspection surface rather than a live cloud shell.
Why it matters
Operators previously had to infer whether an active cloud badge meant health actually passed, which URL to copy, and where to look next. The workspace now exposes non-sensitive runtime proof and maps common deployment questions to the right inspection destination.
What to do
- Use Runtime chat for a quick smoke test after a deployment turns active.
- Use Runtime health proof to confirm the health path, last check, config hash, and image reference without exposing secrets.
- Use Runtime logs and Runtime config when a deployment is reachable but behavior does not match the saved agent configuration.
- Use the AgentNexus lifecycle controls for retry, refresh, and destroy actions; AgentC Runtime Control shortcuts and Command Center commands are inspection paths.