Data, guardrails, and updates

Fynvra runs on your machine; settings, sessions, and keys live in the local app-data directory. File access is limited to attached workspaces, but agents and MCP can still run commands or reach external services, so set tool policy and approval mode per project.

Where data lives

Settings, roles, providers, MCP, and sessions live in the local app data directory. Don’t commit that folder or send it to anyone. Dev builds use fynvra-dev, separate from an installed release. FYNVRA_USER_DATA_DIR is honored only in dev mode.

Large text such as system prompts and instruction files is not stored in settings.json; roles and instruction entries live in their own files in the data directory. Plaintext API keys, MCP environment values, and headers are read only by the main process; the UI shows masks or key names.

Guardrails

• File access is limited to attached workspaces. The renderer cannot use Node.js or Electron directly.
• Agents and MCP can still run commands or reach external services, so set the tool policy and approval mode per project.
• Removing a workspace only removes it from the list; deleting a session removes it from the list while keeping the underlying record. Archiving does not delete worktrees that are still in use or unmerged.
• Protected operations such as git push, git reset --hard, and rm -rf require confirmation in every approval mode.

Updates

Installed Windows builds, and macOS builds signed with a Developer ID, check at startup and every 4 hours. The download installs after you confirm a restart. Unsigned Mac builds are replaced by hand from Releases. Dev mode (pnpm dev) does not check for updates. Linux has no auto-update yet.

Settings → General → App updates shows the current version and check state; follow the prompt to restart and install when an update is ready.