docs(runner-setup): rewrite for the 5.2.x standalone runner - #2
Draft
paulsbrookes wants to merge 1 commit into
Draft
docs(runner-setup): rewrite for the 5.2.x standalone runner#2paulsbrookes wants to merge 1 commit into
paulsbrookes wants to merge 1 commit into
Conversation
The runner-setup skill was entirely on the Python 3.11 venv + tools-bundle installer path with download credentials. Rewrite it around the shipped 5.2.x runner (verified against 5.2.0, 2026-07-14): - Download the self-contained standalone binary from the public, no-auth path files.artemis.turintech.ai/public/artemis-runner/ (`-latest` tracks newest). - Register via `configure --url --token` using the single-use registration token shown in the Web UI (Runners -> Add runner), then `start`. An API key works headlessly as an alternative. - Add the self-update `artemis-runner upgrade` command and advanced-option flags; keep the pip/venv path only as a fallback for when the binary won't run.
paulsbrookes
marked this pull request as draft
July 14, 2026 15:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
runner-setupskill walks users through the Python 3.11 venv + tools-bundle installer path with download credentials. That path is now legacy: the runner ships as a self-contained standalone binary on a public download path, and the CLI surface changed in 5.x (thestart interactive/start non-interactivesubcommands were removed; aconfigure+ registration-token flow and a self-updateupgradecommand were added).Change
Rewrite the skill around the shipped 5.2.x runner (verified against
5.2.0, 2026-07-14), keeping the step-by-step, one-question-at-a-time guidance style:https://files.artemis.turintech.ai/public/artemis-runner/artemis-runner-latest-linux(Windows.exetoo).-latestthere tracks the newest release; no credentials needed.configure --url <deployment> --token <turin_reg_…> --runner-name <name>using the single-use token from the Web UI (Runners → Add new Artemis runner), thenstart. An API key remains a headless alternative (start --api-key).artemis-runner upgrade(per-deployment pre-release policy).--no-delete-task-output,--worker-output-dir,--ram-limit-mb) documented.Verification
All commands were checked against the actual
5.2.0binary:--version,configure --help,start --help,upgrade --help, and confirmation thatstart non-interactivenow errors (unexpected extra argument(s)). The public-latest-linuxwas confirmed byte-identical toartemis-runner-5.2.0-linux.