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 a2b9c44
Browse filesBrowse the repository at this point in the historyBrowse files
docs: check the CLI version before linking a project to a workspace
The Claude Code guide gave the Node.js minimum but not the CLI one, so
someone with an older install went straight to `altimate-code link` and
got "Workspaces are a pilot feature and are off" (0.12.4) or no `link`
command at all (older).
- install step: run the install again to upgrade; linking needs 0.12.5+
- workspace section: a "Check your version" step before sign-in, with
`altimate-code --version`, and `which -a` / `where` for an older copy
that runs first
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_011chv9Rmu7jQXokum1WNcs7
1. Install Altimate Code (Node.js 20 or later): `npm install -g altimate-code`. Already installed? Run it again to upgrade; linking a project to a workspace needs 0.12.5 or later (see [Use an Altimate workspace from Claude Code](#use-an-altimate-workspace-from-claude-code)).
86
86
2. Install the plugin from Anthropic's plugin directory:
87
87
88
88
```bash
@@ -116,25 +116,33 @@ This creates `~/.claude/commands/altimate.md`. You can now use `/altimate` in an
116
116
117
117
Claude Code reaches a workspace through Altimate Code: every task the plugin hands over runs in your project, so it gets the workspace the project is linked to — its skills, its knowledge, your team's shared memory and its integrations. Nothing in Claude Code itself needs configuring.
118
118
119
-
1. **Sign in to Altimate.** In a terminal:
119
+
1. **Check your version.** Linking needs Altimate Code 0.12.5 or later; older versions have no `link` command, or say "Workspaces are a pilot feature and are off".
120
+
121
+
```bash
122
+
altimate-code --version
123
+
```
124
+
125
+
If it is older, run `npm install -g altimate-code` again. If `--version` still shows the old version after that, another copy runs first: `which -a altimate-code` (`where altimate-code` on Windows) lists every copy on your `PATH`, so remove the old one.
It opens your browser; sign in and return to the terminal. (Inside the TUI, `/connect` does the same.) The command also works from Claude Code: type it after `!`in the prompt.
126
134
127
-
2. **Link the project.** In the project folder:
135
+
3. **Link the project.** In the project folder:
128
136
129
137
```bash
130
138
altimate-code link
131
139
```
132
140
133
141
Pick the workspace, or create one. The picker needs an interactive terminal, so it does not run from Claude Code's `!` prompt or a script. There, list the workspaces with `altimate-code workspace list` and link with `altimate-code link --workspace <id or name>`, or create one with `altimate-code link --create`. Moving a linked project to a different workspace also needs `--yes`. Claude can run these for you: ask it to link the project to a workspace.
134
142
135
-
3. **Check it.** `altimate-code workspace status` shows the linked workspace and when its skills last synced.
143
+
4. **Check it.** `altimate-code workspace status` shows the linked workspace and when its skills last synced.
136
144
137
-
4. **Ask Claude.** Questions about your team's conventions, best practices or knowledge are answered from the workspace when they reach Altimate Code. Start them with `/altimate-code:altimate` to be sure they do:
145
+
5. **Ask Claude.** Questions about your team's conventions, best practices or knowledge are answered from the workspace when they reach Altimate Code. Start them with `/altimate-code:altimate` to be sure they do:
138
146
139
147
```
140
148
/altimate-code:altimate what are our naming conventions for staging models?
0 commit comments