> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/space/settings.md).

# Settings

### Available Run Solver versions in the app

DecisionRules can run your rules on more than one solver engine. Newer versions add capabilities, and every version gives the same results for the rules it can run. To call a specific version from your own code, see [Rule Solver API](/doc/api/rule-solver-api.md).

Choose which solver versions can be used when working with rules in this space's UI.

* **One version selected** — everything in the UI runs on that version.
* **Two versions selected** — a picker offers those two. The lower version is the default.

You can select up to two versions at a time. New spaces start with AERO (v2) selected.

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2FGuMgPDejo12obw5NtHgg%2FScreenshot%202026-09-30%20at%2015.05.43%201.png?alt=media&amp;token=e37c8e58-6813-41a5-85f2-d3e196796546" alt=""><figcaption></figcaption></figure>

#### What it affects

* **Test Bench** — the solver a rule runs on when you press Run.
* **Tests** — both the Tests tab of a rule and Space → Tests.
* **Jobs** — starting a job.
* **Integrations** — the solver version in the generated code samples.

{% hint style="warning" %}
It does **not** affect calls from your own code. Each API names its solver in the request, and get what it asks for whatever this setting says.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decisionrules.io/doc/space/settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.