BobSwap, for humans

Your workspace travels as one file

A BOB tab is an agent workspace that lives in your browser. Its conversations, scripts and files can be packed into one workspace archive. BobSwap moves that archive; it does not run the agent or display its conversations.

There are two different ways to move it. A seed is saved for later. A relay is a live handoff. Choose based on whether the receiving tab is available right now.

Seeds: a shelf for saved workspaces

A seed stores an archive privately under an account, a name and a version. For example: personal / research / v1. An agent with the right access key can download it later, even when the original tab is closed.

• Versions do not silently overwrite one another. Different contents need a new version.
• latest means the version most recently uploaded, not the newest date inside the archive.
• Deleting the latest version makes the previous upload become latest again.
• Downloading does not automatically import the archive into a BOB tab. The receiving client handles that locally.

Relay: a handoff while both tabs are open

The relay service pairs two tabs and forwards transient messages. It never saves their workspace contents. Both tabs need to stay open and connected during the transfer.

1. The sending tab opens a fresh share and displays a channel ID and a six-digit pairing code.
2. The receiving tab uses that channel ID and types the code. The default pairing window is 15 minutes; use the expiry shown by the sender.
3. Both tabs display the same four-character visual check. Compare it before proceeding. If the checks differ, cancel and start a new share.
4. The receiver assembles the archive in memory and checks its fingerprint before importing it. Completion or cancellation removes the pairing record.

Five wrong codes destroy the share. Each share accepts only one receiver. An expired, cancelled or completed share cannot be reused—start a fresh one.

This is the intended tab experience. Pairing is built; the sender/receiver pages and the final ownership-swap checks are still coming.

Copy keeps ownership. Swap transfers it.

Copy sends a workspace without changing which device is its owner.

Swap is an ownership handoff. After a successful transfer, the receiving tab asks for ownership, and a person must explicitly accept on the sending device. The devices verify a signed approval and keep their own receipts. BobSwap does not keep an ownership ledger.

A swap does not mean your previous copy has been erased. The previous owner's tab should stop presenting itself as the owner after the handoff. The signed confirmation and receipt flow still needs the upcoming two-tab test pages.

Access keys are not your dashboard login

The operator's email and password are for the private dashboard only. Agents upload and download using keys beginning with bsk_live_, never the email login. There is no public signup.

• Read: retrieve seeds and start a live share.
• Upload: read and add new seed versions.
• Manage: upload, delete and create signed download links.

A key belongs to one account. Keep it private. A download URL containing a key lets anyone holding it read seeds in that account, so prefer a signed link when sharing a single version.

A signed link works without an account key and defaults to 24 hours. Anyone holding the link can download its archive until it expires or that archive is deleted. Revoking the key used to create it does not revoke the link. Avoid links with no expiry unless you deliberately want ongoing access.

The dashboard's key creation and revocation controls are not built yet. An API client needs an already-issued key from the operator; these documentation pages do not create one.

What stays, and what does not

Saved seeds remain stored until deleted. They are private and accessed through keys or signed links.

Relayed workspace content is never stored by BobSwap. Temporary pairing details—device names, public keys, size and progress—exist only while the channel is active or awaiting expiry cleanup. Finished channels are deleted, not archived in a relay history.

“Zero storage” is not a promise of end-to-end encryption. The service forwards live messages; the visual check confirms pairing, not secrecy from the relay. Share only with a device you trust.

If a transfer fails, do not import partial or unverified files. The client must clear its temporary buffers and cancel the share. Automatic closed-tab detection is not yet verified in the upcoming test pages.

Available today

• Built: seed upload/download, version lists, metadata, unchanged-file checks, signed links and relay pairing/control.
• Tested: seed flows and a roughly 5 MB relay between simulated clients.
• Still coming: operator sign-in/dashboard, key controls, live relay monitor, and browser sender/receiver test pages.
• Not yet verified: near-200-MiB archives, automatic disconnect cleanup in the browser, and the complete signed ownership swap.

For connecting a BOB client, the agent reference has request examples and the precise transfer rules.