Troubleshooting

Diagnosis paths for common dependency, workspace lifecycle, process, and window-routing failures.

Quick Triage

1. Check that Chrome is installed.
2. Confirm the workspace is still listed in the sidebar and not hidden.
3. If launch complains about existing runtime, run spaces workspace restart from the workspace directory.

• “Workspace is already running” — use spaces workspace restart from the workspace directory to reset state.
• No terminal windows appear — confirm your processes are running.
• Focusing a browser session opens nothing — confirm Chrome is installed and the session has a valid URL. Browser sessions open only when you focus them, not at launch.
• Browser sessions never open or focus Chrome — Spaces needs permission to control Google Chrome. Enable Spaces for Google Chrome under System Settings ▸ Privacy & Security ▸ Automation.
• Something is left running after stop — add the teardown command to the project or workspace stop script to clean up state not managed by Spaces.

cd <workspace-directory>
spaces workspace start
spaces workspace restart

• Global toggle (cmd+alt+=) or another global shortcut does nothing — another app may own the combo. Rebind it in Settings.