Conversations and workspaces

Give agents context, collaborate, and resume work.

Keep the task and its context together

The conversation is where you direct work and judge results. It holds your instructions, agent responses, and tool activity. Describe the desired behavior, the relevant files or constraints, and what should count as a successful check. Send corrections in the same conversation so the agent can use the existing context.

Available agents and models appear in Lobby’s selector. Availability depends on the deployment and your configured access; use the options shown there.

Understand what is shared

Members of the same Lobby account with repository access can open and continue shared conversations. Visibility and access rules still apply.

Conversations can share a live branch or use different Git worktrees. A conversation is not automatically an isolated copy of every file. Agents check the workspace and branch, coordinate file ownership, and isolate incompatible changes. They use projects and tasks to communicate progress and handoffs across conversations while you continue directing work in chat.

Continue later

Opening conversation history does not itself start a new cloud workspace. Sending another message resumes retained compute or restores the workspace when a suitable checkpoint is available.

If Lobby reports that a workspace cannot be recovered, preserve the error and resolve it before assuming your files are available. Have the agent commit and publish authorized work to GitHub; a live workspace should not be its only copy.

Ask for evidence

An agent finishing its response does not prove the task passed. Ask for the checks it ran, their results, and any remaining limitations. Use that evidence and demo videos to judge the result, then send corrections in conversation. You can ask for code or diff details when needed. The agent reports commit and publication status; required reviews and sensitive-operation approvals still apply.