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 3a88c4d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(workspace): outage is not "not linked", sanitize names, idempotent link --create, handler tests (review)
Consensus review fixes: status/refresh/sync/unlink resolve the link first (service unreachable exits 1, a confirmed unlink exits 3); sync refuses an adopted link; names stripped of control characters; unlink that leaves skills behind exits 1; `--json` ok matches exit 0; `link --create` is a no-op when already linked to that name and refuses an existing namesake unless `--allow-duplicate`; headless create does not open a browser; `workspace` recorded in telemetry; handler-level tests.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV
Copy file name to clipboardExpand all lines: docs/docs/usage/cli.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,9 +53,10 @@ Workspace features are off unless `ALTIMATE_WORKSPACE=1` is set. With it:
53
53
54
54
-`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.
55
55
- From a shell, script or CI job, without the TUI:
56
-
-`altimate-code link --workspace <name|id>` links to an existing workspace, and `altimate-code link --create [name]` creates one (named after the repo by default) and links to it. Neither prompts. If the project is already linked to a different workspace they refuse unless `--yes` is passed.
56
+
-`altimate-code link --workspace <name|id>` links to an existing workspace (an id is matched before a name), and `altimate-code link --create [name]` creates one (named after the repo by default) and links to it. Neither prompts. If the project is already linked to a different workspace they refuse unless `--yes` is passed. Running `--create` again when the project is already linked to a workspace of that name changes nothing, so it is safe in a devcontainer's setup command; if another workspace already has that name it refuses and names its id, unless `--allow-duplicate` is passed.
57
57
-`altimate-code workspace status [--json]` shows the linked workspace, how many saved memories have not reached it, and when skills last synced.
58
-
-`altimate-code workspace refresh` pulls the workspace's skills and memory; `altimate-code workspace sync` sends memory the workspace has not received; `altimate-code workspace unlink [--yes]` detaches the project (`--yes` is required without a terminal).
58
+
-`altimate-code workspace refresh` pulls the workspace's skills (memory is loaded by the next session started in the project); `altimate-code workspace sync` sends memory the workspace has not received; `altimate-code workspace unlink [--yes]` detaches the project (`--yes` is required without a terminal).
59
+
- Exit codes: `0` done, `1` failed (including when the workspace service could not be reached), `2` needs a different request (not signed in, or `--yes` missing), `3` the project is not linked. With `--json`, `ok` is `true` exactly when the exit code is `0`.
59
60
- These commands accept `--directory` and exit `0` on success, `1` on failure, `2` for a request to change (not signed in, or a re-link or unlink without `--yes`), and `3` when the project is not linked.
60
61
-`/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.
61
62
-`altimate-code skill publish <name>` uploads a project skill to the linked workspace; see [Skills](../configure/skills.md#cli-commands).
`Could not check which workspace this project is linked to, so nothing was changed: ${errinstanceofError ? err.message : String(err)}`,
1029
+
deps.printError(
1030
+
`Could not check which workspace this project is linked to, so nothing was changed: ${stripControlChars(errinstanceofError ? err.message : String(err))}`,
0 commit comments