Skip to main content

Project Settings

Configure your project's execution environment and project-level details from the Settings tab inside any project. The Settings page has two sections accessible from the left sidebar: Execution and Project.


Essential Guide

Artemis validates your code by running it with runners.

If you already have a way to compile, verify correctness, and measure performance for your project, set up the commands below. Otherwise, consider these two options to get started:

Artemis Agent

The agent analyses your repo to figure out how to build, test, and benchmark it — including detecting your runner's hardware.

Essential Guide — Artemis Agent and Agent Skill

Click Start a coding task to launch the agent. It will inspect your repository and suggest the right compilation, test, and benchmark commands for your project.

Agent Skill

Run the /repo-setup agent skill to configure build, test, and benchmark commands directly from your terminal. Push to Git and Artemis syncs automatically.

See Artemis Agent Skills for a full guide.


Execution

Runner

Select a runner from the Runner Name dropdown. The selected runner will pick up all execution tasks for this project. If you haven't connected one yet, see Artemis Custom Runner.

Build Commands

Build commands configuration

Configure the command for each execution stage:

  • Compilation — compiles the code and ensures it's free from syntax errors and ready for execution.
  • Test — verifies correctness after each change. Make sure these tests cover the code Artemis will optimise — not just compilation.
  • Benchmark — measures performance (speed, memory, etc.). Output results to artemis_results.json or .csv so Artemis can compare versions.

Each command can be edited, duplicated, run manually, or deleted using the action icons on the right.

Custom Metrics

Track metrics beyond the built-in runtime, CPU, and memory. Have your benchmark script write an artemis_results.json or .csv file to the project root before exiting — Artemis will pick up any values and display them as additional score metrics.

tip

See the File format & examples section in the Custom Metrics panel for the expected JSON/CSV schema.

Agent Assistant

The right-hand panel contains a built-in chat agent that is hardware-aware — it knows your runner's CPU, memory, and platform — and has full context of the commands you've already configured.

You can ask it to:

  • Set up build commands from scratch based on your repo
  • Review and fix issues in existing commands
  • Suggest improvements based on your runner's hardware
  • Troubleshoot failures in any execution stage

Project

The Project section contains project-level configuration for your repository connection and settings.

Project Settings

Fields

  • Name — the display name of your project.
  • Description — an optional description.
  • Owner — the owner of the project.
  • Git Repository — the URL of the connected Git repository.
  • Git Branch — the branch Artemis will use.
  • Git Commit — optionally pin to a specific commit hash.
  • Code Authors — the authors associated with this project.
  • Git Key — the authentication key used to access the repository. See Using private code repositories for setup instructions.
  • Auto Pull Request — when enabled, Artemis will automatically open a pull request for accepted code changes.

Next Steps

After configuring your settings:

Validate your new code versions using these commands