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
workspace: the model cannot say which Altimate Workspace a project is linked to unless it is routing, and conflates it with other services' "workspace" #1331
"Workspace" means two unrelated things in the product — the Altimate Workspace a project is linked to, and other services' own "workspace" (a Databricks workspace, an IDE workspace folder). Nothing tells the model which one an unqualified "workspace" means, so it can answer a Databricks question about the Altimate link, or vice versa, confidently. Two of our own strings used the word for something else: the Databricks auth prompt (<workspace-host>) and the nothing-built validator ("the workspace is configured to require artifacts").
Expected
A short identity section in the system prompt on every step, independent of routing, with a definite answer per state: linked to X (id N) / none linked (and how to link) / could not be verified this turn (assert nothing).
The active instruction scoped to a genuine identity question ("this/current/active workspace", or an unqualified "workspace" asking what this project is connected to) — never to any mention of the word, so unrelated Databricks conversations get no linking pitch.
One owner for identity: the routing directive describes which workspace serves the tools, never the current link.
Our own strings qualify the word when they mean something other than the Altimate Workspace.
Notes
Pilot-gated (ALTIMATE_WORKSPACE=1) like the rest of the workspace feature. Verified end to end against freemium from the PR branch (unlinked, linked, "current workspace", Databricks questions in both states).
Problem
Two related gaps in how the model understands "workspace":
"Which workspace is this project linked to?" has an answer only when the workspace is routing something. feat(workspace): identity in the prompt, and a /workspace menu for refresh, sync and unlink #1278 (closing workspace: identity is dropped from the system prompt when the workspace serves no integrations #1269) put the binding into the routing directive in
awareness.ts, which is silent by design whenever there is nothing to steer. So an unlinked project, a link that cannot be verified this turn, and a freshly created workspace with no integrations all render nothing — and the model answers from whatever "workspace" is nearby in context, or guesses."Workspace" means two unrelated things in the product — the Altimate Workspace a project is linked to, and other services' own "workspace" (a Databricks workspace, an IDE workspace folder). Nothing tells the model which one an unqualified "workspace" means, so it can answer a Databricks question about the Altimate link, or vice versa, confidently. Two of our own strings used the word for something else: the Databricks auth prompt (
<workspace-host>) and the nothing-built validator ("the workspace is configured to require artifacts").Expected
Notes
Pilot-gated (
ALTIMATE_WORKSPACE=1) like the rest of the workspace feature. Verified end to end against freemium from the PR branch (unlinked, linked, "current workspace", Databricks questions in both states).🤖 Generated with Claude Code
https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6