Skip to main content
Fleet Prime Agent brings its own provider credentials: you pick the provider and model per session. Provider and model support comes from the pinned upstream engine; Fleet surfaces the catalog and stores nothing itself.

​
Add a provider

Two equivalent paths:
  • Settings → Providers in the web workspace.
  • /login in the composer.
Credentials are stored by the engine under ~/.prime/agent/ and are shared with any prime-agent install on the same machine, so signing in once covers both the web workspace and the terminal.

​
OAuth providers

Providers that use OAuth instead of a static API key complete their flow through the workspace (POST /api/chat/providers/oauth). The engine refreshes tokens for long-running sessions.

​
OpenAI-compatible endpoints

For self-hosted or OpenAI-compatible servers, the workspace can probe an endpoint’s /v1/models listing (POST /api/chat/models/discover) and register the discovered models. Custom provider definitions are kept by the server’s custom provider store.

​
Pick a model

Choose the model in the composer’s model picker when starting a session, or switch it mid-session (POST /api/chat/model). The model catalog comes from the engine’s model registry (GET /api/chat/models), including thinking-level support per model.

​
Adding a new provider to the engine

Engine features, including providers and models, are developed in PrimeIntellect-ai/prime-agent, not in this repository. Contribute the provider upstream, then upgrade Fleet’s pinned runtime to a release that includes it. See Runtime pin and releases.
Last modified on August 30, 2026