Apps & launchers
When a workspace is running, its detail page shows an Apps section - one card per launcher. A launcher is a service that runs inside the workspace. Starting or stopping a launcher does not restart the workspace or affect other launchers.
The built-in launchers
Section titled “The built-in launchers”| Launcher | What it is |
|---|---|
| LabPod Terminal | Always available - opens immediately |
| JupyterLab | Jupyter notebook and file interface |
| Code | VS Code in the browser (Open VSX or the template’s configured Code app) |
| TensorBoard | Training visualization |
| MLflow | Experiment tracking UI |
Which launchers appear depends on the template. The CUDA Composite template includes all five; a plain PyTorch JupyterLab template shows JupyterLab and the terminal.
If a launcher shows not installed, it isn’t part of the template you chose. Expand the “Show install command” detail for a pip/conda command you can run in the terminal to add it, or ask your admin to register a template that has it pre-installed.
Starting a launcher
Section titled “Starting a launcher”Click Start on the launcher card. LabPod starts the service inside the running container and waits until it responds before showing the Open button (up to 2 minutes). Once open, the app loads in a new tab.
Some launchers - for example TensorBoard - prompt for options before starting (such as the log directory). Fill in the fields and click Start.
You can Restart a running launcher without stopping the workspace.
Opening apps
Section titled “Opening apps”Click Open on a running launcher card to open it in a new tab. The URL uses the workspace
gateway, for example http://<host>:24681/ws/<workspace-id>/jupyter/, rather than the LabPod UI
and API origin. LabPod redirects the link there automatically.
These URLs are protected by your LabPod session cookie. They only work while the workspace is running and you are logged in. If you share a URL with a colleague, they’ll be redirected to the login page.
In LabPod Connect, workspace app navigation stays in the workstation pane for direct and SSH connections.
LabPod Terminal
Section titled “LabPod Terminal”The LabPod Terminal is always available when the workspace is running - no Start required. Click Open to get a full browser-based terminal session inside your workspace.
The terminal runs tmux inside the container, so:
- Closing the browser tab does not end the session. Reconnect with Open and your terminal history and running processes are still there.
- If the server restarts, the terminal reconnects automatically. Its tmux session and scrollback, including blank lines, remain intact.
- You can have multiple terminal windows open at the same time; they all connect to the same session.
- Works in any template that has
/bin/sh- no special image requirements.
Only the workspace owner can open its terminal. If the workspace is stopped, LabPod explains that you must start it first instead of leaving an unusable terminal screen open.
Install project environments that should be shared by your workspaces under /work, for example
/work/venvs/my-project. Do not use ~/work: workspace home is private to one workspace and the
shared work directory is mounted at /work.
Refreshing availability
Section titled “Refreshing availability”If a launcher shows an unexpected status after you’ve installed something, click the Refresh button in the Apps header. This re-probes the container to pick up changes.
If Start reports that the application never answered its readiness check, open Show technical details. The address and HTTP status identify a wrong readiness path or proxy-prefix setting; retrying does not fix a configuration error. Follow the template guidance or ask an administrator to correct the launcher.
Container logs
Section titled “Container logs”The workspace detail page has a Container logs section. Click Load logs to fetch the last N lines (default 200) of the container’s stdout/stderr. Useful for diagnosing startup failures. Choose a higher tail value and click Refresh logs for more history.
For tools not in the launcher list
Section titled “For tools not in the launcher list”Use Extra apps & ports to expose services you start yourself - Gradio, Streamlit, FastAPI, a second TensorBoard instance, etc.