Integration pattern

Map product features to allowed configured agents.

The browser should name the product action. The server should choose the configured agent.

Pattern

Server mapping

const harnessByFeature = {
  contract_review: "chrn_...",
  game_generation: "chrn_..."
};

const harnessId = harnessByFeature[featureKey];

Rules

Do not let the browser submit arbitrary harness_id values.
Keep the mapping in trusted server configuration or a protected database table.
Use separate configured agents when purpose, data access, tools, permissions, model policy, or artifact contract differs.

Open standard

Server-side mapping from feature keys to chrn_ identifiers works because a configured harness is an addressable object returned only within the caller's scope, as UHP's Harnesses chapter defines it. See the Unified Harness Protocol's Harnesses chapter.

Create API Key

Ready to run this against a live workspace? Keys take under a minute.