Team workspace

Privacy Boundaries for Synced Agent Sessions

A design checklist for authentication, user isolation, explicit sharing, and controlled resume actions.

6 min readByk engineering

Discovery is already access

Titles, machine names, repositories, and activity can reveal sensitive work before anyone opens a conversation.

A native macOS dock for every Claude Code session across your team — watch them tile, jump in, and continue any conversation, synced across machines.

Define the sharing unit

A session record needs an owner, permitted viewers, permitted operators, source machine, and synchronization version so access can be enforced.

  • Watch Claude Code sessions as live tiles
  • Jump in and resume a conversation
  • Sync across LAN or cloud

Bound insecure modes

Until authentication and per-user isolation exist, product copy and runtime state must keep LAN and cloud sync explicitly limited to trusted environments.

Current product status: LAN sync has no auth · cloud sync has no per-user privacy.

  • Every Claude Code session as a live tile
  • Jump in and resume any conversation
  • LAN and cloud sync across machines

Continue reading