Where your data lives

Admiral is local-first. Your code and your sessions live on your machines. Nothing requires an account or a network.

The three profiles

A profile is the storage mode Admiral runs in. The engine fixes it at start:

Profile	Meaning
Local	No account. Everything stays on the device. This is the default.
Synced	Signed in. Sessions sync across your devices through the sync service.
Development	For building Admiral itself.

Two rules follow from this design:

Signing in does not move anything. Your existing local sessions do not upload, import, or change. They stay on the device that ran them.
Sign in or out only while the engine is stopped. Close the app, run the command or sign in at the prompt, then start the app again. The new start runs in the new mode.

With a Synced profile:

Session transcripts, names, and state sync between your devices.
Your queued instructions are delivered by the host device, even if you sent them from a device that is now offline.
Attachments stay on the host device. Other devices fetch them from the host when they need to show one.

It does not upload your code. The agent reads the code on the host, where the code lives.
It does not silently relocate sessions. Any device may view or drive a session; the session stays home.
A Local profile never contacts the sync service at all.

Agents run on your machines, inside your project folders.
The agent providers you sign in to receive what you send them, as with any use of those agents.
Admiral's sync service carries session data only for signed-in accounts, over encrypted connections.
Admiral sends no usage data, crash reports, or logs unless you are an approved tester who agreed in the app. Admiral never collects prompts, agent output, file contents, file paths, tokens, or secrets. See The tester program.