Connect devices and manage your account
Choose when to sign in, understand remote connections, and distinguish signing out from deleting data.
Local terminal work does not require a Push account. Sign in when you want your devices to discover workspaces, collaborate, or use account-based remote features.
What signing in adds
Use Settings → Account on the Mac with Apple, Google or GitHub. Connect the same account on your devices, or accept an offered role under your own account for a shared workspace.
Linked sign-in providers belong to one account when you connect them through Connected Accounts. Do not assume two independently created provider accounts are already the same identity.
Your account supports identity, workspace discovery and access. Work, recordings and agent conversations live on the host Mac rather than in the account directory. A later sign-in change does not itself transfer ownership of an established workspace.
Slack is a separate identity connection. Linking Slack identifies who requested work; folder and action permissions still come from the assigned role. See team setup.
The relay
The relay connects devices that cannot reach the host Mac directly. It carries requests and responses; it does not run your coding agent or provide a workspace backup.
Current paired iPhone and browser clients support end-to-end encrypted channels when the host has the required encryption capability. The relay can still observe connection metadata, sizes and timing. A failed encrypted channel does not silently retry as plaintext. Older connections can terminate transport encryption at relay infrastructure; keep the host and clients current for the current pairing behavior.
Remote access can include work text, live terminal output and requested files. Device admission, workspace roles and Data Access determine what a particular client can do. Review connected devices on the Mac and revoke access you no longer want.
Slack and explicit public publishing have their own data flows. See your data for the full feature-level map.
Publishing
Review a selected item and its sharing choices before creating a public link. Keeping a file with work does not make it public. Live previews can expose the selected title and item kind; public content is separate from an authenticated workspace view.
Manage active links through Publishing → Published and use their revoke or stop-publishing controls. Account sign-out and device disconnection do not replace reviewing those links. See results and sharing.
Leaving: signing out, disconnecting, deleting
| Action | What to understand before confirming |
|---|---|
| Sign Out | Ends this device's signed-in connection. It does not delete the workspace on the host Mac. |
| Disconnect | Removes a device/workspace connection while preserving the account. Other work and devices have their own access. |
| Delete Account | Removes the account identity and associated account data. On iPhone, local app data, including unsynced captures, can be cleared. The Mac workspace remains on that Mac. |
Use the export option offered before account deletion, and check that captures reached the Mac. Back up local work separately. Revoke public links and review teammates' or devices' access independently.
A workspace owner's departure needs deliberate ownership and access handling; changing a login is not a substitute. Follow the product's current account instructions and ask for help if ownership is unclear.
See privacy, your data, or troubleshooting.