Repository navigation
[0.1.47] - 2026-11-20
Fixed
-
Copilot agents work with Copilot CLI 1.0.113 and later again. Those CLIs
speak Copilot SDK protocol 4, which nogithub-copilot-sdk1.x release
supports, so every Copilot agent failed at startup withSDK protocol version mismatch: SDK supports versions 3-3, but server reports version 4whenever the
SDK reached such a CLI (for example throughCOPILOT_CLI_PATH, or an external
runtime_url). The Copilot provider now uses the SDK's renamed 2.x release,
microsoft-copilot-sdk>=2.0.1,<3(still imported ascopilot), which speaks
protocol 4.Behaviour is otherwise unchanged. The Copilot runtime still runs as a child
process that inherits Conductor's environment (COPILOT_CLI_PATH, CAPI and
integration-id variables) rather than SDK 2.x's new in-process default, so
dead-runtime recovery and crash isolation keep working, andruntime.provider
custom routing still sends every model to the configured endpoint.SDK 2.x cannot talk to protocol-3 CLIs (Copilot CLI 1.0.112 and earlier). If
COPILOT_CLI_PATHorruntime_urlpoints at one, Conductor now stops with a
non-retryable error naming the CLI to update instead of retrying; unset
COPILOT_CLI_PATHto let the SDK download a matching CLI. Install-script
upgrades replace the old SDK automatically. In an environment you manage
yourself,pip uninstall github-copilot-sdkbefore upgrading, because both
distributions install the samecopilotpackage. Existing Docker and ACA
runner images keep their own SDK and CLI pair and keep working. To move them
to SDK 2.x, rebuild ACA images with--build-arg CONDUCTOR_VERSION=v0.1.47(or a later tag or SHA), because the
Dockerfile's default pin predates it; custom images must update their
equivalent version pins. Rebuild that way any image that supplies its own
Copilot CLI newer than 1.0.112. (#651)