SLURM Cluster Manager
Manage, monitor, and submit SLURM jobs directly from VS Code.
SLURM Cluster Manager brings your HPC workflow into your editor: monitor jobs in real time, inspect logs instantly, and take common actions (cancel/hold/pin) without context-switching to a terminal.
✨ Highlights
- Live job monitoring in a dedicated sidebar (Running / Pending / Held)
- Visual progress bars for time usage (
Elapsed / Time Limit)
- Resource overview (CPUs, memory, nodes)
- GPU stats via
nvidia-smi (when available)
- One-click actions: cancel, hold, pin
- Job history for recent completed/failed/cancelled jobs
- Instant log access for
stdout / stderr
🚀 Features
Active Job Management
- Real-time Monitoring: View all active jobs at a glance (Running, Pending, Held).
- Time Awareness: Smart progress bars show elapsed vs. requested wall time.
- Resource Stats: Display allocated CPUs, memory, and node count for each job.
- GPU Visibility: Uses
nvidia-smi to surface GPU utilization and memory usage where supported.
- One-Click Actions: Cancel, hold, or pin jobs directly from the UI.
- Batch Cancel: Select multiple jobs via checkboxes, then cancel them all at once. The "Cancel All" button becomes "Cancel Selected" when jobs are checked. Selections persist across refreshes.
- Smart Pending Display: Pending jobs hide irrelevant info (Nodes, Elapsed, logs) and instead show estimated start time and dependency indicators (🔗).
- Job Dependencies: View dependency info (e.g.,
afterok:12345) in the expanded job details.
Job Array Management
Smart handling of SLURM job arrays with flexible cancellation options:
- Cancel entire array: Remove all jobs in the array at once
- Cancel pending jobs: Cancel only pending jobs, keep running ones
- Cancel specific job(s): Flexible input supporting:
- Single index:
3
- Range:
0-10 (indices 0 through 10 inclusive)
- Step:
0-20:2 (every 2nd job: 0, 2, 4, ..., 20)
- List:
1,3,5,7 (non-contiguous jobs)
- Bounds validation: Automatically validates against actual array range
- Safety warnings: Extra confirmation when cancelling >100 jobs
Note: Array-level cancel options only appear for pending jobs. Running array tasks are cancelled directly like any individual job.
Job History & Logs
- Integrated History: Browse recent completed, failed, and cancelled jobs (default: last 7 days).
- Instant Log Access: Right-click any job (active or historical) to open its
stdout / stderr.
- Smart Path Resolution: Automatically resolves log locations from
sbatch directives and scontrol metadata.
Workflow Integrations
- Pinning: Keep critical long-running jobs visible even while filtering or sorting.
- Search & Filter: Quickly find jobs by name.
- Cluster Hog Indicators: Two fun indicators at the top of your job list:
- Job Hog: The user with the most running jobs (🐷 Job Hog, 🔥 Cluster Dominator, 🤗 CUDA Cuddler, 😋 Node Nom-Nom)
- GPU Hog: The user hoarding the most GPUs (🧛 VRAMpire, 🎮 GPU Gobbler, ⚡ Watt Wizard, 🏋️ Tensor Titan)
Hall of Shame
- Cluster Leaderboard: A dedicated sidebar view ranking all users by GPU allocation and running job count.
- Manual refresh only — no background polling, so it won't add load to your cluster.
- Top 3 hogs get shame emojis: 💀 🔥 👹
Script Intelligence
- Quick Submit: A ▶ button appears in the editor title bar when viewing any file containing
#SBATCH directives. One click to submit — no dialogs.
- Partition Hover Stats: Hover over a partition name in
#SBATCH --partition= to see real-time GPU usage, running/pending jobs, and node availability with a visual usage bar.
- Visual Hints: Partition names get a dotted underline to show they're hoverable.
⚙️ Configuration
Configure the extension via VS Code Settings (Cmd+, on macOS / Ctrl+, on Windows/Linux):
| Setting |
Default |
Description |
autoRefreshInterval |
30 |
Refresh frequency (in seconds). Range: 5s → 1h |
autoRefreshEnabled |
false |
Auto-start refreshing on window load |
confirmCancelJob |
true |
Ask for confirmation before cancelling a job |
Tip: If you monitor many jobs, increasing autoRefreshInterval reduces SLURM command load.
✅ Requirements
This extension must run on a machine with direct access to SLURM commands.
In practice, that means you should install it only on the cluster side (e.g., a login node / head node / SLURM-accessible node — whichever your site provides), not on your local computer.
Required commands:
squeuescontrolsacctsbatchscancel
Important: No Remote Connection (Yet)
At the moment, the extension cannot connect to a remote cluster by itself.
It does not SSH into a server, tunnel commands, or forward SLURM calls.
✅ Supported setup: Run VS Code on the SLURM-accessible node (or use VS Code Remote - SSH to open a remote VS Code session on that node) and install the extension on the Remote target.
🚧 Remote connection support is work-in-progress (WIP) and will be added in a future release.
🤝 Contributing
Contributions are welcome — bug fixes, documentation improvements, and feature requests.
If you’re opening a PR, please include:
- A short description of the change and why it helps
- Screenshots/GIFs for UI updates (when applicable)
📄 License
MIT — see LICENSE.
If this extension helps you, consider giving it a ⭐ on GitHub!
Made with ❤️ by Dhimitrios Duka with Google Antigravity
