Skip to main content
Expanse exposes two intelligence commands. Both reason over evidence from your own compute.

expanse analyse

Before submission. Recommends CPU, memory, GPU, and walltime.

expanse diagnose

After failure. Solution-oriented guidance with cited evidence.

Resource recommendation

expanse analyse recommends what a workload will need before you submit it. It accepts a SLURM batch script, a source file, a Kubernetes workload manifest, or a Nomad jobspec.
Recommendations are tied to your compute: when similar runs exist, the output cites the executions that anchored the numbers. For genuinely novel workloads there is no history to cite, so the recommendation is derived from your source alone, flagged with low confidence and explicit missing-evidence warnings rather than a fabricated history. Patches are review-first: analyse never touches your files on its own. Inspect the patch with expanse analyse diff, then apply it with expanse analyse apply (interactive confirmation, or --yes).

Failure diagnosis

expanse diagnose returns solution-oriented guidance for a failed execution. It cites the evidence it used: telemetry, logs, the captured source bundle, and similar executions of the same workload.
The interactive fix prompts appear only on a terminal, and only when the diagnosis produced a unified-diff artefact. Patch bytes are never embedded in the response; fetch and apply them explicitly from any shell:
Patches are review-first: the server never applies them. Application always happens on your machine, after you have seen the diff.