Skip to main content

​
Team Collaboration Model

Raycaster Doc is built for teams. Every project member gets their own isolated staging workspace, so multiple people can work simultaneously without stepping on each other’s changes.

​
How Isolation Works

Project (main branch)
├── Alice's staging workspace  ─── (her uploads, renames, edits)
├── Bob's staging workspace    ─── (his uploads, renames, edits)
└── Carol's staging workspace  ─── (her uploads, renames, edits)
  • Each member works in their own staging area
  • Changes are invisible to others until committed
  • Commits merge into the shared main state
  • After committing, your staging workspace resets to the latest main

​
Conflict Resolution

Since each user works on an isolated branch, most conflicts are avoided entirely. When committing:
  • Source-wins strategy — your committed changes take priority
  • Name conflicts — automatically resolved with numeric suffixes (e.g., Report (1).pdf)
  • Failed commits — if something goes wrong mid-commit, the workspace enters a needs_reconcile state and you can discard to recover

​
Real-Time Updates

When a teammate commits changes, you’ll see updates reflected in real time via server-sent events (SSE). The workspace explorer and diff view update automatically — no need to refresh.

​
What Updates in Real Time

  • Workspace file tree changes
  • Diff panel updates
  • Chat messages and agent activity
  • Review run progress and action items
  • Notifications

​
Sharing & Deep Linking

Every view in Raycaster Doc is URL-driven. You can share:
  • Links to specific documents: ?file=<artifactId>
  • Links to staged views: ?workspaceId=<uuid>
  • Links to historical versions: ?commitId=<hash>
  • Links to chat sessions: ?chat=<chatId>
Recipients with project access will see exactly what you see.