Workspaces
Your research, ready to pick up
Keep a named project, its saved files and compute configuration together. Workspaces is a preview. The console checks the environments, configuration and connections currently available to your account before starting compute.
Create and find your project
Create a saved project with an environment, GPU requirements, project capacity and maximum session duration. Optionally connect a permitted public or private GitHub repository. Review the current configuration quote before starting. Where account-funded sessions are enabled, sessions use account funding without requiring a separate session spending cap. Account spending controls still apply.
Workspace cards show compute state, GPU configuration, repository and saved-file size, with running sessions first. Search or filter by name, GPU or repository. Open a project for compute controls, connection readiness, files and usage.
Connect and develop
Use the available browser editor, desktop VS Code over SSH or SSH command for the same running project. Existing notebook configurations retain JupyterLab access. Add your own public SSH key in Settings, or use Set up SSH for this computer, then connect when the tool is ready. Teammates use their own keys.
A command started in the workspace terminal runs on its session. Finishing that command, closing the editor or disconnecting SSH does not stop compute. Submit a separate workload when you want a managed job with its own lifecycle.
Schedule, save and control costs
Schedule a session for a requested ready time, optionally set its stop time, or cancel its schedule. Preparation begins ahead of the requested time, but availability is checked at launch and a schedule does not reserve capacity.
Stop compute explicitly and observe file-save and release progress. Saved files remain with the project between sessions. When compute and transfers are stopped, export or explicitly delete saved project files, and edit supported settings for the next session. Inspect session history, usage and receipts, with storage accounted for separately from compute.
Supported shapes and connection flags determine what can start and connect. A saved project is not a running process, and restoring its files does not restore arbitrary application memory.