`ghd` in action

A real terminal session, recorded 2026-10-24 against talos-hq/clud on GitHub: ten agents reading pull requests at once through the ghd daemon, then again a moment later, and the same read through plain gh for comparison.

bash — ghd demo

3 GraphQL points

for 11 cold reads across 6 PRs: requests for one repo that arrive together share one aliased query. gh spends one query per call, so 11.

0 points

for the second round of 10 reads: 5 proven unchanged by ETag 304s, which GitHub does not charge, and 5 served fresh.

5 ms vs 476 ms

a fresh warm read through ghd, against the same read through gh. A read that needs revalidation costs one REST round trip, about 0.4 s.

Chapters

Recorded with script(1); the player replays its real output bytes. Pauses longer than 1.2 s are shortened, and each time line shows the real duration. The demo shortens the fresh window to 400 ms (GHD_FRESH_MS) so the second round falls outside it; the default is 2 s.