Connect another device

The device that holds the project folder runs the agent. That device is the host. Any other device you sign in to can view and steer the session. This page connects your second device.

What sync gives you

• Sessions everywhere. Sessions and their transcripts stay current on every signed-in device.
• Remote control. Read the transcript, queue instructions, answer questions, and read diffs for a project that lives on another machine.
• Work that outlives your laptop. Close the laptop. The host keeps working, delivers your queued messages, and the session is up to date when you return.

Connect in three steps

You need an Admiral account. Accounts are invite-only. See The tester program.

1. Sign in on the host. In Admiral, open Settings > Account and select Sign in. Sign-in uses a short code, in the app or in a browser.
2. Sign in on the other device. Install Admiral on the second desktop, or open the iOS app, and sign in with the same account.
3. Pick the device. The device switcher in the sidebar lists your devices. Select the host to see its projects.

Rules worth knowing

• Signing in changes nothing on disk. Your existing local sessions do not upload, move, or import. They stay where they are.
• The storage mode is fixed at engine start. Admiral picks its storage mode, Local or Synced, when it starts. Sign in or out while the engine is stopped, then start the app.
• Local-only never touches the network. A device that is not signed in contacts no server.
• Attachments stay home. Images live on the host device. Other devices fetch them from the host when they need to show one.

The iOS app

The iOS app is a full peer: same account, same sessions, same controls. It runs no engine itself; it drives the engines on your machines. Distribution is through TestFlight.

Next steps

• Run a headless engine: make an always-on machine your host.
• Where your data lives: what sync does and does not do.