> ## Documentation Index > Fetch the complete documentation index at: https://synthlabs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Use a prepared workspace > Inspect setup and run commands in an environment your organization has already configured. A workspace is a place to work, not an evaluation score or training checkpoint. Use this surface when your organization has supplied a configured environment and you need to inspect its setup or execute a command there. ## Inspect setup Get the environment ID from the workspace's owner or Dashboard: ```bash theme={null} synth workspace setup get ``` The receipt identifies the setup run, when one exists. Use that run ID for: ```bash theme={null} synth workspace setup status synth workspace setup events ``` Do not confuse the environment ID, setup-run ID and managed task-run ID. They identify different resources and are not interchangeable. ## Execute a command Once the environment is ready and you have access: ```bash theme={null} synth workspace exec 'pwd' --timeout 60 ``` Read the command receipt for its state and any local state-file path. If it returns an attachable session, attach using that exact file: ```bash theme={null} synth workspace attach ``` For an uncertain request, keep its request ID and use the command's documented lookup behavior before submitting another command. Shell commands can change the remote workspace; inspect them with the same care as local commands. ## Rerunning setup is a mutation `synth workspace setup replay` reruns a configured setup recipe. It is not a general-purpose retry for a task or failed training run. Inspect the current environment and obtain the owner's approval before changing shared setup. Use [managed execution](/guides/managed-execution) for repeatable task trials, and [lifecycle and recovery](/operations/lifecycle-and-recovery) for run recovery. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.