How files load from and save to encrypted storage in the IDE

The IDE talks directly to your project's encrypted store — there is no third-party editing service in the loop. Here's how files move in and out.

Loading

When you open Software → IDE, it pulls the project's full file set from the encrypted Documents store and builds the file tree and editor from it. Imported repo clones come through with their full nested paths intact, so the tree mirrors your real folder structure.

Saving

Edits save back to the same encrypted store directly — the file you change in the browser is written to the project's Documents on save. Because all of this runs against your own project data, there's no external sync step.

How the storage is protected

Project content is encrypted at rest with AES-GCM. Each project (and folder bucket) gets its own key, derived server-side from a server-only master key using the bucket id, so one project's data can't be read with another's key. The encryption key never reaches the browser — decryption happens only on the server, just-in-time.

This is operator-decryptable envelope encryption, not zero-knowledge or end-to-end: the design keeps keys off the client, but it does not mean the data is mathematically un-readable by the operator.

Keeping your edits safe during AI runs

The IDE tracks which files you've changed but not yet saved. When Camelia edits files and the IDE re-pulls from the store, your local-only edits to files she didn't touch are kept, while files she changed adopt her server copy (she already saw your unsaved edits). You'll get a notice when that fold-in happens.