Sessions
A session is a live sandbox with an AI agent attached to your codebase. You can run multiple sessions per project, each working on a different task.
Creating a session
Click the + button next to your project in the sidebar, or use the New Session button. The sandbox boots from your project's snapshot and starts the dev server automatically.
Session lifecycle
Sessions move through these states:
Starting
The sandbox is booting from the snapshot. This typically takes 5-15 seconds. During this time, Lot syncs the latest code from your repository, writes environment variables, and starts the dev server.
Running
The agent is actively working — reading files, writing code, running commands. You can watch its progress in real time.
Idle
The agent has finished its current task and is waiting for your next message. The sandbox is still running.
Waiting for user
The agent has a question and needs your input before continuing. Answer the question in the chat to resume.
Paused
The sandbox is hibernated. All memory state is preserved — processes, file system, and running services are frozen in place. Paused time is not billed. See Auto-pause and resume below for details.
Deleted
The session has been deleted by the user. The sandbox is terminated and all data (conversation history, diffs, and sandbox state) is permanently removed.
Switching between sessions
Click any session in the sidebar to switch to it. Each session maintains its own conversation, diff, and preview independently. Switching sessions doesn't affect running agents — they continue working in the background.
Parallel sessions
You can run multiple sessions on the same project simultaneously. Each gets its own sandbox with an independent copy of the code. This is useful for:
- Working on multiple features at once
- Testing different approaches to the same problem
- Having one session fix bugs while another adds features
Each session creates its own branch and PR, so there are no conflicts.
Auto-pause and resume
Lot automatically pauses and resumes sandboxes to save you money. You don't need to manage this — it happens in the background.
When the agent is active
While the agent is actively working, the sandbox stays running for up to 24 hours. This gives the agent plenty of time for long-running tasks without interruption.
When the agent is idle
Once the agent finishes its task (idle, waiting for your input, or errored), a 5-minute countdown starts. If you don't send another message within 5 minutes, the sandbox automatically pauses to stop the billing clock.
What happens when paused
Pausing hibernates the sandbox. All memory state is preserved — your running processes, file system, dev server, and everything in memory is frozen exactly as-is. When the sandbox resumes, everything picks up right where it left off.
How to resume
The sandbox resumes automatically when you interact with it:
- Send a message — the sandbox resumes, your message is delivered, and the agent starts working
- Click Resume — the right-side panels (preview, terminal, logs) show a Resume button when the sandbox is paused. Clicking it resumes the sandbox for 5 minutes so you can inspect the preview, run terminal commands, or check logs
Resume is near-instant — the sandbox comes back within a few seconds with all state intact.
Deleting a session
Click the icon on a session in the sidebar to delete it. This terminates the sandbox and permanently removes all session data including conversation history and diffs.
Model selection
You can switch Claude models between messages using the dropdown in the input panel. Available models include Opus and Sonnet. The model choice persists for the session.