Slurm workflows

Connect Clio to supported Slurm tools for cluster work.

Work with a scheduler

Clio connects to Slurm through the stdio MCP server shipped by clio-kit. The server provides job submission, listing, description, cancellation, and cluster information. A working scheduler connection is required; client binaries alone are not enough.

Use the full guide's setup commands to declare the server, then run clio-coder doctor to check the Slurm clients and configuration.

Use a job workflow

Install the project-scoped Slurm skill:

clio-coder library install skill:slurm-jobs --project

Then ask it to run a specific script and report the evidence:

/skill slurm-jobs Submit this script, wait for its terminal state, and report the job ID, exit code, stdout, and stderr paths.

The skill submits once, polls through the MCP server, and reports the outcome. It does not fall back to shell sbatch when the server is unavailable.

Choose approvals deliberately

An undeclared action class defaults to unknown. In default autonomy, both submission and read-only polling ask for approval; headless default runs deny those asks.

MCP trust classification applies to the whole server, including submission and cancellation. Review the full guide before changing that classification or enabling unattended execution. For small local changes, begin with ordinary project checks.