Skip to main content
An executor is the coding agent that does the work inside the runner. Each task runs with one executor. You set executors up once as executor profiles, then pick one when you create a task.

​
Agents you can use

When you add an executor profile, the Agent field offers two agents: A custom executor is a profile you build on one of these agents: your own name, model and agent configuration (see Advanced configuration). Self-hosted installs can also replace the runner image behind each agent.

​
Personal and organization profiles

A profile lives in one of two scopes. In the task picker, personal profiles come first. Organization profiles are labelled — organization.

​
Add a profile

1

Open Settings → Executors

The page is titled Executors.
2

Click Add executor

Use it under My workspace. Organization admins see an add button under Organization too.
3

Fill in the form

Give it a Name, such as Code review. The name appears in the task picker. Choose the Agent. Under Model, keep Use runner default or choose Custom model identifier.
4

Save

Save the profile. It now shows in the task picker.
Names can’t contain / or \, and can’t start with - or ..
Saving checks the form only. It doesn’t test your credentials or whether the model exists. Anything you leave unset is inherited from the runner’s default configuration.

​
Advanced configuration

Open Advanced configuration to edit the Configuration JSON directly. It must be a JSON object up to 32 KiB. A blank configuration is the same as {}. Format JSON tidies it. The JSON is merged into the agent’s own settings in the runner. Some keys are managed by Bellows and have no effect. The form lists any you set. The same section has gate repair rounds: how many times a task on this executor may try to repair a failed gate on its own. The default is 3, the maximum is 10, and 0 turns repair off. The value is fixed when the task is created. See Gates.
Keep API keys out of the configuration JSON. Set them as environment variables under Settings → Workspace (your own) or Settings → Organization (shared). The form links to Workspace settings.

​
Pick an executor for a task

In the New task composer, the Executor chip next to Repository lists every profile you can use. Suspended profiles are not listed. If you don’t pick one, the task uses your default. If you have no usable profile, Bellows refuses the task and links to Add an executor in Settings.

​
Defaults and suspending

  • Make default in a row’s actions saves your own preference. The default row shows a Default tag, and the composer selects it for you. Each member chooses their own default, including among organization profiles.
  • Suspend stops a profile from launching tasks. A suspended profile can’t be a default. Resume brings it back.
  • Remove deletes a personal profile. Admins can Delete an organization profile, or Make personal to move it into their own list.
Follow-ups and retries keep the executor of the original task.

​
From the CLI

bellows executor list shows the profiles you can use.