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 960b936
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(workspace): relink memory, consent before seeding, pin skills, clearer link and /workspace (AltimateAI#1373)
* fix(workspace): dogfood fixes for relink, consent, pin skills and link messages
Relink resets session memory; discovered links seed only on Attach; an
unresolvable IDE pin retires another workspace's skills; link reports the
memory seed outcome and explains a teammate's private workspace; clearer
/workspace menu, pilot-off stubs and prompt copy. FixesAltimateAI#1372.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): address review on the dogfood fixes
Mark sessions stale on a binding change instead of dropping in-flight loads;
fail closed on any unresolvable pin in scope; report a failed memory lookup as
incomplete, not off; seed on Attach from the cached dialog; tighten the hidden
workspace conflict check; qualify routing copy for local integrations.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): address second review round
Hide a superseded memory overlay at once (epoch taken after binding resolution),
so a relink, unlink or reset during a load or refresh cannot republish the old
workspace; seed an offline Attach only after the server confirms the link;
report the local memory opt-out distinctly; pin-aware no-account copy; latch
the /workspace menu while the picker opens.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): clear the adopted flag when Attach approves a cached binding
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): scope memory epochs per project and bracket the binding lookup
A relink landing mid-lookup can no longer stamp the old binding current, and
linking another project no longer hides this one's memory. Offline Attach warns
when it cannot confirm the link; pin advice only for a pin governing the folder;
name both memory opt-out variables.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): stamp failed memory loads; use the hidden-conflict check in the TUI
A failed load no longer reloads on every turn; TUI conflict toasts use the
same hidden-workspace predicate as the CLI; the already-seeded message no
longer claims all memory is synced.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): pin the account across offline Attach; keep a failed load's epoch
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): pin offline Attach to the account the dialog was shown under
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): pin the account inside recordApprovedBinding; harden the relink test
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): revalidate online Attach; Open follows the IDE pin; signal-based race tests
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): capture the account before the pre-check; Open fails closed on a bad pin
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): pin the account when warming a discovered binding
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): skip the discovery warm-up when no account is known
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): keep a failed pin check unresolved for Open in browser
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): report the seed gate from the sweep itself; Open for an unlinked pinned project
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): report an unavailable memory setting in Sync; pin the stale-memo test
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): surface an account-changed Attach; do not overstate unsent memory on gate errors
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): pin the account in link; bound the menu pin check; no Switch under a pin
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(workspace): refuse link without readable credentials; no Unlink under a pin
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* test(workspace): cover /workspace menu rows and hidden-binding conflict toast
Plugin-level tests for two TUI surfaces that shipped on this branch untested:
- runWorkspaceManage: when linked and not pinned, the menu offers Refresh,
Sync, Switch workspace, Unlink and Done; when unlinked it offers "Link to a
workspace" rather than a dead end. Open-in-browser is asserted conditionally
(it depends on a resolvable web URL).
- bindOrRebindInline: a 409 that withholds the existing workspace name renders
the "workspace you can't see" guidance, not the false "claimed while you were
choosing" race message.
Both fail when their fix is reverted (mutation-checked). bindOrRebindInline and
runWorkspaceManage are exported for the tests; no behaviour change.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
Co-authored-by: Haider <[email protected]>
Copy file name to clipboardExpand all lines: docs/docs/usage/cli.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
@@ -51,10 +51,10 @@ altimate --agent analyst
51
51
Workspace features are off unless `ALTIMATE_WORKSPACE=1` is set. With it:
52
52
53
53
-`altimate-code link` links the current project to a workspace (or creates one). The sidebar then names the workspace and shows how many memories are not yet synced and when skills last synced.
54
-
-`/workspace` in the TUI opens a menu: **Refresh** pulls the workspace's skills and memory into this project, **Sync** re-sends local memory the workspace never received, **Unlink** detaches the project.
54
+
-`/workspace` in the TUI opens a menu: **Refresh** pulls the workspace's skills and memory into this project, **Sync** re-sends local memory the workspace never received, **Open in browser** (when a web URL is available) shows the workspace on the web, **Switch workspace** relinks the project, **Unlink** detaches it. In a project that is not linked yet, it offers **Link to a workspace** instead.
55
55
-`altimate-code skill publish <name>` uploads a project skill to the linked workspace; see [Skills](../configure/skills.md#cli-commands).
56
56
- In an ordinary session the agent is told every turn which workspace the project is linked to — or that none is, or that the link could not be verified just now. In an extension-pinned session it is told the pinned workspace instead, and that it differs from the project's own link. Either way "which workspace am I in?" has an answer, and the agent is told not to confuse it with a Databricks workspace or an IDE workspace folder.
57
-
- When `altimate-code serve` is launched by the VS Code / Cursor extension, the workspace selected in the extension's panel governs that session's skillsand memory, taking priority over whatever the project is linked to on the backend, and is scoped to the folder it was launched for. Warehouse tool routing still follows the project's own link for now. A pin is fixed for the life of the `serve` process, so the extension relaunches `serve` when the selection changes; nothing updates a running one.
57
+
- When `altimate-code serve` is launched by the VS Code / Cursor extension, the workspace selected in the extension's panel governs that session's skills, memory and (unless `--integrations local` is set) warehouse tool routing, taking priority over whatever the project is linked to on the backend, and is scoped to the folder it was launched for. A pin is fixed for the life of the `serve` process, so the extension relaunches `serve` when the selection changes; nothing updates a running one.
0 commit comments