fix: clarify workspace memory is per-user

SU
19h ago
+49-24

Issue for this PR

Closes #1404

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

  • Problem: The prompts told the agent that saved workspace memories were shared with teammates.
  • Actual behavior: Mirrored records are private, and reads return the current user’s records.
  • Fix: Update the tool description and two workspace prompt surfaces to describe per-user syncing consistently. Point team-wide conventions toward published workspace skills.

If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!

How did you verify your code works?

  • From packages/opencode: bun test test/altimate/workspace/ test/memory — 1,552 passed, zero failures.
  • From the root: bun turbo typecheck — 13 tasks passed using cache.
  • Oxlint on the five changed files — zero errors; all 64 warnings are on unchanged (pre-existing) code

Cost side effects

None- prompt text was a small fixed length increase

Screenshots / recordings

None- this is a prompt change

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR
  • I checked for cost side effects (model calls, queries or cloud resources that grow with user data) and described them, or wrote "none"

If you do not follow this template your PR will be automatically rejected.

Summary by cubic

Fixes the workspace memory prompts so the agent no longer claims saved memories are shared with teammates. Mirrored records are private and reads return only the current user's records, so the memory-write tool description and all workspace prompt surfaces (identity, contents, and post-link starter) now describe per-user syncing consistently, point team-wide conventions to published workspace skills, and include regression tests for each surface.

Summary by CodeRabbit

Documentation

  • Clarified that workspace memory synchronizes only for the current user across linked checkouts.
  • Clarified that teammates cannot access user-specific workspace memory.
  • Directed team-wide conventions to published workspace skills.
  • Confirmed continued use of workspace memory tools rather than the separate data store.

Tests

  • Updated coverage for per-user behavior across enabled, disabled, and unbound scenarios.
  • Added checks for teammate isolation and workspace skill publishing guidance.