Settings are split between account settings, project settings, editor preferences, and privacy controls.
Home settings
From Home you can:
- update your profile name,
- open billing and upgrades,
- toggle diagnostic data,
- log out,
- choose a global model,
- choose a default target for the project creation prompt.
Editor settings
Inside a project, Settings includes project-specific options such as indexing and checkpoint behavior. Some settings belong to the project; some belong to the app.
Font settings
Embedr stores separate font sizes for:
- editor,
- chat,
- terminal,
- output.
This matters in classrooms and labs where a projected screen needs larger text than a laptop workflow.
Privacy controls
The current visible privacy control is diagnostic data. Diagnostic data helps improve the app by sharing technical interaction patterns. It should not include your source code, passwords, or personal file contents.
You can disable diagnostic data any time.
Tool approvals
Tool approval settings control how much the agent can do without asking each time.
Use stricter approvals when:
- teaching beginners,
- working in a valuable repo,
- using hardware that can be damaged by wrong behavior,
- running commands copied from the internet,
- editing files outside the project.
Use more permissive approvals when:
- doing quick local prototypes,
- repeatedly compiling,
- running safe read-only commands,
- you already have clean Git state.
Local storage
The desktop app uses local app storage for preferences and state such as:
- welcome state,
- selected board and port,
- selected environment,
- board options,
- custom targets,
- panel sizes,
- recent project state,
- font sizes,
- chat thread names,
- temporary update data.
Project source files are not stored inside this settings file.
Updates
Embedr can check for app updates through an update metadata endpoint. The update response includes latest version, release notes, release URL, and download URL when available.
If update check fails, verify internet access or download the latest installer manually from the website.
Account data versus project data
Account data includes sign-in identity, subscription state, and authenticated service access. Project data is your local folder.
When you log out:
- account-bound services stop,
- local project files remain on disk,
- local app preferences may remain unless manually cleared.
Practical privacy habits
- Keep secrets out of source files.
- Do not paste API keys into chat.
- Use environment files carefully and add them to
.gitignore. - Review terminal commands before approval.
- Treat generated docs and code as drafts until reviewed.