Skip to content

Settings

Available

CutReady has two levels of settings: Global settings that apply everywhere, and Workspace settings that apply to the current workspace and can override global defaults. Both open as full-width panels (no sidebar).

Open global settings from the gear icon (⚙️) pinned to the bottom of the sidebar. Global settings apply across all workspaces.

Global settings panelGlobal settings panel
Global settings with Display, Themes, AI Provider, Agents, Feedback, and Updates tabs

Set the name and email CutReady signs your snapshots with. Your profile is saved on this computer, not in the workspace, so each collaborator keeps their own.

If you leave it empty, manual saves use the first name and email CutReady finds. Automatic workspace saves require a complete saved profile:

  1. Your profile — the values saved in this tab.
  2. Environment — GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL.
  3. Git config — user.name and user.email for the workspace, or your global git config.
  4. System username — a name only.

The tab shows which source each value came from. If no email is found, CutReady asks for your name and email the first time you save a snapshot. Changes CutReady saves for you, like adding or renaming a project, save only the files they touch. Automatic saves require a complete identity in your CutReady profile; a detected Git identity alone isn’t used for these saves. They stay in your pending changes, with a notice, if your profile is missing or those files already had unsaved edits. Select Use detected to clear your profile and go back to the detected values.

Open workspace settings from the monitor icon (🖥️) in the sidebar navigation. Workspace settings apply to the current workspace only and can override global defaults for repository, memory, display, theme, AI provider, and agent settings.

Configure the GitHub remote for syncing your workspace. Enter the HTTPS or SSH URL and click Test Connection to verify. See Workspace Remote for full details.

CutReady stores all sensitive credentials — API keys, OAuth tokens, and personal access tokens — in an IOTA Stronghold encrypted vault. The vault file (vault.hold) lives in the app data directory, not in your workspace.

  • Automatic migration: On first launch after upgrading, any plaintext credentials in settings.json are migrated to the encrypted vault
  • Transparent: No password prompt — encryption is handled automatically
  • Secure by default: Credentials never touch the filesystem in plaintext

Global settings are persisted in Tauri’s app data directory. Workspace settings are stored within the workspace. All settings apply immediately when changed — no restart required.