DotweaveDotweave
DocsGitHub
DotweaveDotweave
    • Introduction
    • Install Dotweave
    • Set up your first sync
    • Set up a second device
    • How syncing works
    • Directory and repository layout
    • Sync modes
    • Profiles
    • Platform-specific paths
    • Secrets and encryption
    • Track files and directories
    • Push, review, and commit day to day
    • Keep several devices in sync
    • Enable shell autocomplete
    • Install the agent skill
    • Upgrade config and repository formats
    • Troubleshoot a broken sync
    • dotweave init
    • dotweave track
    • dotweave push
    • dotweave pull
    • dotweave status
    • dotweave untrack
    • dotweave cd
    • dotweave profile
    • dotweave doctor
    • dotweave autocomplete
    • dotweave skill
    • manifest.jsonc
    • settings.jsonc
    • Environment variables and paths
    • Error messages
DocsGitHub
  1. Dotweave/
  2. settings.jsonc

settings.jsonc

The machine-local settings file that records which sync profile is active.

Location and version

settings.jsonc lives directly in the dotweave home directory, next to keys.txt and the repository sync directory. It is never committed, because it is not inside the sync directory.

The current version is 3. Dotweave migrates a version 2 file in place, writing a settings.jsonc.v2.bak backup first. Any other version fails the command.

A missing settings.jsonc is not an error. Dotweave treats it as "no active profile" and uses the implicit default profile.

The file is JSONC, so // and /* */ comments are allowed. A settings.json file sitting beside it is rejected rather than read.

Fields

FieldType and defaultPurpose
version3, requiredSchema version. Must be exactly 3 after migration.
activeProfilestring, optionalName of the profile this machine uses. Trimmed, and must be non-empty when present. Omit the field to use the default profile.

activeProfile must name a profile registered in manifest.jsonc, or the literal default. Dotweave validates the reference when it loads the sync config, not when it reads this file.

Example

{
  // This laptop syncs the work profile.
  "activeProfile": "work",
  "version": 3
}

Dotweave writes activeProfile only through dotweave profile use. Running dotweave profile use with no argument removes the field.

Errors

An unparseable file, a wrong version, or an empty activeProfile stops the command before any file is touched. Read Error messages for the exact messages and fixes.

Related pages

Read Profiles for what an active profile changes, or dotweave profile for the commands that write this file.

← PreviousConfigurationmanifest.jsoncEvery field in the version 8 sync manifest, including entry shape, platform value objects, and the validation rules Dotweave enforces.→ NextConfigurationEnvironment variables and pathsHow DOTWEAVE_HOME, XDG_CONFIG_HOME, and the Windows AppData fallbacks decide where Dotweave stores its data.

On this page

  1. Location and version
  2. Fields
  3. Example
  4. Errors
  5. Related pages