Skip to content

docs: connecting a provider happens in the Providers sidebar section (issue #67) - #73

Merged
SebConejo merged 2 commits into
mainfrom
fix/issue-67-providers-connect
Aug 18, 2026
Merged

SebConejo merged 2 commits into
mainfrom
fix/issue-67-providers-connect

Conversation

@SebConejo

Copy link
Copy Markdown
Member

Applies the recommended options for all four findings of #67 (batch pass, 2026-08-18), each live-verified on a local instance at platform HEAD before writing:

  1. The connect flow moved. Seven pages sent users to a Routing page of provider tiles that no longer exists. Verified live: the sidebar carries Providers → Local / Usage-based / Subscriptions, each provider is a card with a Connect button, custom providers are added from Usage-based, and a harness's Routing page holds tiers, models, and fallbacks only. The four provider pages and the three error pages (M100/M101/M102, descriptions included) now describe that flow. The obsolete two-tab step on the subscriptions page is gone (the panel opens the right form directly).
  2. Model lists are cached per connection. New "Refreshing the model list" section (the Refresh models button was verified live on the Routing page), a pointer from the subscriptions page, and the Kimi Coding Plan id note (kimi-k3 → k3, plus the two new ids).
  3. Meta ships. Verified live: the Meta card is on the Usage-based page. It joins the supported-providers table and the key-prefix table — its LLM_ prefix IS enforced by the form, unlike the reversed Bedrock/NVIDIA rows.
  4. The screenshot exists now. Captured on the live instance and shipped as images/providers-usage-based.png under the connect steps: sidebar Providers section, connections table, card grid with Connect buttons. Supersedes the two unfulfillable image requests of Docs audit — providers (api keys, subscriptions, local, custom) — 2026-08-11 #55.

Coherence: GREEN. Closes #67.

…(issue #67)

Live-verified on a local instance at platform HEAD: the sidebar carries
Providers → Local / Usage-based / Subscriptions, each provider is a card
with a Connect button, custom providers are added from Usage-based, and
the harness Routing page holds tiers only. Seven pages rewritten (four
provider pages, three error pages with their descriptions). The model
list is documented as cached per connection with the Refresh models
remedy and the Kimi id rename. Meta joins the provider and prefix
tables (its LLM_ prefix is enforced by the form). The Usage-based
screenshot ships as the connect-flow image.
@SebConejo
SebConejo merged commit ce48b7f into main Aug 18, 2026
1 check passed
@SebConejo
SebConejo deleted the fix/issue-67-providers-connect branch August 18, 2026 16:56
SebConejo pushed a commit that referenced this pull request Aug 19, 2026
Window was one merged PR. #2734 shows as merged on GitHub but its base
is a feature branch, so it is off main and was excluded.

The PR falsified no docs sentence. All five findings are pre-existing
defects on the surface it lands on: a silent tool-call model filter, two
impossible response bodies in the API reference, the Ollama / Ollama
Cloud name collision, and the undocumented third-party capability
catalog.

Also reconciles decisions.md finding #67-2 to fixed: docs PR #73 merged
on 2026-08-18 and the line still read "PR pending", which the draft
published as fact until round 3 of verification caught it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs audit — 2026-08-15 (PRs #2700–#2717)

1 participant