@@ -150,6 +150,12 @@ the same directory), or `~/.openclaw/agents/<agentId>/copilot` otherwise.
|
150 | 150 | Override with `copilotHome: <path>` on the attempt input when you need a |
151 | 151 | custom location (for example, a shared mount for migration). |
152 | 152 | |
| 153 | +Live harness tests use `OPENCLAW_COPILOT_AGENT_LIVE_TOKEN` when a direct token |
| 154 | +is needed. The shared live-test setup intentionally scrubs `COPILOT_GITHUB_TOKEN`, |
| 155 | +`GH_TOKEN`, and `GITHUB_TOKEN` after staging real auth profiles into the isolated |
| 156 | +test home, so passing a `gh auth token` value through the dedicated live-test |
| 157 | +variable avoids false skips without exposing the token to unrelated suites. |
| 158 | + |
153 | 159 | ## Configuration surface |
154 | 160 | |
155 | 161 | The harness reads its config from per-attempt input |
@@ -314,13 +320,19 @@ right scope, and `session_status: "current"` resolves to a stale
|
314 | 320 | sandbox key. The bridge builder is in |
315 | 321 | `extensions/copilot/src/tool-bridge.ts` and mirrors the PI |
316 | 322 | authoritative call at |
317 | | -`src/agents/pi-embedded-runner/run/attempt.ts:1029-1117`. Two PI fields |
318 | | -are intentionally **not** forwarded at MVP and tracked as follow-ups: |
319 | | -`sandbox` (the harness does not yet route through `resolveSandboxContext`) |
320 | | -and the PI tool-search/code-mode machinery |
321 | | -(`toolSearchCatalogRef`, `includeCoreTools`, |
322 | | -`includeToolSearchControls`, `toolSearchCatalogExecutor`, |
323 | | -`toolConstructionPlan`), which has no analog at the SDK boundary. |
| 323 | +`src/agents/pi-embedded-runner/run/attempt.ts:1029-1117`. `runAttempt` |
| 324 | +already resolves sandbox context through the shared |
| 325 | +`resolveSandboxContext` seam, passes the SDK an effective working |
| 326 | +directory, and forwards `sandbox` plus the subagent-spawn workspace into |
| 327 | +the tool bridge. The bridge also forwards the bounded tool-construction |
| 328 | +controls it can enforce at the SDK boundary: `includeCoreTools`, the |
| 329 | +runtime tool allowlist, and `toolConstructionPlan`. |
| 330 | + |
| 331 | +The remaining PI tool-search/code-mode fields are intentionally **not** |
| 332 | +forwarded at MVP and tracked as follow-ups: `toolSearchCatalogRef`, |
| 333 | +`includeToolSearchControls`, and `toolSearchCatalogExecutor`. Those |
| 334 | +controls drive PI's native tool-search UI and have no direct Copilot SDK |
| 335 | +analog yet. |
324 | 336 | |
325 | 337 | ### Session-level GitHub token |
326 | 338 | |
|
