For teams

Working with a team

What changes when the context stops being only yours.

A workspace lives in one of two kinds of place, and a machine can hold both at once:

  • This Mac - everything in ~/Recall/ on your laptop. Single-user. No network. Nothing to run.
  • A box - a Postgres backend you (or someone in your team) runs. Multiple people can share workspaces, claim tasks, and see each other's activity live. You can have several boxes: your own and the team's, side by side.

There is no mode to switch. The tree shows each home as a top-level node with its workspaces under it, and where a workspace lives is decided once, when it is created. Joining a box does not touch your ~/Recall/; it adds a node beside it. See "Where each workspace lives".

When to use which

On this Mac

  • Solo work.
  • Offline or airplane sessions.
  • Experimenting with something you don't want visible to teammates yet.

On a box

  • Collaborating with at least one other person.
  • You want your context available on more than one machine (laptop + desktop).
  • You're OK running the backend (or pointing at one somebody runs).

The two-person quick start

See "Host it yourself" and "Inviting teammates" in this section for the full walkthrough. The 30-second version:

  1. One person runs the backend via docker compose up in backend/.
  2. That person registers it as their own from their Mac with rememd add-instance --server <url> --token-stdin - or in Settings, Add an instance you run - using the admin token from the box's backend/.env. No invite needed for the owner.
  3. They right-click the row they want to grant - workspace, product, focus area or feature - and choose Invite, then send the URL to the teammate.
  4. The teammate runs rememd join <invite-url> and that's it.

What's synced and what's not

Shared (same view for everyone on the team):

  • The hierarchy: workspaces, products, focus areas, features.
  • Tasks with their status, assignee, dependencies.
  • PRDs, session logs, notes, session-event timelines.

Per-user (never leaves your machine):

  • Where you've cloned each repo on disk. Lives in ~/.recall/repo-map.json, keyed by the shared UUIDs of focus areas / features. Dev B's path is theirs; yours is yours. Neither shows up in the other's rememd.

This means dev B doesn't need any shared setup beyond git clone-ing the repos wherever they want on disk. Rememd doesn't care.