Fleet & Profiles

What it is

Layered configuration for the coder fleet — reusable profiles (model caps, coder tool, env, MCP toggles) that bind to projects, with overrides, resolving to one effective config per project.

Operator surface

  • Profiles — fleet_profile_list / _get / _create / _update / _delete / _clone and profile env (fleet_profile_env_set / _remove / _list).
  • Bindings & overrides — fleet_project_bind, fleet_project_unbind, fleet_project_override, fleet_project_override_env_set / _remove.
  • Resolution — fleet_resolve and fleet_resolve_env (show the merged result and where each value came from).
  • Related coder controls — coder_spawn, coder_list, coder_kill and the on-demand coder tools.

REST is FleetProfileController / CoderFleetController.

How it works

FleetProfileRecord lives in the control plane and supports inheritance (a profile can extend a parent); ProjectFleetBinding attaches a profile to a project and layers per-project overrides on top. fleet_resolve merges system defaults → parent profile → profile → project overrides and returns FieldSources so you can see exactly which layer set each value — the same resolved config that governs how coders are spawned (see Agents) and what environment and MCP capabilities they get.