You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ec66d0a
Browse filesBrowse the repository at this point in the historyBrowse files
fix: offer Altimate Base to every user on an implicit free Zen default
Closes#1301.
The 0.11.0 migration to Altimate Base only fired when `opencode/big-pickle` was
in persisted `recent`, which only a picker writes. 1,027 of 1,031 Big Pickle
machines were implicit-default users with no `recent`, so on 0.11.x they were
silently rerouted to the next public free Zen model (`nemotron-3.5-lightning-free`)
and never offered Base.
TUI (`packages/tui`)
- `usesImplicitFreeDefault()`: eligibility is now "launch default resolves to a
free public OpenCode Zen model (Big Pickle included), no explicit selection,
no project provider allowlist", judged on `fallbackModel()` so a restored
session model is never mistaken for the default.
- One startup decision in `app.tsx` replaces the two racing effects: prior
decline → skip; registered Base → migrate silently; returning user (prompt
history at startup, project sessions, or a recent model) → migration
disclosure; a brand-new user keeps the first-run welcome picker. A
`dialog.replace()` that loses a race falls through instead of latching.
- Escape / Ctrl-C on the migration disclosure now routes through the close
guard to the same path as explicit No: the decline is persisted AND the
provider picker opens, instead of stranding the user on the retired model.
- Migration copy names the actual free model being moved.
- Telemetry: `altimate_base_confirm_shown` / `altimate_base_choice` /
`altimate_base_register_result` now fire for the migration origin (they were
gated on the first-run funnel, so the migration was invisible), with an
`origin` field.
- `PromptHistory` exposes `loaded()` and a one-time `hadHistoryAtStartup()`.
Server (`packages/opencode`)
- `Provider.defaultModel()` and the ACP default scan: a registered Altimate Base
now outranks the keyless public Zen tier (`options.apiKey === "public"`) and
nothing else; a keyed Zen account or any BYOK provider still wins. Headless
hosts (`serve` behind the VS Code extension) therefore land on Base once the
install is registered.
Tests: `test/context/local.test.ts` (free-Zen detection, eligibility,
recents rewrite), `test/cli/tui/dialog-altimate-base.test.tsx` (migration
telemetry without first-run, Escape → decline + picker, generalized copy),
`test/provider/provider.test.ts` and `test/acp/default-model.test.ts` (public
tier vs keyed Zen vs registered Base, recents precedence unchanged, Big Pickle
never migrated headlessly).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_012uzYijGHdhxvpUzhgWxayo
Copy file name to clipboardExpand all lines: docs/docs/configure/providers.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ registration request; **No** is selected by default. After registration, the mod
68
68
explicit model is selected. Big Pickle is retired as a new selection — it no longer appears in the
69
69
picker or the full model catalog for users choosing a model for the first time. Users already on
70
70
Big Pickle are still detected on launch and offered Altimate Base through the same consent gate.
71
+
If you decline the default switch, `declinedManagedBaseDefault: true` in the state directory's `model.json` keeps public Zen ahead of registered Base for headless and ACP defaults, with Base used only as a last resort; accepting migration or explicitly selecting Base clears the flag.
71
72
72
73
Official release binaries embed the current gateway endpoint at build time. Operators and local
73
74
development can override it without changing code:
Copy file name to clipboardExpand all lines: docs/docs/reference/telemetry.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,8 +57,8 @@ We collect the following categories of events:
57
57
|`onboarding_started`| The first-run setup gate opened (fresh launch with no usable model). |
58
58
|`model_picker_shown`| The provider picker was displayed. `trigger` distinguishes the first run from `/connect`, from declining Altimate Base, and from the prompt gate. |
59
59
|`provider_selected`| A provider row was chosen — `altimate_gateway`, `altimate_base`, `anthropic`, `openai`, `google`, `search_all`, or `other` for anything outside the curated five. `provider_id` carries the raw id only for publicly-known providers, so a provider you named yourself in config is reported as `other` with no name attached. `via_search` marks a pick made inside the full catalogue after choosing "Search all providers…". **Choosing search emits this event twice for one user** — once as `search_all`, then again with the provider actually chosen — so count distinct users or filter on `via_search`, not raw event count. Recorded at the moment of choice, so a sign-in that is then cancelled still counts. |
60
-
|`altimate_base_confirm_shown` / `altimate_base_choice`| The Altimate Base disclosure was shown (`welcome` or `model` origin), and what the user decided (`accept`/`cancel`). |
61
-
|`altimate_base_register_result`| The consented registration outcome: `success`, `rate_limited`, `unavailable`, `network`, or `error`. No credential or gateway response body is included. |
60
+
|`altimate_base_confirm_shown` / `altimate_base_choice`| The Altimate Base disclosure was shown, and what the user decided (`accept`/`cancel`). `origin` is `welcome`, `model`, or `migration` (returning free-default users offered Altimate Base on launch); required for the disclosure event and optional for the choice event. |
61
+
|`altimate_base_register_result`| The consented registration outcome: `success`, `rate_limited`, `unavailable`, `network`, or `error`. Optional `origin` is `welcome`, `model`, or `migration` (returning free-default users offered Altimate Base on launch). No credential or gateway response body is included. |
62
62
|`gateway_device_code_issued`| The Altimate Gateway authorize URL was built and the browser open attempted. **Name note:** the flow is a browser loopback OAuth — there is no device code. The name follows the original event spec. |
63
63
|`gateway_auth_completed` / `gateway_auth_failed`| Gateway sign-in outcome. `reason` is `timeout`, `denied`, or `error` — never the underlying message, which can contain the instance name. An unrecognised callback state does not reject the pending attempt, so a CSRF mismatch surfaces as `timeout`. |
64
64
|`instance_connected`| Credentials received and saved. `time_to_connect_ms` runs from the start of the authorize call, so it includes the browser launch. No instance or tenant name is sent. |
0 commit comments