# Show HN: HPC-Hub, an app for working with HPC clusters > Source: > Published: 2026-11-12 22:09:02+00:00 An app for working on HPC clusters from Linux, Windows and macOS (Android is on the way). One click connects you (VPN, SSH, Duo or a code from your authenticator app), gets you a compute node, and opens VS Code, Claude or a terminal there. Files, jobs, Globus transfers and LaTeX are in the same window. It comes set up for NJIT Wulver, Yale Bouchet and SDSC Expanse. You can add other clusters in Settings. | Projects | Jobs | |---|---| - **Clusters** : connect with one button. VPN, SSH and Duo push are handled for you. Ask for a compute node with the cores, memory and time you saved for that cluster. - **Jobs and usage** : your jobs, your history or everyone's, with filters, details and cancel. Service units per person and storage quotas. - **Projects** : name a folder on a cluster and open it in VS Code, Claude, Files or LaTeX in one click. Copy or sync a project, with its Claude chats, to another cluster. - **Terminals** : tmux sessions on the cluster, so VS Code tunnels and agents keep running when you close the laptop. - **Agents** : run Claude, Codex, Antigravity or Cursor on a compute node, and choose which commands they may run. - **Files** : browse, preview PDFs and images, edit, zip, upload and download. Copy between clusters directly or with Globus, with live progress. - **Globus** : sign in once. The app finds each cluster's collection by itself and asks only for the permissions Globus needs. Experimental, off until you turn them on in Settings: - **LaTeX** : an Overleaf-like editor for projects on the cluster. Build with latexmk, jump between source and PDF, see git history, pull and push. - **Skills** : add skills to Claude and Codex on each cluster, from HPC Hub's set or any git repository. - **Scheduled agents** : an agent runs a task on its own, for example every night at 02:00. - Usernames and passwords are typed into the app and kept in your system's keyring (GNOME Keyring, macOS Keychain, Windows Credential Manager; on Android an encrypted file whose key stays in the phone's Keystore), never in plain text and never hardcoded. Settings in `~/.config/hpc-hub` hold no secrets. - Globus sign-in uses OAuth with PKCE in your own browser. Tokens are kept in the keyring. - Your saved VPN password is typed only into sign-in pages of your university's own site or a known sign-in provider, over https. - One exception, on the cluster: VS Code keeps its GitHub sign-in in your home folder there, unencrypted, so a tunnel on a new node does not ask you again. Sign out with `code tunnel user logout` if you don't want that. Download the file for your system from [Releases](https://github.com/bavanDA/hpc-hub/releases). The installers are not signed yet, so your system warns you the first time. 1. Run the `-setup.exe` (or the`.msi` ). If Windows says "Windows protected your PC", click**More info** , then**Run anyway** . 2. Open HPC Hub from the Start menu. 3. The first time you connect a cluster with a VPN (Wulver, Yale), HPC Hub asks to set up its VPN helper. Click **Set up** and approve the Windows prompt. This happens once. 1. Open the `.dmg` and drag HPC Hub to Applications. 2. Open it. macOS says it can't check the app: go to **System Settings, Privacy & Security** , scroll down and click**Open Anyway** . This happens once. 3. The first time you connect a cluster with a VPN, approve "Set up the VPN helper" and type your Mac password once. On Windows and macOS the VPN sends all your DNS through the university while it is up, and Disconnect on Windows doesn't sign you out on the VPN server (it ends by itself). - Ubuntu, Debian: `sudo apt install ./HPC-Hub_*_linux_amd64.deb` - Fedora, RHEL: `sudo dnf install ./HPC-Hub_*_linux_x86_64.rpm` - Any other: `chmod +x HPC-Hub_*.AppImage` and run it. The VPN needs `openconnect` from your distribution. A VPN that signs in on the university's web page (Yale's) also needs PyGObject with GTK 4 and WebKitGTK 6: `python3-gi gir1.2-webkit-6.0` on Ubuntu and Debian, `python3-gobject webkitgtk6.0` on Fedora. Not released yet. To try it, build it yourself (see [docs/design/android.md](https://github.com/bavanDA/hpc-hub/blob/main/docs/design/android.md)). It will come to Google Play and F-Droid. To log in, open HPC Hub's menu on your computer, then Set up the phone app, and scan the QR code with the phone. Globus copies need a free Globus app id. Make one at app.globus.org/settings/developers (choose a native app, name it HPC Hub, redirect URL `https://auth.globus.org/v2/web/auth-code`) and paste it on the Globus page. ``` app/ desktop app: Tauri (src-tauri, Rust) and React (src) mobile/ Android app; reuses app/src hpc_hub/ Python backend the apps talk to over JSON-RPC api/ the RPC server and one module per feature in methods/ core/ config, keyring, SSH: used by every feature connect/ VPN, sign-in, Duo compute/ Slurm, compute nodes, jobs, usage files/ browse, edit and copy files on the clusters globus/ Globus sign-in, collections and transfers agents/ Claude and other agents, chats, skills, permissions latex/ LaTeX editor, build, SyncTeX, git pdf/ PDF tools and read aloud projects/ named project folders and copying them across clusters terminals/ tmux sessions backup/ backups of cluster folders bin/ helpers ssh and openconnect call (askpass, SSO) packaging/ the frozen backend and release settings tests/ same folders as hpc_hub/ python3 -m venv .venv .venv/bin/pip install pytest ruff -r packaging/requirements-backend.txt .venv/bin/python -m pytest -q .venv/bin/ruff check hpc_hub tests packaging cd app && npm ci npm run tauri dev # the desktop app npx tsc -b && npm test # types and frontend tests ``` Guidelines: - Each feature has its own folder in `hpc_hub/` and in`app/src/components/` . Logic that parses output or builds shell commands has tests. Shared test fakes are in`tests/helpers.py` . - One job per file. A file over about 300 lines should be split. - Remote commands go through `SshMaster.run` . Quote paths with`shlex.quote` . - Never hardcode usernames, passwords or personal paths, including in tests. Use made-up names like `jdoe` . - Few comments, and only ones that say why. Lines up to 120 characters. - UI text: plain and short, no em or en dashes. - Commits: atomic, `type(scope): short msg` . MIT, see [LICENSE](https://github.com/bavanDA/hpc-hub/blob/main/LICENSE).