Hello everyone,

I would like to introduce HPC Client GUI, a desktop application I have been developing to make everyday work with SSH-accessible Slurm clusters easier.

The project grew out of my own research and CFD workflows on Türkiye’s TRUBA infrastructure. I wanted to reduce the need to switch between a terminal, an SFTP client, scheduler commands, and job-output files.

HPC Client GUI brings these tasks together:

• SSH connections and reusable connection profiles
• Remote file browsing, SFTP uploads/downloads, and transfer management
• Slurm job submission, queue monitoring, accounting information, and cancellation
• Job output and error-file inspection
• Integrated terminal and CLI workflows
• Optional X11 forwarding
• Downloadable cluster profiles, job templates, and lint rule packs, including ANSYS Fluent journal checks

The application runs locally on Windows, macOS, and Linux. It uses SSH, SFTP, and standard Slurm commands such as sbatch, squeue, sacct, and scancel; it does not require a server-side agent, web portal, or slurmrestd deployment.

Repository, screenshots, documentation, and downloads:
https://github.com/mskomek/hpc-client-gui

Although TRUBA was the original use case, the project is intended for other SSH + Slurm environments. Compatibility with individual clusters depends on their authentication methods, scheduler configuration, and site policies. This is an independent project, not an official TRUBA or SchedMD tool.

I would appreciate feedback from both researchers and cluster administrators, especially on:

• Compatibility with different Slurm configurations and output formats
• SSH authentication, MFA, and jump-host requirements
• Appropriate polling frequency and login-node load
• Site policies or safeguards a desktop client should respect
• Missing features or documentation that would prevent adoption

If anyone is willing to try it on another cluster, the repository includes a read-only compatibility validation guide. Please do not share credentials, confidential hostnames, or private configuration in public reports.

For transparency, the project is source-available under the PolyForm Noncommercial License 1.0.0; commercial use requires a separate license. The current macOS packages are unsigned and not notarized, as disclosed in the release notes.

Thank you for your time. Suggestions, compatibility reports, and critical feedback are all welcome.

Best regards,
Mehmed Sinan Kömek