Skip to content

Fix README onboarding claims: key stored first, deploy is async #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheGreatAxios merged 1 commit into from
Aug 29, 2026
Merged

Fix README onboarding claims: key stored first, deploy is async #439

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion DESIGN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
9 changes: 6 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading