Skip to content

fix(setup): accept registry from plugin data dir, not just cache #388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
auroracapital merged 1 commit into from
May 30, 2026
+6 −3
Merged

fix(setup): accept registry from plugin data dir, not just cache #388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions claude-ops/scripts/setup.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,12 @@ for tool in "${MISSING[@]}"; do
echo " ✗ ops: $tool not found — run /ops:setup to configure"
done

# Check registry
REGISTRY="$SCRIPT_DIR/registry.json"
if [ ! -f "$REGISTRY" ]; then
# Check registry. The canonical registry lives in the plugin DATA dir
# (CLAUDE_PLUGIN_DATA_DIR), which survives plugin upgrades; the cached copy
# under $SCRIPT_DIR is wiped on every upgrade. Accept either location so a
# valid data-dir registry doesn't trigger a false "no registry" warning.
REGISTRY_DATA_DIR="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}"
if [ ! -f "$SCRIPT_DIR/registry.json" ] && [ ! -f "$REGISTRY_DATA_DIR/registry.json" ]; then
echo " ✗ ops: no project registry — run /ops:setup to create one"
fi

Expand Down
Loading