Sandbox and terminal
Investigate live behavior and coordinate terminal control with your team.
Before you begin
Open an accessible reproduction. Live sandbox access depends on your account, organization permissions, and available resources. Guests may be limited to captured evidence.
A sandbox is an isolated environment. Your local dependencies, private services, and credentials are not automatically available there. Never assume starting it proves the bug reproduces.
Open the terminal
Choose Terminal in the workspace to work with the live sandbox. Captured logs remain a record of the original failure; terminal commands produce new investigation output.
When the sandbox is suspended, use Resume terminal when offered. Wait for the connection to become ready before typing. If resuming fails, read the visible error and check access and resource availability before retrying.
Coordinate control
One participant is the driver and can send shell input. Other participants view the shared session without typing into it.
Use Take control when offered for an available session. If another participant is driving, use Request control and wait for transfer. The current driver can use Transfer control. Read the control status before running a command so you do not interrupt a teammate's investigation.
Run an investigation
Use the terminal's actual working directory and available project scripts. Check source and installed dependencies before running a build or test. A command may change files or start processes in the live sandbox.
Live investigation and clean verification serve different purposes. Terminal output can help explain a failure, but it does not replace a verification report against a fresh environment.
Recover a disconnected session
Read the terminal status, reconnect or resume when offered, and confirm driver ownership again. Avoid starting the same long running command twice while a connection is recovering. If your role cannot wake the sandbox, ask an authorized organization member to continue the investigation.
For setup and replay failures, see troubleshooting.