Working with a team

rememd has two modes:

• Local (default) - everything lives in ~/Recall/ on your laptop. Single-user. No network. Nothing to run.
• Remote - data lives in a Postgres backend you (or someone in your team) runs via Docker. Multiple people can share workspaces, claim tasks, and see each other's activity live.

You can switch between modes at any time. Joining a remote backend does not delete your local ~/Recall/; it just changes where rememd reads/writes while in remote mode.

When to use which

Local

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

Remote

• Collaborating with at least one other person.
• You want your context available on more than one machine (laptop + desktop).
• You're OK running Docker (or pointing at a shared host).

The two-person quick start

See "Setting up remote mode" and "Inviting a teammate" 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 runs rememd join <invite-url> and becomes the admin.
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.