Lifecycle Agent
Investigate a Lifecycle Environment, examine evidence, and do approved recovery tasks from the Environment details page.
Lifecycle Agent helps you investigate and recover an Environment without leaving its details page. It starts with the build and namespace in context, then uses the tools your administrator has allowed.
Lifecycle Agent is an administrator-controlled feature. The Agent panel and available models or actions can be different for each deployment and repository.
Investigate an Environment
- Open Environments.
- Select the Environment that you want to investigate.
- Open Lifecycle Agent from the Environment details page.
- Select Diagnose failure, Repair, or enter a focused question.
- Examine the agent’s explanation and the evidence from its tool calls.
- After you check its target and effect, approve a proposed write action.
Good prompts name the observed symptom and the outcome you want:
- “Why did the latest deploy fail?”
- “Which Service cannot become ready, and what evidence supports that?”
- “Propose the smallest repair. Do not make changes.”
The agent can offer follow-up actions such as Investigate more, Open editor, Continue with workspace, or Start workspace when those capabilities are available.
Tools and approvals
The agent can use these evidence types together:
| Area | Typical use |
|---|---|
| Lifecycle | Examine Environment, Build, Service, and job state |
| Kubernetes | Read resources, events, and logs in the Environment namespace |
| Repository | Read related source and configuration |
| Workspace | Examine or edit files and run commands in an isolated workspace |
| External MCP | Use administrator-approved tools from connected MCP servers |
Administrator and repository policies control tool availability. Some reads can run without approval. Policies can require approval for or deny writes, shell commands, network access, and deployment changes.
An approval immediately authorizes the proposed action. The action can change a running Environment or an external system. Before you approve it, make sure of the repository, namespace, command, and affected files.
Select a model
If your deployment offers more than one model, use the model selector in the Agent panel. The configured provider, allowed models, and default model are controlled by an administrator.
Do not paste provider credentials into a chat or repository.
Start over
When prior messages do not apply, select Reset conversation. The new conversation does not include the previous investigation messages.
Lifecycle Agent and Agent Sessions
The Environment details panel covers one Lifecycle Environment. Agent Sessions support broader repository work when the Labs feature is available. See Agent Sessions for the distinction.
Troubleshooting
- The Agent panel is missing: an administrator can tell you if your deployment and repository enable Lifecycle Agent.
- No models are available: an administrator must configure a provider and at least one allowed model.
- A tool is missing or denied: tool and approval policies can be global or for one repository. Tell an administrator to examine the combined policy.
- An action is waiting: open its approval request and examine the full operation. Only an authorized user can approve it.
Administrators can continue with Lifecycle Agent configuration, MCP integration, and Agent administration.