Skip to content

fix!: move default vault paths to the generic code/ XDG namespace#18

Merged
atyrode merged 1 commit into
mainfrom
fix/generic-xdg-namespace
Jul 17, 2026
Merged

fix!: move default vault paths to the generic code/ XDG namespace#18
atyrode merged 1 commit into
mainfrom
fix/generic-xdg-namespace

Conversation

@atyrode

@atyrode atyrode commented Jul 17, 2026

Copy link
Copy Markdown
Owner

The default vault-manifest lookup (~/.config/atyrode/code-auth-vaults.json) and new-vault broker state dirs carried an atyrode/ namespace inherited from the author's dotfiles — not self-contained for a public tool. Now everything defaults under code/, matching the generator's existing ~/.config/code/ + ~/.local/share/code/.

Migration for existing setups (one-time): mkdir -p ~/.config/code && mv ~/.config/atyrode/code-auth-vaults.json ~/.config/code/auth-vaults.json — or export CODE_AUTH_VAULTS_FILE to keep a custom location. Existing vaults' broker/token paths are recorded inside the manifest, so they keep working wherever they already live.

Marked fix! — a default-path change is behavior-breaking for anyone relying on the old default (it shipped for less than a day).

🤖 Generated with Claude Code

The vault manifest and per-vault broker state defaulted to an atyrode/
namespace inherited from the author's dotfiles — not self-contained for
a public tool. Defaults are now:

  ~/.config/code/auth-vaults.json          (manifest lookup)
  $XDG_STATE_HOME/code/auth-vaults/<id>/   (broker.token, new vaults)
  $XDG_CACHE_HOME/code/auth-vaults/<id>/   (snapshot.json, new vaults)

Existing vaults are unaffected in-place: their token/cache paths are
recorded in the manifest at creation time. Migrating means moving the
manifest file itself (or pointing CODE_AUTH_VAULTS_FILE at it).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@atyrode
atyrode enabled auto-merge (squash) July 17, 2026 00:13
@atyrode
atyrode merged commit 14e72a7 into main Jul 17, 2026
1 check passed
@atyrode
atyrode deleted the fix/generic-xdg-namespace branch July 17, 2026 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant