Software And Code
10 articles
Using the in-browser CodeMirror IDE over your Documents folder
Software → IDE is a self-hosted CodeMirror 6 editor over your project's full Documents folder, with a file tree, multi-language syntax highlighting, and in-place editing.
How files load from and save to encrypted storage in the IDE
IDE files load from and save to the project's encrypted store directly — AES-GCM at rest, per-project keys that never leave the server. No third-party editor backend.
Previewing your code in the sandboxed in-browser preview
The IDE preview bundles client-side web projects locally with esbuild-wasm and renders them in a sandboxed iframe — your code never leaves the origin; server/Next.js code can't run.
Using 'Fix with Camelia' to make a preview runnable
When the IDE preview can't run, 'Fix with Camelia' asks the copilot to add a browser entry, ensure React deps, fix imports, then saves and re-runs automatically.
Importing a public repo with the Open Source Explorer
The Open Source Explorer browses public repos via GitHub Search (presets or free text) and imports any of them into your current project, cloning into its Documents folder.
How an imported repo is cloned and decomposed into components and flows
An imported repo is cloned into a folder in the current project's Documents (keeping its nested structure) and decomposed into components and flows you can work with.
Editing project secrets, API keys, and env vars in Environment
Software → Environment is a per-project editor for secrets, API keys, and env vars — add, update, and delete entries stored encrypted at rest with a project-scoped key.
Why secret values are masked and never returned to the browser
Saved secret values are returned only as masked hints, never as plaintext — keys are encrypted at rest and decrypted server-side, so the full value never reaches the browser.
Having Camelia edit your whole project folder from the IDE
In the IDE, Camelia's bar edits across your whole project Documents folder server-side; your unsaved edits are sent to her each turn and the IDE re-pulls after she runs.
Where imported repositories land inside your current project
Imported repos always land as a folder inside your current project's Documents (decomposed into components and flows) — never a new project. Switch projects first if needed.