Skip to content

Commit a32eada

Browse files
committed
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.
1 parent fbdae89 commit a32eada

2 files changed

Lines changed: 7 additions & 4 deletions

File tree

‎DESIGN.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ as a document, and these are working surfaces.
125125
## Search
126126

127127
Two separate surfaces, never merged, and neither opens the other (a
128-
decision re-litigated more than once — see `docs/DECISIONS.md` → Search):
128+
decision re-litigated more than once):
129129

130130
- **The magnifier in the stage top bar is a per-page filter.** It scopes to
131131
whatever page it's on — Files filters files, Skills filters skills — and

‎README.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,12 @@ through picking a provider — Anthropic, OpenAI, Google, OpenRouter, Hugging
8787
Face, Groq, or another of the curated providers in
8888
[`packages/hub-client/src/catalog-seed-data.ts`](packages/hub-client/src/catalog-seed-data.ts)
8989
— and pasting their own key (or, for OpenRouter, completing a PKCE OAuth
90-
connect), proves it with a real call before storing anything, then deploys
91-
and confirms the default routines on the spot — no separate `bun run seed`
92-
step, no docs to read. Whichever provider they connect gets its own curated
90+
connect), which is stored right away — no separate `bun run seed` step, no
91+
docs to read. A wrong key isn't caught up front; it surfaces the first time
92+
it's actually dialed for real inference, through the same in-chat "Fix this
93+
connection" flow any credential failure uses. The bench's default agents
94+
deploy in the background — "Your workbench is ready — agents will come
95+
online shortly," no "Connecting…" wait in the browser. Whichever provider they connect gets its own curated
9396
catalog entry planted the same way `bun run seed` plants Anthropic's; see
9497
[docs/model-seeding.md](docs/model-seeding.md) for how that catalog data is
9598
curated and kept up to date.

0 commit comments

Comments
 (0)