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
altimate_memory_write says workspace memory is shared with the team, but it is per-user #1404
altimate_memory_write tells the agent that, in a workspace-linked project, memory is shared with the team. It isn't: workspace memory is mirrored per user.
When the project is linked to an Altimate Workspace with workspace sync on and workspace memory enabled this is the TEAM's memory: blocks sync to the workspace and to every linked checkout, so a decision saved here is what teammates' sessions read.
Actual behaviour (packages/opencode/src/altimate/workspace/memory-api.ts):
Every mirrored record is written with visibility: "private" ("Always "private" in v0 … nothing reads it today", line 50).
MemoryApi.list() reads "this user's mirrored records" (line 154), so a teammate's sessions never load another user's blocks.
Impact: the agent saves team decisions and conventions to memory expecting teammates to get them, and may tell the user so. Teammates never see them. Memory does follow the same user across their own linked checkouts.
Fix: reword the description to say workspace memory follows the user across their linked checkouts and is not shared with teammates (yet), and point team-wide conventions to a published workspace skill. Revisit when memory gains team visibility.
Activity
SudSampath commentedon Oct 20, 2026
If it's alright- I am taking a look at this now.
fix: reword the workspace memory sync line and test both surfaces
fix: say the starter's workspace memory is per-user