Open a shell
- Open the intended Code workspace.
- Choose Add a panel → Terminal.
- Inspect the shell prompt and working directory before running a command. Use
pwdin a shell that supports it, or the shell’s equivalent location command. - Run the command and read its exit/output state before continuing.
- Add another Terminal panel when you need a separate shell, such as a long-running local preview alongside verification commands.
Terminal and Browser panels can have multiple instances. Moving or resizing the panel changes its workspace presentation; it does not make command effects temporary.
Separate shell and agent state
A running development server in a terminal is separate from a provider run in the transcript. Stopping the coding task does not imply that all terminal processes have stopped. Similarly, closing a visual tab should not be treated as evidence that every process it launched has ended.
Check the actual process or terminal state when a port remains busy. Avoid launching duplicate servers simply because the first terminal is no longer visible.
Recover a terminal problem
If a terminal cannot start, verify that the workspace exists and the configured OS shell is available. For an exited shell, open a new Terminal and confirm its directory again. A missing command can indicate that the app inherited a different PATH than your standalone terminal; fully reopening Rudr can help after an external installation.
Native shell, reconnect, and process-lifetime behavior can differ by OS and remains a walkthrough gap in this draft. Use workspace troubleshooting for recovery and Browser to inspect a running local site.