Skip to main content
Pioneer needs a model source before it can answer in threads or run model-backed tasks. That source can be a cloud API, a local model runtime, or an OpenAI-compatible endpoint. Some agent tools, such as Codex CLI, are configured separately from ordinary API providers because they run through their own CLI workflow on the gateway host. Provider setup follows the same flow for each provider. Connect the desktop app to the gateway, open Providers from the bottom bar, choose a provider type, enter its credentials or endpoint details, save it, and select a model in a thread. Provider configuration belongs to the current workspace on the gateway, not to the desktop app. The gateway’s secret store holds API keys and tokens. If you configure a provider in Default Workspace and switch to Client A, configure that provider again for Client A. A different gateway has its own provider configuration.
Provider requests are made by the gateway host. A remote gateway needs network access to the provider even if your desktop computer already has access.

​
General connection flow

Use this flow for any supported provider:
1

Choose the gateway and workspace

Connect the desktop app to the gateway and switch to the workspace that should own this provider configuration.
2

Open Providers

Click the providers icon in the bottom bar to open Providers.
3

Add the provider

Choose the provider type and enter the required key, endpoint, region, deployment, or local runtime address.
4

Save in the workspace

Save the provider configuration and confirm it appears for the current workspace.
5

Test with a thread

Create a thread, select the provider and model, and send a short test message.
Some providers can list models automatically. Others require you to enter the exact model ID. If model listing does not work, copy the model ID from the provider dashboard or runtime and test it with a small prompt. When a listed model exposes reasoning controls, Pioneer can show a reasoning effort selector next to the model selection. Changing effort affects the next turn that uses that model selection. If the model does not advertise reasoning effort options, the selector is hidden and Pioneer sends the turn without an explicit effort value.

​
Supported providers

Pioneer supports dedicated provider integrations, local runtimes, OpenAI-compatible endpoints, and separate CLI agent runtimes. Use Supported Providers when you need the broader compatibility list. Use CLI Runtime API only when you are building or debugging CLI-backed model selection.

​
Choosing a provider

Start with a provider you already have access to. Use your organization’s cloud account when it manages one, a local runtime when the gateway host provides it, or a router when you want several models behind one integration. Model sources differ in tool support and operational behavior. Before using one for tool-heavy or scheduled work, confirm access, supported tool features, authentication, context size, cost, and latency. For models with reasoning controls, start with the provider’s default effort unless you know the tradeoff you want. Higher effort can improve harder reasoning tasks, but it may also increase latency or cost depending on the provider.
Make sure you configured it in the same workspace and gateway you are currently using.
Try entering a model ID manually. Some providers do not expose model listing in a way Pioneer can use.
Check the key, token scope, account status, endpoint, region, deployment name, and gateway environment.
Check network access, proxy settings, firewall rules, and DNS from the gateway machine.

​
Further reading