> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bluee.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Save one coding agent's managed configuration as a new revision



## OpenAPI

````yaml /openapi/next.yaml put /admin/harnesses/{harness}/managed-config
openapi: 3.1.0
info:
  title: Blue — Service Contract
  version: 0.1.0
  description: >
    The client-side contract the `blue` CLI expects from the provisioned
    service. The reference `control-api` implements it; any BYO service that
    honors these shapes can be swapped in. Gateway-mode inference JWT issuance
    is OPTIONAL — governance-only deployments need only `GET
    /governance-config`. CLI callers use OAuth 2.0 access tokens issued through
    RFC 8628 device authorization; dashboard callers use an HTTP-only Better
    Auth session cookie.
servers:
  - url: https://harness.example.com
    description: Replace with the Control API URL for your deployment.
security:
  - oauthDevice: []
tags:
  - name: System
    description: Service health and authenticated identity.
  - name: Configuration
    description: Personalized governance policy and client reconciliation state.
  - name: Gateway
    description: Per-user managed inference-gateway credential lifecycle.
  - name: Sessions
    description: Raw-session upload, metadata, and download lifecycle.
  - name: Administration
    description: Organization-administrator policy and client operations.
  - name: User management
    description: >-
      Organization user lifecycle, session revocation, and invitation
      operations.
  - name: Identity provisioning
    description: SCIM 2.0 user and group provisioning for an external identity provider.
paths:
  /admin/harnesses/{harness}/managed-config:
    put:
      tags:
        - Administration
      summary: Save one coding agent's managed configuration as a new revision
      operationId: updateHarnessManagedConfig
      parameters:
        - name: harness
          in: path
          required: true
          schema:
            type: string
            description: Harness key from the compiled registry
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateHarnessManagedConfig'
      responses:
        '200':
          description: Saved governance revision
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HarnessManagedConfig'
        '400':
          description: Harness or managed configuration is invalid
        '409':
          description: Base revision is stale
components:
  schemas:
    UpdateHarnessManagedConfig:
      type: object
      required:
        - base_revision
        - managed_config_yaml
      properties:
        base_revision:
          type: string
          format: uuid
        managed_config_yaml:
          type: string
          description: YAML mapping containing only the selected harness's managed settings
        version_requirement:
          type:
            - string
            - 'null'
          description: Optional semver range enforced for the installed harness
        allow_unverified_versions:
          type: boolean
          default: false
          description: >-
            Permit versions beyond Blue's certified ceiling when constrained by
            an explicit version_requirement
    HarnessManagedConfig:
      type: object
      required:
        - revision
        - harness
        - managed_config_yaml
        - allow_unverified_versions
      properties:
        revision:
          type: string
          format: uuid
        harness:
          type: string
          description: Harness key from the compiled registry
        managed_config_yaml:
          type: string
        version_requirement:
          type:
            - string
            - 'null'
        allow_unverified_versions:
          type: boolean
  securitySchemes:
    oauthDevice:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        OAuth 2.0 access token obtained through RFC 8628 at
        /api/auth/device/code and /api/auth/oauth2/token. The API enforces
        governance:read, session:write, and client-status:write as appropriate.

````