GitHub recently added a check_run_id claim to OIDC tokens issued during workflow execution. Atmos Pro now uses this native identifier to link CLI requests directly to workflow run records on the server side — automatically and without any changes to your workflows.

When Atmos Pro dispatches a workflow, GitHub fires a workflow_run webhook containing the run's numeric ID. Atmos Pro stores that ID on the workflow run record. Later, when the CLI authenticates via GitHub's OIDC provider, the signed token includes a check_run_id claim — the same numeric ID. The server decodes it from the JWT and matches it to the stored record. The entire linkage happens through GitHub-native identifiers with zero configuration on your part.

This also means your workflow run-name is entirely yours. Name your runs however you want — the Atmos Pro integration no longer depends on it.

This works automatically with your existing workflows. If your workflows still pass atmos_pro_run_id, that continues to work as before. The new OIDC-based linkage activates when it's absent, so there's nothing to update and no CLI upgrade needed.