GPU Experiment Workspace

Current Running

A compact MATLAB-style workspace: files on the left, code editor in the center, and live output plus the interactive shell in one terminal area.

Connecting to experiment server…
Editor

Python Script

Open .py or drop file
Missing packages are installed automatically into the selected environment.

Terminal

Shell connects automatically after unlock
Waiting for server output…
GPU Monitor

GPU & VRAM History

Loading GPU history…

No GPU history recorded yet.

The server checks GPU state periodically but stores a new history point only when GPU utilization or VRAM usage changes. Records older than 7 days are removed automatically.

Monitoring, code execution, history, files, and the shell use the same protected workspace. Submitted source code and authentication secrets are never returned by the public API.

Protected editing session

Unlock Editing

Control access requires two factors: your password and the current 6-digit code from your authenticator app. After both are verified, a secure HttpOnly session cookie is used until the session expires or you lock it.

Both factors are required. Failed login attempts are rate-limited by the server, and successful/failed access is written to the security audit log.

Protected security log

Security Activity

Review recent control logins and sensitive actions. IP address, browser user-agent, session ID, time, and result are recorded on the server. Passwords and authenticator codes are never written to this log.

Loading active sessions… —
No security activity has been recorded yet.

Image preview

Result Image

Selected result image

Protected action

Create Environment

Creates a new isolated Python environment, installs PyTorch CUDA 12.9, and validates a real CUDA tensor before the environment becomes ready.

Protected action

Delete Environment

Delete this environment and all packages installed inside it. Protected environments cannot be deleted.

Protected action

Stop Running

This sends a graceful stop request to the current process group. If it does not exit, the backend will force-stop it after a short timeout.