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 ba98c93
Browse filesBrowse the repository at this point in the historyBrowse files
Brings in the workspace sync state (#1429), which records what each memory
load served, keyed by cloud record id.
Resolved in `loadWorkspaceMemory`: the load still serves the newest record
per copy key, and the sync-state items are those served records, after the
expiry check. Two live records of one block are one item, keyed by the
record served.
Test: main's "two teammates' blocks with the same block id are two items"
listed two global records with one block id. The listing holds only the
caller's own records, so that pair is two copies of one block, which this
branch serves once. The test now lists two projects' blocks with one block
id (still two items), and a new test covers two copies of one block (one
item, unchanged once the older copy is archived).
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01LmLXkY5NUqPL7nH2exe9zb
Copy file name to clipboardExpand all lines: .opencode/skills/altimate-setup/SKILL.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
@@ -1,6 +1,6 @@
1
1
---
2
2
name: altimate-setup
3
-
description: Configure Altimate platform credentials for datamate and API access
3
+
description: Configure Altimate platform credentials for API and workspace access
4
4
---
5
5
6
6
# Altimate Setup
@@ -28,4 +28,4 @@ Guide the user through configuring their Altimate platform credentials.
28
28
```
29
29
Then set permissions to owner-only: `chmod 600 ~/.altimate/altimate.json`
30
30
31
-
4.**Validate**: Call the `datamate_manager` tool with `operation: "list"` to verify the credentials work. Report success or failure to the user.
31
+
4.**Validate**: If the `datamate_manager` tool is available, call it with `operation: "list"` to verify the credentials work, and report success or failure to the user. If it is not (it is turned off in a project linked to an Altimate workspace), ask the user to run `/workspace` → Refresh instead, which calls the Altimate API with these credentials and reports an error if they don't work.
log.warn("could not delete a datamate created as the project was linked",{id: created.id,err: String(err)})
544
+
returnfalse
545
+
},
546
+
)
547
+
if(rolledBack)returnadded
548
+
return{
549
+
...added,
550
+
output: `${added.output}\n\nOne exception: the datamate '${args.name}' (ID: ${created.id}) had already been created in your Altimate account and could not be deleted again; delete it there if it is not wanted.`,
0 commit comments