Thinking Partner,
Not Typist

Amplifier Stories

AI upstream of code shipped amplifier-chat

The Frame

The real leverage is upstream of the keyboard

We already trust AI to type code. But amplifier-chat is what happens when AI joins the design thinking too — not just the typing.

And this isn't a thought experiment. It shipped.

Proof — This Shipped

amplifier-chat is a public, shipped browser chat UI

microsoft/amplifier-chat installs into amplifier-distro via the amplifierd.plugins entry point — a real plugin, not a demo.

So who built this real, maintained product?

84

Pull requests (all states)

102

Commits on main

Public

Shipped & maintained repo

/chat/

Endpoints served by the plugin

The Builder

One developer wrote most of it — aloud, in the open

Samuel Lee authored 78 of the 102 commits on main in a dense March-2026 burst — some days landing 7 to 9 commits.

At that pace, execution speed becomes the problem.

78

of 102 main commits by Samuel Lee

7–9

commits/day on peak March days

287

total commits across all refs

Mar 2026

the dense build window

The Tension

The UI didn't crawl — it outran unaided design

A 1-line scaffold on 2026-03-03 became 4,625 lines the same day, then climbed toward five figures. Raw execution outpaces design thinking that isn't captured.

Something had to hold the shape at that speed.

1

1 line — scaffold, 2026-03-03

2

4,625 lines — same day, 2026-03-03

3

4,959 lines — 2026-03-05 (PR #5)

4

11,000 lines — index.html today

The Mechanism

The design thinking got captured, not lost

16 per-feature plan/spec docs — 12,265 lines total, largest 1,578 — were authored alongside the code between 2026-03-09 and 03-26. Durable specs kept pace with the build.

And paperwork? No — these steered a living product.

16

plan/spec docs authored alongside code

12,265

total lines across those docs

1,578

lines in the largest single spec

03-09→26

the design-arc dates (March 2026)

The Turn

Captured design became a large, living surface

Those specs steered a single-page app that today totals 12,594 lines of front-end — index.html (11,000) plus feedback-widget.js (1,318) and loading.html (276) — and it's still maintained.

Which brings us to the precise snapshot of what shipped.

12,594

total front-end lines shipped

11,000

lines in index.html (the SPA)

1,318

lines in feedback-widget.js

276

lines in loading.html

The Payoff

On 2026-03-22/23, the UI stood at exactly 8,942 lines

Verified at commits 3e6c969 and e136fff: index.html measured 8,942 lines exactly — a real product grown from design thinking captured as specs, not typed cold.

That's what AI-as-thinking-partner actually shipped.

8,942

lines of shipped UI, measured exactly at two commits on 2026-03-22/23

The Takeaway

Point AI upstream. Capture the thinking as specs.

Aim AI at the design, not just the keyboard — and one developer can ship a real, maintained product like amplifier-chat.

Thinking partner, not typist.

Sources

Research Methodology

SHIPPED / PUBLIC / MAINTAINED

Repository: microsoft/amplifier-chat (independently re-verified against a fresh clone; git remote confirmed).

Data as of: last commit 2026-07-13 (dependabot dependency bumps); build window 2026-03-03 through mid-April 2026.

Commands run:

Commit counts: git rev-list --count origin/main (102) · git rev-list --all --count (287)
Authorship: git shortlog -sne origin/main (Samuel Lee 78 of 102)
UI line counts: git show <commit>:src/chat_plugin/static/index.html | wc -l (8,942 at 3e6c969 / e136fff; 11,000 current)
Front-end total: wc -l on index.html + feedback-widget.js + loading.html (12,594)
Design docs: enumerated docs/**/(plans|specs)/*.md (16 docs, 12,265 lines, largest 1,578)
PRs: gh pr list -R microsoft/amplifier-chat --state all (84)
Plugin wiring: git show origin/main:pyproject.toml | grep -i plugins (amplifierd.plugins)

Primary contributor: Samuel Lee — 78 of 102 main commits (Paul Payne 9, "Amplifier Dev" 7, dependabot 7, Salil Das 1).

Gaps: The story-level "5,184-line spec," "163 commits," and the "experience, not the token" principle could NOT be reproduced in-repo and are deliberately excluded from this deck.

Thinking Partner,Not Typist