@@ -5,6 +5,33 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.12.4] - 2026-09-29
+
+One fix for every TUI user, and a round of workspace-pilot work: the IDE extension can drive `/workspace` and `skill publish` over `serve`, a sync says which skills it skipped, and cached workspace state is scoped to the signed-in account. Everything under **Added** is behind `ALTIMATE_WORKSPACE=1`. **Heads-up for support (pilot):** after upgrading, each project's cached workspace link and synced skills are discarded and fetched again on first use (the cache format changed to carry the account), so the first turn in a linked project re-syncs.
+
+### Added
+
+- **`serve` exposes `/workspace` Refresh and Sync over HTTP**, so the VS Code / Cursor extension's workspace panel can run the same actions as the TUI's `/workspace` menu. The routes answer 409 outside the pilot, and refuse browser-originated requests: any request a browser marks as coming from another site (a `Sec-Fetch-Site` other than `same-origin` or `none`, so `same-site` too), any `Origin` on a server without `OPENCODE_SERVER_PASSWORD`, and any other origin when one is set. Pilot only (`ALTIMATE_WORKSPACE=1`). (#1366)
+- **`skill publish` from the IDE extension.** `serve` lists which of the project's skills can be published and publishes one to the linked or extension-pinned workspace, with the same rules and refusal wording as the CLI: built-in, personal and workspace-delivered skills are refused, and a near-miss name gets a "did you mean". Pilot only (`ALTIMATE_WORKSPACE=1`). (#1371)
+- **A workspace sync says which skills it skipped, and why.** A skill that failed to arrive used to look exactly like a workspace with no skills. The TUI shows a warning, headless `run` prints one line, and `/workspace` → Refresh lists them — at most three by name, with a plain reason ("it is too large for this client", "it could not be saved on this device"); raw errors stay in the log. The same problem is not repeated every turn. An offline check in a project that is linked, or pinned by the IDE extension, now warns instead of passing silently. Pilot only (`ALTIMATE_WORKSPACE=1`). (#1374, #1376)
+
+### Changed
+
+- **Linking asks before uploading memory you saved earlier.** When the TUI finds that a project is already linked on the server, it now asks ("Attach and continue") before backfilling the memory saved on this machine into that workspace; nothing is sent until you choose it. New memory saved in a linked project still goes to its workspace, as before — a project belongs to exactly one workspace. Pilot only (`ALTIMATE_WORKSPACE=1`). (#1373, closes #1372)
+- **`/workspace` and `link` are clearer.** The menu adds **Open in browser** and **Switch workspace**, and an unlinked project is offered **Link to a workspace**. When the project is linked to a teammate's private workspace you cannot see, `link` says so instead of reporting a race and sending you round a retry loop. Relinking drops the previous workspace's memory from the session instead of continuing to show it. A skill you wrote in the project always wins over the workspace's copy of the same name, so publishing an update to it is no longer refused. Pilot only (`ALTIMATE_WORKSPACE=1`). (#1373)
+- **Outside the pilot, `altimate-code link` and `skill publish` explain themselves.** They print "Workspaces are a pilot feature and are off. Set ALTIMATE_WORKSPACE=1 to use this command." instead of failing with "Failed to change directory to …/link", and the TUI's `--workspace` option is no longer listed in `--help`. (#1373)
+
+### Fixed
+
+- **Returning to a conversation in the TUI now keeps the model it was using.** Picking a model in one conversation could rewrite the model recorded for the conversation opened before it, so switching back selected the wrong model. Every user, not only the pilot. (#1365, closes #1364)
+- **Two Altimate accounts on one machine no longer share workspace state.** The cached project link, the resolver's short-lived caches, and the synced workspace skills were keyed on the tenant only, so after switching to another account on the same tenant, the previous account's link — and its private workspace skills — could be served for up to five minutes. All of it is now keyed on the account, a snapshot another account fetched is withheld from discovery and removed, and anything that cannot be attributed is withheld rather than served. Pilot only (`ALTIMATE_WORKSPACE=1`). (#1377, fixes #1339)
+- **Link and re-link messages no longer talk about "bindings" or "pre-checks".** Found in this release's review.
+
+### Known limitations
+
+- Skill discovery now resolves the real path of each skill file it finds (one `realpath` per skill), for every user, to tell a workspace snapshot apart from an ordinary skill; a skill whose path cannot be resolved is left out, as a broken link already was.
+- `skill publish` keeps secrets out by file name only (`.env*`, `*.pem`, `credentials.json` and similar); it does not scan contents, so a token inside `config.yaml` is uploaded. Publishing is tenant-wide.
+
 ## [0.12.3] - 2026-09-23
 
 **Heads-up before upgrading (every user):**
 
@@ -10,6 +10,21 @@
   --alt-orange: #F07030;
   --alt-orange-deep: #C5571F;
   --alt-orange-tint: rgba(240, 112, 48, 0.12);
+  /* Text that sits ON the brand orange. White gave 2.97:1 against #F07030 —
+     axe flagged the two primary CTAs, and WCAG AA wants 4.5:1 for text this
+     size. Near-black reads 6.69:1 on the same orange, so the brand colour
+     stays exactly as the brand book specifies and the label becomes legible.
+     The hover shade lifts instead of deepening, because with dark ink a
+     lighter surface raises contrast (8.24:1) where a darker one lowered it. */
+  --alt-ink-on-orange: #09090B;
+  --alt-orange-lift: #FF8547;
+  /* Brand orange used as TEXT. On the dark scheme #F07030 reads 6.9:1 against
+     the near-black page and needs no help. On the light scheme the same orange
+     sits on white or on its own 12% tint and drops to 2.4–2.8:1, so the
+     eyebrow, the active product tab and the feature chips all failed AA there.
+     The light override below deepens it to 4.9:1 on the worst of those three
+     backgrounds while staying the same hue. */
+  --alt-orange-text: var(--alt-orange);
   --alt-teal: #00CCAA;
   --alt-teal-tint: rgba(0, 204, 170, 0.12);
 
@@ -35,10 +50,16 @@
 
 /* ---- Light theme — clean, off-white-leaning -------------------------- */
 [data-md-color-scheme="default"] {
+  --alt-orange-text: #A8420C;
   --md-primary-fg-color: var(--alt-bg-light);
   --md-primary-fg-color--light: #F4F4F5;
   --md-primary-fg-color--dark: var(--alt-fg-dark);
-  --md-accent-fg-color: var(--alt-orange);
+  /* Material paints the active nav item and every link hover with the accent,
+     and body copy links with the typeset colour. On white, #F07030 gave 2.97:1
+     and #C5571F gave 4.41:1 — both under AA. The deepened orange reads 6.09:1
+     and is still the same hue. The slate block below keeps the brand orange,
+     which already reads 6.9:1 against the near-black page. */
+  --md-accent-fg-color: var(--alt-orange-text);
   --md-accent-fg-color--transparent: var(--alt-orange-tint);
   --md-default-bg-color: var(--alt-bg-light);
   --md-default-fg-color: var(--alt-fg-dark);
@@ -47,7 +68,7 @@
   --md-default-fg-color--lightest: var(--alt-border-light);
   --md-code-bg-color: #FAFAFA;
   --md-code-fg-color: #18181B;
-  --md-typeset-a-color: var(--alt-orange-deep);
+  --md-typeset-a-color: var(--alt-orange-text);
   --md-footer-bg-color: var(--alt-bg-dark);
   --md-footer-bg-color--dark: #000000;
 }
@@ -381,7 +402,7 @@ body, .md-typeset {
   font-weight: 700;
   letter-spacing: 0.14em;
   text-transform: uppercase;
-  color: var(--alt-orange);
+  color: var(--alt-orange-text);
   margin: 0 0 0.8rem;
 }
 .ak-eyebrow::before {
@@ -515,10 +536,10 @@ body, .md-typeset {
 .ak-btn svg { width: 15px; height: 15px; }
 .ak-btn-primary {
   background: var(--alt-orange);
-  color: #FFFFFF !important;
+  color: var(--alt-ink-on-orange) !important;
 }
 .ak-btn-primary:hover {
-  background: var(--alt-orange-deep);
+  background: var(--alt-orange-lift);
 }
 .ak-btn-secondary {
   background: transparent;
@@ -642,7 +663,7 @@ body, .md-typeset {
   font-weight: 500;
   letter-spacing: 0.005em;
 }
-.ak-bench-line strong { color: var(--alt-orange); font-weight: 700; }
+.ak-bench-line strong { color: var(--alt-orange-text); font-weight: 700; }
 .ak-bench-line .ak-dot {
   width: 4px;
   height: 4px;
@@ -756,7 +777,7 @@ body, .md-typeset {
 }
 .md-nav__link--active {
   font-weight: 600;
-  color: var(--alt-orange) !important;
+  color: var(--alt-orange-text) !important;
 }
 .md-nav--secondary .md-nav__link--active {
   position: relative;
@@ -791,13 +812,13 @@ body, .md-typeset {
 /* ---- Scroll-to-top FAB — solid orange, no gradient -------------- */
 .md-top {
   background: var(--alt-orange);
-  color: #FFFFFF !important;
+  color: var(--alt-ink-on-orange) !important;
   font-weight: 600;
   border-radius: 6px;
   box-shadow: 0 4px 12px rgba(240, 112, 48, 0.30);
 }
 .md-top:hover {
-  background: var(--alt-orange-deep);
+  background: var(--alt-orange-lift);
 }
 
 /* ---- Reading-progress hairline — orange, not gradient ----------- */
@@ -942,8 +963,8 @@ body, .md-typeset {
   -webkit-mask-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.85' stroke-linecap='round' stroke-linejoin='round'><path d='M20.5 11H19V7c0-1.1-.9-2-2-2h-4V3.5a2.5 2.5 0 0 0-5 0V5H4c-1.1 0-2 .9-2 2v3.8h1.5a2.5 2.5 0 0 1 0 5H2V20c0 1.1.9 2 2 2h3.8v-1.5a2.5 2.5 0 0 1 5 0V22H17c1.1 0 2-.9 2-2v-4h1.5a2.5 2.5 0 0 0 0-5z'/></svg>");
           mask-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.85' stroke-linecap='round' stroke-linejoin='round'><path d='M20.5 11H19V7c0-1.1-.9-2-2-2h-4V3.5a2.5 2.5 0 0 0-5 0V5H4c-1.1 0-2 .9-2 2v3.8h1.5a2.5 2.5 0 0 1 0 5H2V20c0 1.1.9 2 2 2h3.8v-1.5a2.5 2.5 0 0 1 5 0V22H17c1.1 0 2-.9 2-2v-4h1.5a2.5 2.5 0 0 0 0-5z'/></svg>");
 }
-/* Altimate MCP — connect / link */
-.md-tabs__link[href*="/datamates/"]::before {
+/* Workspaces — connect / link */
+.md-tabs__link[href*="/workspaces/"]::before {
   -webkit-mask-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.85' stroke-linecap='round' stroke-linejoin='round'><path d='M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71'/><path d='M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71'/></svg>");
           mask-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.85' stroke-linecap='round' stroke-linejoin='round'><path d='M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71'/><path d='M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71'/></svg>");
 }
@@ -1075,7 +1096,7 @@ body, .md-typeset {
 }
 .ak-picker-tab--active {
   background: var(--alt-orange-tint);
-  color: var(--alt-orange);
+  color: var(--alt-orange-text);
   font-weight: 600;
   border-left-color: var(--alt-orange);
 }
@@ -1128,7 +1149,7 @@ body, .md-typeset {
   border-radius: 4px;
   font-size: 0.72rem;
   font-weight: 600;
-  color: var(--alt-orange);
+  color: var(--alt-orange-text);
   background: var(--alt-orange-tint);
   letter-spacing: 0.01em;
   text-decoration: none;
@@ -1141,7 +1162,7 @@ a.ak-feature-chip::after {
 }
 a.ak-feature-chip:hover {
   background: var(--alt-orange);
-  color: #fff;
+  color: var(--alt-ink-on-orange);
 }
 a.ak-feature-chip:hover::after {
   opacity: 1;
@@ -2104,7 +2125,7 @@ a.ak-flow-chip:hover {
 }
 .ak-flow-lane--highlight a.ak-flow-chip:hover {
   background: var(--alt-orange);
-  color: #FFFFFF !important;
+  color: var(--alt-ink-on-orange) !important;
   border-color: var(--alt-orange);
 }
 
@@ -2738,3 +2759,25 @@ a.ak-stat:hover {
     justify-content: center;
   }
 }
+
+/* Collapsible admonition used on the dbt setup pages for the
+   query-comment / QUERY_TAG configuration block.
+   Header is bumped for prominence; body inherits page font size. */
+.md-typeset details.knobs-callout {
+  margin: 1.5rem 0;
+}
+.md-typeset details.knobs-callout > summary {
+  font-size: 1rem;
+  font-weight: 700;
+  padding: 0.9rem 2.6rem 0.9rem 2.6rem;
+}
+.md-typeset details.knobs-callout[open] > summary {
+  padding-bottom: 0.9rem;
+}
+.md-typeset details.knobs-callout > *:not(summary) {
+  padding-left: 1.2rem;
+  padding-right: 1.2rem;
+}
+.md-typeset details.knobs-callout > *:last-child {
+  padding-bottom: 1rem;
+}
@@ -19,8 +19,8 @@ altimate has a growing ecosystem of plugins, tools, and integrations.
 
 - **GitHub Actions**: Automated PR review and issue triage
 - **GitLab CI**: Merge request analysis
-- **VS Code / Cursor / Windsurf**: [IDE integration](../usage/ide.md) via the Datamates extension (branded **Altimate MCP** in-editor)
-- **[Altimate MCP](https://help.altimate.ai/datamates/)**: AI teammates platform with MCP integrations, Knowledge Hub, Memory, and Guardrails
+- **VS Code / Cursor / Windsurf**: [IDE integration](../usage/ide.md) via the Altimate Workspaces extension
+- **[Altimate Workspaces](https://help.altimate.ai/workspaces/)**: integrations, knowledge, memory and skills for your AI agent, in any editor or MCP client
 - **MCP**: Model Context Protocol servers
 - **ACP**: Agent Communication Protocol for editors
 
 
@@ -103,6 +103,6 @@ SDK, server API, plugins and the broader ecosystem.
 ## Other Altimate products
 
 - [Power User for dbt](https://help.altimate.ai/dbt-power-user/) — Best dbt extension for VS Code / Cursor.
-- [Altimate MCP](https://help.altimate.ai/datamates/) — A local-first MCP server for your data stack.
+- [Altimate Workspaces](https://help.altimate.ai/workspaces/) — Everything your AI agent needs, set up once, in any editor or MCP client.
 - [Altimate Lite for Snowflake](https://help.altimate.ai/snowflake-native-app/) — More out of your Snowflake compute, without your data leaving your account.
 - [Altimate Platform](https://altimate.ai/platform?utm_source=help-docs&utm_medium=referral&utm_campaign=docs-inline-link) — Enterprise cost optimization for [Snowflake](https://altimate.ai/use-cases/altimate-for-snowflake?utm_source=help-docs&utm_medium=referral&utm_campaign=docs-inline-link) and [Databricks](https://altimate.ai/use-cases/altimate-for-databricks?utm_source=help-docs&utm_medium=referral&utm_campaign=docs-inline-link).
@@ -99,6 +99,7 @@ Configuration can be controlled via environment variables:
 | `ALTIMATE_CLI_DISABLE_PRUNE`           | Disable database pruning             |
 | `ALTIMATE_CLI_DISABLE_MODELS_FETCH`    | Don't fetch models from models.dev   |
 | `ALTIMATE_DISABLE_WORKSPACE`           | Set to `1` to turn off every workspace feature (linking, skill and memory sync, the workspace engine). Workspaces are on by default |
+| `ALTIMATE_WORKSPACE_WEB_URL`           | Development only: the base URL of a local web app's Workspaces pages, used instead of the tenant's for `link`'s browser hand-off and workspace links. Include the mount path, e.g. `http://acme.localhost:3000/workspaces` |
 | `ALTIMATE_INTEGRATIONS`                | Set to `local` to keep warehouse tools local rather than routing them through a bound workspace's engine |
 | `ALTIMATE_CODE_SERVE`                  | Set to `1` by `altimate-code serve` itself, whether the IDE extension or you launched it. Marks that process as the extension's host — so it is the one that reads the pin variables — and is stripped from every child the bash and shell tools start |
 | `ALTIMATE_PINNED_WORKSPACE_ID` / `_NAME` / `_ROOT` | Set together by the IDE extension on `serve`: the workspace selected in its panel and the folder it applies to. All three or none — a partial pin is refused rather than ignored. Read only when `ALTIMATE_CODE_SERVE` is set; never persisted; stripped from child processes |
 
@@ -1,11 +1,11 @@
 ---
 title: "IDE Integration — Altimate Code in VS Code"
-description: "Use Altimate Code inside VS Code via the Datamates extension. Requires the altimate-code CLI to be installed."
+description: "Use Altimate Code inside VS Code via the Altimate Workspaces extension. Requires the altimate-code CLI to be installed."
 ---
 
 # IDE Integration
 
-altimate-code integrates with your IDE via the [Datamates extension](https://marketplace.visualstudio.com/items?itemName=altimateai.vscode-altimate-mcp-server) — listed as **Datamates** in the Marketplace, its in-editor commands and docs are branded **Altimate MCP** — giving you AI-powered chat with 100+ data engineering tools directly in your editor.
+altimate-code integrates with your IDE via the [Altimate Workspaces extension](https://marketplace.visualstudio.com/items?itemName=altimateai.vscode-altimate-mcp-server) — listed as **Altimate Workspaces** in the Marketplace (it was called Datamates before version 0.10.0) — giving you AI-powered chat with 100+ data engineering tools directly in your editor.
 
 ---
 
@@ -17,23 +17,23 @@ Install the altimate-code CLI globally:
 npm install -g altimate-code
 ```
 
-The Datamates extension requires this to be installed for the chat and tools to function.
+The Altimate Workspaces extension requires this to be installed for the chat and tools to function.
 
 ## Install the Extension
 
-Install the Datamates extension for your IDE:
+Install the Altimate Workspaces extension for your IDE:
 
 - **VS Code** — [Microsoft Marketplace](https://marketplace.visualstudio.com/items?itemName=altimateai.vscode-altimate-mcp-server)
 - **Cursor / other VS Code-compatible editors** — [Open VSX Registry](https://open-vsx.org/extension/altimateai/vscode-altimate-mcp-server)
-- **Windsurf** — Install via the built-in extension marketplace (search "Datamates")
+- **Windsurf** — Install via the built-in extension marketplace (search "Altimate Workspaces")
 
 ## Open Altimate Code Chat
 
 After installing the extension:
 
 1. Press `Cmd+Shift+P` (macOS) or `Ctrl+Shift+P` (Windows/Linux) to open the command palette
-2. Type `Altimate MCP`
-3. Select **Altimate MCP: Open Altimate Code Chat**
+2. Type `Altimate Workspaces`
+3. Select **Altimate Workspaces: Open Altimate Code Chat**
 
 This opens the Altimate Code chat panel where you can interact with altimate agents and use all 100+ data engineering tools.
 
@@ -66,8 +66,8 @@ The extension installs the CLI natively: the release archive is fetched over HTT
 You need an LLM to power the chat. Two options:
 
 - **BYOK (Bring Your Own Key)** — Free and unlimited. Configure any of the [35+ supported providers](../configure/providers.md) (Anthropic, OpenAI, AWS Bedrock, Azure OpenAI, etc.)
-- **[Altimate LLM Gateway](https://help.altimate.ai/datamates/user-guide/components/llm-gateway/)** — Managed LLM access with dynamic model routing. 10M tokens free to get started — no API keys to manage
+- **[Altimate LLM Gateway](https://help.altimate.ai/workspaces/user-guide/components/llm-gateway/)** — Managed LLM access with dynamic model routing. 10M tokens free to get started — no API keys to manage
 
-## Full Altimate MCP Documentation
+## Full Altimate Workspaces documentation
 
-The Datamates extension offers additional capabilities beyond Altimate Code Chat, including MCP server integrations, Knowledge Hub, Memory Hub, and Guardrails. See the [Altimate MCP documentation](https://help.altimate.ai/datamates/) for full setup guides, integration configuration, and feature details.
+The Altimate Workspaces extension offers more than Altimate Code Chat: integrations, knowledge, memory and skills from your workspace. See the [Workspaces documentation](https://help.altimate.ai/workspaces/) for full setup guides, integration configuration, and feature details.