Skip to content
lobby

Can your teammate pick up where you left off?

Compare Lobby and your existing Codex workflow on one real handoff. Keep the issue, starting commit and acceptance checks the same. Judge the reviewed result and the context your teammate can recover.

Try the handoff pilot

Choose around how your team works

Keep your current workflow

If independent tasks, Git worktrees and pull-request review already give your team enough context, start there. Codex supports worktrees for parallel work; do not assume that parallel agents require Lobby.

Read OpenAI’s worktree documentation

Evaluate a shared Lobby workspace

Consider Lobby when people need to continue the same conversation and coordinate work on a shared project. Members with the required access can recover conversation history, task decisions and source context.

Read what Lobby shares

Lobby can run Codex. This evaluates the surrounding workflow, not a claim that one model writes better code. Model access, repository permissions and environment setup still need to be configured.

Run the teammate handoff

Use a disposable repository or a bounded issue approved by your team. This is a pilot recipe, not a recorded customer result. No production changes are needed.

  1. A starts a small change

    Pin the starting commit and a failing acceptance check. Ask an implementation agent to make the change, and a separate review agent to check it. Save the task link, current commit, exact test results and unresolved decisions.

  2. B continues from the shared context

    A stops directing the work. B opens the same Lobby conversation with their own authorized account, reads the linked task, inspects the current source and reruns the check. Record any context B has to ask A to repeat.

  3. B finishes the review

    Publish an authorized feature PR. A human reviews the exact head commit against the acceptance check. Keep missing evidence and failing checks visible; an agent finishing its turn is not acceptance.

Open the starting prompt

Replace the bracketed fields before use. Do not paste credentials.

Work on [issue] from [starting SHA]. Success means [observable acceptance check]. Link the existing task and preserve unrelated work. Implement the smallest change, run the check, and ask a separate reviewer to inspect the exact revision. Before the teammate handoff, record the conversation and task links, current source SHA, commands and observed results, unresolved decisions, and environment recovery steps. Publish only an authorized feature PR. Do not merge or deploy.
Open the teammate’s verification checklist
  • Can B read the original request and subsequent corrections?
  • Do the branch, files and commit match the handoff record?
  • Can B run the same check with the documented setup?
  • Are unresolved decisions and ownership visible?
  • Does human review accept the exact published commit?

Start a Lobby pilot

Compare evidence, not agent counts

Repeat the same issue in your Codex workflow using the same model and settings where available. Record unavailable settings as unknown. Use fresh workspaces, alternate run order, and keep the reviewer’s acceptance criteria fixed.

Accepted result
Passing behavioral checks and a human review tied to the published commit.
Handoff effort
Time B spends recovering context, repeated explanations, and missing environment steps.
Failures and cost
Stale edits, failed checks, manual recovery, elapsed time and reported usage. Missing usage stays unknown.

No controlled head-to-head result is published here yet. A successful page visit, signup or agent launch is not a reviewed-result activation.

Shared files require coordination. Isolate incompatible changes in worktrees; publish important work because a live VM is not its only durable record. Access removal and workspace recovery have their own boundaries.

Read more about projects and task history, source control and access boundaries.