claude-code - 💡(How to fix) Fix [Feature Request] Support relative/portable paths in plugin manifest installPath for cross-environment ~/.claude sharing [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56462Fetched 2026-05-06 06:27:24
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description Plugin manifests installed_plugins.json and known_marketplaces.json store installPath / installLocation as absolute paths captured at install time (e.g. /home/alice/.claude/plugins/cache/...).

This breaks any setup where ~/.claude is shared across environments with different usernames:

  • Devcontainers (host user ≠ container vscode/node)
  • Multi-user shared homedirs over NFS
  • Restoring .claude backup on a new machine with different username
  • Codespaces / remote dev where $HOME differs from local

Symptom: plugins listed but slash commands/skills not loaded inside the second environment, since paths point nowhere.

Request: support one of

  • ~ expansion in installPath / installLocation
  • $HOME / ${HOME} expansion
  • Paths relative to the JSON file's directory (or to ~/.claude)

Preferred: relative paths, since they're unambiguous and don't depend on env at read time. Could be opt-in via a config flag if backward compatibility is a concern.

Repro: install any plugin on host, bind-mount ~/.claude into a devcontainer with a different remoteUser, observe plugin missing.

Environment Info

  • Platform: linux
  • Terminal: konsole
  • Version: 2.1.126
  • Feedback ID: 556123c7-4b9d-4fc9-a9a2-1b018b78d8d1

extent analysis

TL;DR

Support for relative paths in plugin manifests could resolve the issue of plugins not loading in different environments.

Guidance

  • Consider using relative paths in installed_plugins.json and known_marketplaces.json to make the setup more flexible across environments.
  • Evaluate the feasibility of implementing ~ or $HOME expansion in installPath and installLocation as an alternative solution.
  • Investigate the possibility of introducing a config flag to opt-in for relative paths, ensuring backward compatibility.
  • Test the proposed solution in a devcontainer setup with a different remote user to verify its effectiveness.

Example

No code snippet is provided as the issue description does not include specific code references.

Notes

The proposed solution may require changes to the plugin installation process and the parsing of installed_plugins.json and known_marketplaces.json. It is essential to ensure that the new approach does not introduce compatibility issues with existing plugins.

Recommendation

Apply a workaround by using relative paths in plugin manifests, as it is the preferred solution mentioned in the issue description, providing an unambiguous and environment-agnostic way to store plugin locations.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Support relative/portable paths in plugin manifest installPath for cross-environment ~/.claude sharing [1 comments, 2 participants]