Runner and Scripts
Choose where this Project's code runs and what runs there from Project Settings → Runner and Scripts.
Select a Runner
A Runner is Artemis Runner software on your workstation or server. It receives tasks, runs a downloaded copy of the Project's saved code, and sends logs and results back to Artemis. Select one from the Runner dropdown to make it the Project's default. Its hardware (CPU, cores, memory and GPU) shows once it has reported it.
If you have not connected a Runner yet, click Add new Artemis runner, which opens Platform Settings → Runners, then return here to select it.
The default is only a starting point. A Branch Validation can pick another Runner when you run a Script, and a Discovery Run saves its own Runner selection.
Scripts
A Script is a named, ordered set of Commands. Each Command belongs to one phase, and the phases always run in this order:
- Setup commands run once, for example to install dependencies, build the code and run the tests. If a setup command fails, the benchmark phase is skipped.
- Benchmark commands are the measured part. They can run several times and are the only place metrics are collected, including the custom metrics your benchmark writes. See Metrics.
- Teardown commands run once at the end to clean up generated files.
Click New script to create one, give it a name, add Commands to each phase and drag them into order. One Script is the Project's Default; use Set as default from a Script's actions to change it. Validations and Discovery Runs copy the Script when they start, so editing it later does not change runs that already happened.
Each Command runs from the root of the staged code in its own shell, so make every Command self-contained: select its runtime and activate its environment explicitly, and do not rely on a previous Command's cd. Commands should run without prompts and exit non-zero when their check fails.
Click Run to try a Script on the selected Runner. Each run shows the status, runtime and logs of every Command.
Ask the agent
Ask agent opens a chat that knows your Runner's hardware and the Scripts you already have. Ask it to set up Commands for your repository, review a failing Script, or suggest improvements for your hardware. If you would rather use your own coding agent, Ask local agent gives you a prompt to paste into it.