[vinayagg]

What broke
Opening a remote thread downloaded its files and execution state, while moving the thread left its MCP setup behind. A user also had to operate the source machine to initiate a transfer.

Why
Reads used full peer snapshots, and integrations and credentials lived outside transfer checkpoints.

What changed

• Show directory labels and read-only conversation text without downloading files, run state, or MCP settings.
• Add Transfer here: same-account requests proceed automatically when the source is idle; another editor's request requires the owner's approval.
• Carry effective cloud app selections and custom MCP settings and credentials only in explicit same-user transfers over the encrypted peer channel. Stage credentials privately and keep them out of thread documents and Server storage.
• Keep transferred integrations scoped to that thread. Require setup and explicit enabling for local commands and loopback services on the destination.
• Preserve local offline reads and the existing source-initiated offer/accept flow.

Tested
npm run check in desktop and server. Coverage includes conversation-only reads, direct TLS and relay transfers, same-user MCP credential transfer, teammate approval, revocation, integrity checks, and local-tool activation. Desktop and hosted UI builds are included.

Not touched
Personal browser sessions and AI provider settings stay local. Transfers to another account do not carry the source user's app authorizations or MCP credentials. Live provider accounts were not tested.

Companion Server PR: https://github.com/Bees-bot/bees-server/pull/69. Requires migration 037 and the updated Server for destination-initiated transfers.