Agent lifecycle
An agent session moves through these backend states:
| State | Meaning |
|---|---|
PROVISIONING |
Kuberns is preparing the temporary agent infrastructure. |
RUNNING |
The agent is available and analyzing the workload. |
AGENT_COMPLETE |
The agent returned a completed configuration. |
FAILED |
The session recorded an error or failed phase. |
TERMINATED |
The temporary agent infrastructure has been terminated. |
What you see
During onboarding, the dashboard polls the session approximately every five seconds. When the session is running and its connection URL is available, the dashboard embeds the live agent view.
The session can record startup logs, internal logs, checkpoints, heartbeat timestamps, failure phase, completion state, and an error message.
Completion
After a successful agent result:
- Kuberns validates and stores the detected configuration.
- Generated Dockerfiles, environment-variable data, and detected resources are synchronized.
- The temporary agent host is terminated.
- Kuberns starts the normal application creation, build, and deployment process.
Agent completion does not mean the application build has succeeded. Follow the build in Build & Deployment and Build Logs.