From a32eadaabdca4800a273d88202e6f5024c60f21a Mon Sep 17 00:00:00 2001 From: Sawyer Cutler Date: Fri, 28 Aug 2026 05:29:30 -0700 Subject: [PATCH] Update docs: onboarding stores the key first, validates on first use README overstated onboarding: it said connecting a provider "proves it with a real call" and "confirms the default routines on the spot." CL-6123 dropped the blocking probe (key is stored immediately, a bad one surfaces on first real use via the in-chat "Fix this connection" flow) and CL-6457 moved default-routine deploys to a background drain. Also drops DESIGN.md's citation of docs/DECISIONS.md, which does not exist. Fixes CL-7143. --- DESIGN.md | 2 +- README.md | 9 ++++++--- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/DESIGN.md b/DESIGN.md index 0dbb6d538..148382372 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -125,7 +125,7 @@ as a document, and these are working surfaces. ## Search Two separate surfaces, never merged, and neither opens the other (a -decision re-litigated more than once — see `docs/DECISIONS.md` → Search): +decision re-litigated more than once): - **The magnifier in the stage top bar is a per-page filter.** It scopes to whatever page it's on — Files filters files, Skills filters skills — and diff --git a/README.md b/README.md index 62007603f..c40c28111 100644 --- a/README.md +++ b/README.md @@ -87,9 +87,12 @@ through picking a provider — Anthropic, OpenAI, Google, OpenRouter, Hugging Face, Groq, or another of the curated providers in [`packages/hub-client/src/catalog-seed-data.ts`](packages/hub-client/src/catalog-seed-data.ts) — and pasting their own key (or, for OpenRouter, completing a PKCE OAuth -connect), proves it with a real call before storing anything, then deploys -and confirms the default routines on the spot — no separate `bun run seed` -step, no docs to read. Whichever provider they connect gets its own curated +connect), which is stored right away — no separate `bun run seed` step, no +docs to read. A wrong key isn't caught up front; it surfaces the first time +it's actually dialed for real inference, through the same in-chat "Fix this +connection" flow any credential failure uses. The bench's default agents +deploy in the background — "Your workbench is ready — agents will come +online shortly," no "Connecting…" wait in the browser. Whichever provider they connect gets its own curated catalog entry planted the same way `bun run seed` plants Anthropic's; see [docs/model-seeding.md](docs/model-seeding.md) for how that catalog data is curated and kept up to date.