Having Camelia edit your whole project folder from the IDE
The IDE registers itself as one of Camelia's live surfaces, so the AI copilot can edit across your entire project Documents folder — not just one open file.
How it works
While you're in Software → IDE, the universal Camelia bar at the top of the page is wired to "the code" — this project's Documents files. Ask her to make a change and she edits the files server-side. After each of her turns, the IDE re-pulls the files from the encrypted store so you see the result.
She edits what you actually see
Your unsaved editor changes are shipped to Camelia each turn (within a size budget), so she works against the version on your screen rather than only the last saved copy. Very large unsaved files fall back to the server copy.
How conflicts are resolved on refresh
When the IDE re-pulls after her turn:
- Files she changed adopt her server copy — she already saw your unsaved edits there, and any local edits to those files are folded into her version. You'll get a notice listing what was folded in.
- Files she didn't touch keep your local edits, even if they're unsaved.
This keeps your in-progress work from being silently lost while still letting Camelia operate across the whole folder.
Good things to ask
Use it for cross-file work — refactors, adding a missing entry point, wiring imports, or scaffolding new files. If you're trying to get the preview running, "Fix with Camelia" is a focused version of the same capability aimed at making a project runnable.