- `github-copilot`

Anything outside that set falls through `selection.ts`'s `auto_pi` branch back

to PI.

It also supports custom `models.providers` entries when the selected model has

a non-empty `baseUrl` and one of these API shapes:

- `openai-responses`

- `openai-completions`

- `ollama` (OpenAI-compatible completions)

- `azure-openai-responses`

- `anthropic-messages`

Native provider ids such as `openai`, `anthropic`, `google`, and `ollama` remain

owned by their native runtimes. Use a distinct custom provider id when routing

an endpoint through Copilot BYOK.

Copilot BYOK endpoints must be public-network HTTPS URLs. The harness gives the

Copilot SDK a per-attempt loopback proxy URL, then forwards provider traffic

through OpenClaw's guarded fetch path so DNS pinning and SSRF policy stay

owned by OpenClaw. Use the native OpenClaw runtime for local Ollama, LM Studio,

or LAN model servers.

## BYOK

Copilot BYOK uses the SDK's session-level custom provider contract. OpenClaw

passes the resolved model endpoint, API key, bearer-token mode, headers, model

id, and context/output limits without moving provider transport logic into

core.

For example:

```json5

{

agents: {

defaults: {

model: "custom-proxy/llama-3.1-8b",

models: {

"custom-proxy/llama-3.1-8b": {

agentRuntime: { id: "copilot" },

},

},

},

},

models: {

mode: "merge",

providers: {

"custom-proxy": {

baseUrl: "https://api.example.com/v1",

apiKey: "${CUSTOM_PROXY_API_KEY}",

api: "openai-responses",

authHeader: true,

models: [{ id: "llama-3.1-8b", name: "Llama 3.1 8B" }],

},

},

},

}

```

BYOK sessions are separately keyed from subscription sessions and from other

endpoints or credential fingerprints. Rotating the key, headers, model, or

endpoint creates a fresh Copilot SDK session instead of resuming incompatible

state.

## Auth

custom location (for example, a shared mount for migration).

Live harness tests use `OPENCLAW_COPILOT_AGENT_LIVE_TOKEN` when a direct token

is needed. The shared live-test setup intentionally scrubs `COPILOT_GITHUB_TOKEN`,

`GH_TOKEN`, and `GITHUB_TOKEN` after staging real auth profiles into the isolated

test home, so passing a `gh auth token` value through the dedicated live-test

variable avoids false skips without exposing the token to unrelated suites.

is needed. The shared live-test setup intentionally scrubs

`COPILOT_GITHUB_TOKEN`, `GH_TOKEN`, and `GITHUB_TOKEN` after staging real auth

profiles into the isolated test home, so passing a `gh auth token` value

through the dedicated live-test variable avoids false skips without exposing

the token to unrelated suites.

## Configuration surface

`extensions/copilot/src/`:

- `copilotHome` — per-agent CLI state directory (defaults documented above).

- `model` — string or `{ provider, id, api? }`. When omitted, OpenClaw uses

the agent's normal model selection and the harness verifies the resolved

provider is in the supported set.

- `model` — string or `{ provider, id, api?, baseUrl?, headers?, authHeader? }`.

When omitted, OpenClaw uses the agent's normal model selection and the

harness verifies the resolved provider is supported.

- `reasoningEffort` — `"low" | "medium" | "high" | "xhigh"`. Maps from

OpenClaw's `ThinkLevel` / `ReasoningLevel` resolution in

`auto-reply/thinking.ts`.

## Limitations

- The harness only claims the canonical `github-copilot` provider at MVP.

Additional providers (BYOK or otherwise) should land in follow-up PRs that

ship the adapter alongside the wire-up.

- The harness claims `github-copilot` plus unowned custom BYOK provider ids.

Manifest-owned native provider ids stay on their owning runtime even when

`agentRuntime.id` is forced to `copilot`.

- The harness does not deliver TUI; PI's TUI is unaffected and remains the

fallback for whatever runtimes do not have a peer surface.

- PI session state is not migrated when an agent switches to `copilot`.