Where does my code and history live?

Why nothing syncs to a cloud

Because there is no server that would need your code, and adding one would create a class of risk the product has no reason to carry.

Where everything lives

• Your code stays in its folder. Muster reads it and runs agents in it. It never copies it anywhere.
• Sessions and transcripts are written by the CLI, in the CLI’s own directory on your machine. Muster indexes them; it does not upload them.
• Projects, queue, roles and settings live in a local database in the app’s data folder.
• Project passwords, if you use the vault, are encrypted by the system keychain. The plaintext is decrypted in the main process and written straight to the clipboard, which clears itself in thirty seconds; it never passes through the interface layer. Without a keychain, Muster refuses to store rather than storing in the clear.

What does leave your machine

Exactly what the agent CLI sends to its own provider, on your account, as it would from your terminal. Muster makes no model calls of its own — every token is spent by the CLI you already use.

The only other network traffic is the update check and, once, the licence activation.

What you give up

There is no sync between your laptop and your desktop, no shared workspace, no team view. Muster is one developer, one machine, one set of agents.

That is a deliberate scope, not a roadmap gap. The moment sessions sync, there is a server holding your repository’s contents, an account system around it, and a breach surface that has to be defended forever — for a convenience that a second machine solves by opening the project there.