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 6f92853
Browse filesBrowse the repository at this point in the historyBrowse files
fix: close the late-registration gaps and tidy review findings
- Headless disclosure: `printDisclosureOnceForHeadless` now prints whenever
Base is registered and the once-per-install marker is unclaimed, not only
when this launch's own registration finished. A registration that outlasted
the startup wait finished in the background and every later launch reported
"already registered", so the notice was never shown. The marker is claimed
with an exclusive create before printing, so concurrent launches print once.
- Register route: skip the process-wide reload only when the credential is
unchanged AND Base is already in this server's provider list. After a
background auto-registration (or a credential refreshed in place) the file
is unchanged but the cached provider state predates it.
- Move `isPublicZen` out of the `Provider` namespace into
`provider/public-zen.ts` (packages/opencode/AGENTS.md "Module shape").
- Restore `altimate_base_register_result` for picker registrations during
first-run onboarding (welcome picker `origin: "welcome"`, catalogue and
provider dialog `origin: "model"`), as the removed confirm component did.
- Cap the persisted 429 auto-register backoff at 24 hours, and serialise the
backoff record's read-modify-write under its own file lock.
- Docs: registration happens on every unregistered install, whether or not
the user has a model of their own; logout keeps automatic registration off
until Base is picked again; fleet audits look for `altimate-base.json`; the
`ALTIMATE_CLI_CLIENT=datamates` skip applies to `serve`; the registration
telemetry row covers the server route.
- Tests: route reload when Base is not loaded, backoff cap, headless
disclosure after a background registration, picker result callback; the
explicit-model test restores its env even if mounting fails.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_016x3nbZU5Vb6HnSTqE7vELm
Copy file name to clipboardExpand all lines: docs/docs/getting-started/quickstart.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
@@ -25,7 +25,7 @@ On a fresh install, a welcome panel appears with a curated 6-provider picker:
25
25
26
26
-**Altimate LLM Gateway***(recommended)* — 10M tokens free, no API keys. Routes to the best model per task across Sonnet, Opus, GPT-5, and more. Sign-in opens a browser tab; complete Google or email signup and you're back in the TUI. If your terminal can't open a browser (SSH / tmux / WSL), the CLI prints the URL — paste it into a browser on your desktop.
27
27
-**Anthropic** / **OpenAI** / **Google** — paste an API key or OAuth in.
28
-
-**Altimate Base** — a hosted open model, free and rate limited, with no signup or API key. Requests and responses may be logged and used to improve Altimate's products, so do not send secrets or confidential code. If you don't pick another provider, a fresh install registers it automatically — there is no confirmation dialog — and prints this notice once. Opt out with `ALTIMATE_BASE_AUTO_REGISTER=0`, `altimate providers logout altimate-base`, or `disabled_providers` (see [providers](../configure/providers.md#altimate-base)).
28
+
-**Altimate Base** — a hosted open model, free and rate limited, with no signup or API key. Requests and responses may be logged and used to improve Altimate's products, so do not send secrets or confidential code. Every install registers it automatically at startup, whichever provider you pick — there is no confirmation dialog — and shows this notice once; it only becomes your model when nothing else you configured is usable. Opt out with `ALTIMATE_BASE_AUTO_REGISTER=0`, `altimate providers logout altimate-base`, or `disabled_providers` (see [providers](../configure/providers.md#altimate-base)).
29
29
-**Search all providers…** — full picker if you need Bedrock, Databricks AI Gateway, Cloudflare AI Gateway, Snowflake Cortex, DigitalOcean Inference, etc.
30
30
31
31
Or set an environment variable and skip the picker:
Copy file name to clipboardExpand all lines: docs/docs/reference/network.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
@@ -41,7 +41,7 @@ altimate needs outbound HTTPS access to:
41
41
| Destination | Purpose |
42
42
|-------------|---------|
43
43
| Your LLM provider API | Model inference (Anthropic, OpenAI, etc.) |
44
-
| Official Altimate Base gateway (embedded in release), or the host set by `ALTIMATE_BASE_GATEWAY_URL`| Altimate Base registration (automatic on a fresh install with no model of its own, unless `ALTIMATE_BASE_AUTO_REGISTER=0`) and inference |
44
+
| Official Altimate Base gateway (embedded in release), or the host set by `ALTIMATE_BASE_GATEWAY_URL`| Altimate Base registration (automatic at startup on any install not yet registered, unless `ALTIMATE_BASE_AUTO_REGISTER=0` or after logging out of Base) and inference |
45
45
|`registry.npmjs.org`| Package updates |
46
46
|`models.dev`| Model catalog (can be disabled) |
47
47
| Your warehouse endpoints | Database connections |
Copy file name to clipboardExpand all lines: docs/docs/reference/security-faq.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,14 @@ Answers to the most common security questions about running Altimate Code in you
13
13
14
14
Altimate Code sends prompts and context to the LLM provider you configure (Anthropic, OpenAI, Azure OpenAI, AWS Bedrock, etc.). **You choose the provider.** No data is sent anywhere else except optional [telemetry](#what-telemetry-is-collected), which contains no code, queries, or credentials.
15
15
16
-
Altimate Base is Altimate's own hosted free model. A fresh install with no model of its own
17
-
registers it automatically — there is no confirmation dialog to accept. Requests and responses are
16
+
Altimate Base is Altimate's own hosted free model. Every install that is not yet registered
17
+
registers it automatically at startup, whether or not you also have a model of your own — there is
18
+
no confirmation dialog to accept. It only becomes your default model when nothing you configured is
19
+
usable. Requests and responses are
18
20
logged and may be used to improve Altimate products and services, including the model; secrets are
19
21
automatically masked before storage, but don't rely on it — avoid sending secrets or confidential
20
22
code. This notice is printed once — a toast in the TUI, or a one-line stderr notice the first time
21
-
a headless entrypoint (`run`, `serve`, `acp`, `web`) registers it — and is part of the Altimate
23
+
a headless entrypoint (`run`, `serve`, `acp`, `web`) runs with Base registered — and is part of the Altimate
22
24
Base service, separate from anonymous product telemetry. To opt out: set
23
25
`ALTIMATE_BASE_AUTO_REGISTER=0` before Base ever registers, run `altimate providers logout
24
26
altimate-base` afterward, or exclude it from your own model choices with `enabled_providers` /
@@ -115,7 +117,7 @@ You can also configure per-agent permissions. For example, restrict the `analyst
115
117
| Destination | Purpose |
116
118
|-------------|---------|
117
119
| Your configured LLM provider | Model inference |
118
-
| Altimate Base gateway | Registration (automatic on a fresh install with no model of its own) and inference |
120
+
| Altimate Base gateway | Registration (automatic at startup on any install not yet registered) and inference |
Copy file name to clipboardExpand all lines: docs/docs/reference/telemetry.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
@@ -45,7 +45,7 @@ We collect the following categories of events:
45
45
| `first_launch` | Fired once on the first CLI run after an install or upgrade, triggered by a marker file the installer wrote — the installers themselves send nothing and contact no telemetry endpoint. Contains the installed version, `is_upgrade`, and `install_method` (`curl`, `powershell`, `npm`, `vscode-extension`, `local` for `install --binary`, or `unknown` for markers written before the field existed). `vscode-extension` starts appearing only once an extension build containing the marker write ships, so a zero share for it means the extension has not rolled out yet rather than no extension installs. No PII. **Reading `is_upgrade`:** it means "this machine had run altimate-code before", probed as whether `~/.altimate/machine-id` already existed — *not* "a binary was already present". A reinstall onto a machine that ever ran the CLI reports `is_upgrade: true`, and `altimate uninstall` leaves `machine-id` in place, so a metric excluding upgrades counts installs **per previously-unseen machine** and undercounts reinstalls onto known ones. (`is_upgrade` is a boolean in the event schema; it arrives in Application Insights `customDimensions` as a string, so KQL filters read `tostring(customDimensions.is_upgrade) != "true"`.) Delivery is at-most-once: the marker is deleted before the event flushes, so a process that dies first loses that install rather than re-firing it every launch. Local `--binary` installs report `version: "local"`. |
46
46
|`startup_ready`| Fired once per process when the top-level command can serve its first request or frame (`serve` listening, TUI transport resolved, `run` about to send its first prompt). Contains the command name, `duration_ms` since process start, and `fresh_install` (true when this process also emitted a non-upgrade `first_launch`). No PII. |
47
47
|`event_loop_stall`| A 250 ms monitor tick fired more than 1 s late, meaning the event loop was blocked for that long (for example an in-process dependency install). Contains the command name, `thread` (`main` or `worker`), `blocked_ms`, and `since_start_ms`. Capped at 20 per thread (the main thread and the TUI server worker each keep their own counter). No PII. |
48
-
|`altimate_base_registration`| Timing and outcome of each Altimate Base registration, whether triggered automatically at startup or by an explicit picker selection (concurrent calls share one result, and a still-valid cached credential reports `success` without a network round trip): `result` (`success`, `network`, `http`, `response`, `cancelled`, `configuration`, or `error`), `duration_ms`, and the HTTP `status` when the result is `http`. Distinct from `altimate_base_register_result`, which records the onboarding-flow outcome. No gateway URL, response body, credential, or error text is included. |
48
+
|`altimate_base_registration`| Timing and outcome of each Altimate Base registration, whether triggered automatically at startup, by an explicit picker selection, or through the `POST /altimate/base/register` route an IDE calls (`origin: "server"`) (concurrent calls share one result, and a still-valid cached credential reports `success` without a network round trip): `result` (`success`, `network`, `http`, `response`, `cancelled`, `configuration`, or `error`), `duration_ms`, and the HTTP `status` when the result is `http`. Distinct from `altimate_base_register_result`, which records the onboarding-flow outcome. No gateway URL, response body, credential, or error text is included. |
49
49
|`task_outcome_signal`| Behavioral quality signal at session end — accepted, error, abandoned, or cancelled. Includes tool count, step count, duration, and last tool category. No user content. |
50
50
|`task_classified`| Intent classification of the first user message using keyword matching — category (e.g. `debug_dbt`, `write_sql`, `optimize_query`), confidence score, and detected warehouse type. No user text is sent — only the classified category. |
51
51
|`tool_chain_outcome`| Aggregated tool execution sequence at session end — ordered tool names (capped at 50), error count, recovery count, final outcome, duration, and cost. No tool arguments or outputs. |
0 commit comments