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
fix: revert model ID rename (backward-compat) + resolve review comments
Addresses two review findings:
1. cubic P1 — renaming the internal model ID from `altimate-default` to
`altimate-llm-gateway` broke backward compatibility. Opencode
persists selected model IDs to `model.json` (favorites, recents,
variants) and users can pin `model: altimate-backend/altimate-default`
in their opencode.json. After the rename those references would
silently go stale. Keep the ID as `altimate-default`; the polish the
user actually wanted was the display name, which stays as
"Altimate LLM Gateway". Added a comment explaining why the ID is
preserved. Rephrased the auto-selection tip in
`docs/docs/configure/providers.md` to refer to the display name
rather than the internal ID.
2. Coderabbit — the custom-URL example in `docs/docs/getting-started.md`
used `api-url::instance-name::api-key` which is ambiguous; the parser
requires `http(s)://`. Replaced with a concrete
`https://api.example.com::...` example and added a sentence stating
the scheme is required.
Also reverted provider.ts, acp/agent.ts, provider.test.ts, and
release-v0.5.20-adversarial.test.ts to use the original `altimate-default`
ID.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/docs/configure/providers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Managed LLM access with dynamic routing across Sonnet 4.6, Opus 4.6, GPT-5.4, GP
39
39
For pricing, security, and data handling details, see the [Altimate LLM Gateway guide](https://datamates-docs.myaltimate.com/user-guide/components/llm-gateway/).
40
40
41
41
!!! tip "Automatic model selection"
42
-
When Altimate credentials are configured and no model is explicitly chosen, `altimate-backend/altimate-llm-gateway` is selected automatically. You can override this by setting `model` in your config or by restricting the `provider` section to specific providers only.
42
+
When Altimate credentials are configured and no model is explicitly chosen, the Altimate LLM Gateway is selected automatically. You can override this by setting `model` in your config or by restricting the `provider` section to specific providers only.
Copy file name to clipboardExpand all lines: docs/docs/getting-started.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
@@ -94,10 +94,10 @@ For example: `acme::your-api-key` — this uses the default API URL `https://api
94
94
-**Instance Name** — the subdomain from your Altimate dashboard URL (e.g. `acme` from `https://acme.app.myaltimate.com`)
95
95
-**API Key** — go to **Settings > API Keys** in your Altimate dashboard and click **Copy**
96
96
97
-
If your instance uses a different API URL (e.g. a self-hosted or `getaltimate.com` deployment), prepend it:
97
+
If your instance uses a different API URL (e.g. a self-hosted or `getaltimate.com` deployment), prepend the full URL — it must include the `http://` or `https://` scheme, hostname-only values will fail validation:
98
98
99
99
```text
100
-
api-url::instance-name::api-key
100
+
https://api.example.com::instance-name::api-key
101
101
```
102
102
103
103
For example: `https://api.getaltimate.com::acme::your-api-key`
0 commit comments