Agent Sessions
Start, examine, and continue repository work with Lifecycle Agent in an isolated workspace.
Agent Sessions keep a conversation for repository work. A session can also open an isolated workspace. You can suspend, resume, or release the workspace.
Agent Sessions is a Labs feature. If New Chat, Sessions, or My agents is missing, ask an administrator if the feature is available.
Start a session
- Open New Chat.
- Select the built-in Agent or an available custom Agent.
- When more than one model is available, select a model.
- Examine optional tool and MCP selections.
- Give the task, repository, branch, and necessary outcome.
- Before work begins, examine the resolved repository or Environment context.
A session can start without a workspace. The Agent can start a workspace when the task needs repository files or commands.
Good first messages set a boundary:
Follow the run
The session shows messages, tool calls, workspace state, and pending approval. Tool information is evidence. Before you accept a result or change, examine the tool information.
When an action needs approval:
- Read the full command, file change, network request, or external operation.
- Make sure of the repository and workspace target.
- Approve only that action, or deny it with corrective feedback.
- When you understand its scope, use Always allow … in this chat only with administrator permission.
Lifecycle can send repository content and prompts to the configured model provider. When selected, external MCP or workspace providers also receive this data. Do not include credentials or data that those providers are not approved to process.
Use the workspace
Depending on the active workspace backend, a session can offer:
- Open editor
- authenticated preview ports
- suspend and resume
- Keep workspace
- Release workspace
For a suspended workspace, the session shows when Lifecycle can reclaim it automatically. Automatic reclamation can discard uncommitted files. Select Keep workspace to prevent automatic reclamation. A kept workspace can still suspend and resume.
When you select Release workspace, Lifecycle stops its processes and discards its files. The conversation stays, and a new task can start a new workspace. Before release, commit wanted changes or keep them in a different approved system.
Continue and examine sessions
Open Sessions to search recent or archived work and resume a conversation. Before continuing a previous session:
- reread its repository and branch context
- find whether its workspace continues to be the same one
- examine pending or failed actions
- state the changed goal
When prior context must not influence the next task, select Reset conversation.
Custom Agents and connections
My agents contains user-created Agent definitions when policy allows creation. An administrator can disable custom Agents, limit them to administrators, or use an allowlist.
Manage personal model or MCP connections in Settings → My connections. After a connection change, start a new run. Make sure that the expected tools are available.
Environment-scoped investigations
For a failure tied to one Lifecycle Environment, the Agent panel on that Environment’s details page selects the Build context. See Lifecycle Agent. Use Agent Sessions for broader repository work that benefits from a dedicated workspace.
Troubleshooting
- No model is available: an administrator must enable a provider and model.
- Workspace setup fails: Examine the displayed stage. An administrator must test the active backend.
- A tool is unavailable: Examine the selected Agent, personal connection, and combined repository policy.
- An action does not continue: Resolve its approval or deny it with feedback. Do not send duplicate write actions.