An Open Source Contribution

Amplifier Builds Amplifier

The GitHub Copilot Provider Story

The Constraint

Frontier Models. Without the Overhead.

Model Sprawl

Anthropic, OpenAI, and more. Serious experimentation means access to all of them.

Infrastructure Tax

Spinning up LLM infrastructure with auth layers and endpoints takes time and expertise.

Enterprise Approval Gap

Using models inside a company still requires compliance and security sign-off.

Every one of these constraints has the same answer: GitHub Copilot — frontier models from multiple providers, no additional setup required, no LLM infrastructure to own.

The Gap

Why not use GitHub Copilot in Amplifier?

That question didn't have an answer yet.
Because the GitHub Copilot provider for Amplifier didn't exist.

Discovery

Feb 10, 2026 — V0 Ships

Built in One Week

From zero to working provider. Streaming support, SDK driver, converters, model discovery, test suite. All delivered.

Official Launch

The Amplifier team saw what it could unlock for the ecosystem and adopted it as a native Amplifier provider.

Momentum

V1: Releases Shipping, SDK Breaking

v1.0.1

Feb 17 — 18 models, 692 tests, 95% coverage

v1.0.2

Feb 28 — SDK 0.1.28 update

v1.0.3

Mar 7 — SDK 0.1.30 update

v1.0.4

Mar 8 — SDK 0.1.32 update

Keeping pace with a fast-moving Copilot SDK — same-day and same-week absorption of every breaking change. The codebase earned each update.

The Problem

Hotfixes on Hotfixes

SDK Imports Scattered

Copilot SDK imports landed in the middle of provider logic — no clean boundary.

Tests Tightly Coupled

Tests were reliable but coupled to implementation details. Any SDK change rippled through.

No Formal Specification

Only code comments and tribal knowledge. No contract-driven development.

The work to make any small change was growing. Something had to change.

The Pivot

Four Goals for V2

1. Match the Provider Contract

Indistinguishable from any other first-class Amplifier provider. 100% contract compliance.

2. Isolate the SDK Layer

All Copilot SDK imports in a single quarantine module. When SDK breaks, only that module changes.

3. Solid Tests, No Shortcuts

No MagicMocks. Actual runtime types. TDD discipline applied consistently.

4. Contract-Driven Development

Behavioural specs in markdown. Readable by humans and AI assistants alike.

The Twist

What if I used Amplifier
to build the Amplifier provider?

amplifier-expert

·

core-expert

·

python-dev

·

superpowers

·

git-ops

·

dot-graph

Amplifier's own agent ecosystem did the heavy lifting — architecture advice, code generation, quality review, and git operations — all orchestrated through Amplifier itself.

The provider was built by the same ecosystem it now powers.

V2.0.0

175 Files. 5 Days. 100% AI-Assisted.

175

Files Changed

+36K

Lines Added

−31K

Lines Deleted

858

Tests Passing

Validation

SDK 0.2.x Breaks. Architecture Holds.

V1: Entangled

SDK breaking change → touches provider logic, tests, configuration. Everything ripples.

V2: Isolated

SDK breaking change → contained in sdk_adapter/ layer only. Provider-Amplifier integration untouched.

Copilot SDK 0.2.1 relocated PermissionRequestResult and SubprocessConfig.
Isolated to one module. The architecture absorbed the change without a ripple.

The re-architecture goals were validated in production.

The State Today

1,218 Tests · 98% Coverage

64

Days Active

6

SDK Breaks Absorbed

8+

Releases Shipped

0

Lint/Type Errors

The Unlock

15+ Frontier Models. Zero API Cost.

15+

Frontier Models

$0

Additional API Cost

Enterprise Compliant

Everyone with a GitHub Copilot subscription
can now use Amplifier at zero additional cost.

Thank You