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 cfa587f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(workspace): explain a link to a teammate's private workspace; warn that quick workspaces are private
- A 409 whose `existing_datamate_name` is withheld means the project is linked
to a workspace the caller cannot see. `link` (three paths) and the TUI (three
toasts) said "another workspace claimed this project while you were choosing"
/ "another workspace", sending users round a retry loop. They now say it is
most likely a teammate's private workspace and to ask its owner to share it.
- `link`'s quick create warns that only the creator can see the new workspace,
so teammates who clone the repo are told it is unlinked until it is shared.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
`This project is already linked to "${existingName}". Workspace "${projectName}" was created but is not linked — re-run \`altimate-code link\` and pick a different action to switch, or delete the new workspace in the SaaS.`,
@@ -536,6 +540,8 @@ export async function createThenBindOrRebind(
536
540
`The workspace could not be created: ${err.message}. Nothing was created, and this `+
537
541
`project is still linked to "${stripControlChars(existing.datamate.name)}".`,
538
542
)
543
+
}elseif(isHiddenBindingConflict(err)){
544
+
prompts.log.error(`${HIDDEN_BINDING_MESSAGE} Nothing was created.`)
0 commit comments