Collaboration

Multiple people can work in the same Doable project simultaneously — like Google Docs or Figma.

Inviting collaborators

Three options:

1. Add to the workspace — Workspace Settings → Members → Invite. They join your workspace and see all workspace-visible projects.
2. Share a single project — Editor → Share → Invite by email. Adds them to the workspace as a Viewer (or Member, your choice) and grants project access.
3. Anyone-with-the-link — Editor → Share → Toggle. Generates a link with read or edit scope. Useful for client previews.

What you see during collaboration

• Cursor pills — each user gets a colored cursor in the code editor with their name.
• Selection highlights — see what your teammate is selecting.
• Active-now badges — the workspace dashboard shows which projects have someone in them.
• Chat is shared — every member of the chat sees streaming AI responses live. Useful for "look at this" moments.

Conflict resolution

Doable uses Yjs CRDTs for collaborative editing — every operation is conflict-free by construction. Two users typing at the same position get a deterministic, well-defined merge. No locks, no "someone else is editing" modal.

The AI counts as a third collaborator. If you and the AI both touch the same lines simultaneously, the merge is well-defined (you'll see your characters interleaved) — extremely rare in practice.

Live AI updates

When the agent edits a file, every collaborator sees the change immediately. This works because:

1. The AI writes the file via the API.
2. The API broadcasts the new content into the project's Yjs room.
3. Every connected editor receives it and updates Monaco.

So when you ask the agent to “rename Foo to Bar”, your teammates watch the rename happen across files in real time.

Presence-aware features

• The chat shows a "Sara is typing…" indicator.
• The history view shows who made which commit.
• The audit log records who triggered which AI action.

Disconnecting & reconnecting

Network drops are seamless:

• The editor switches to offline mode (a discrete pill at the top).
• You keep editing locally.
• When the connection comes back, your edits sync and the room state catches up.

Privacy considerations

If your project has visibility = public, anyone with the URL can view the live preview, but the editor is still gated by workspace membership unless you've explicitly shared the link.

Disabling collaboration

If you only ever expect single-user use of your Doable instance:

• Skip running the services/ws server.
• Set NEXT_PUBLIC_WS_URL= to empty.
• The editor falls back to single-player mode.

For multi-user instances, services/ws is required.