claude-code - 💡(How to fix) Fix [FEATURE] 切换供应商之后 , 安装的插件没有自动启动 [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#46305Fetched 2026-04-11 06:23:48
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

当前claude code如果安装了插件 , 需要配置enabledPlugins属性 , 插件才会真正生效 , 问题是当我切换了供应商之后 , 我的另外一个供应商的settings.json文件并没有配置这个属性 , 或者配置的插件少了 , 导致每次我切换供应商的时候都要重新配置一次漏了的插件

如下图 , 图二是我经常使用的供应商配置文件 , 图一是我兜底的供应商 , 当我切换的时候 , 启用的插件就少了 <img width="472" height="138" alt="Image" src="https://github.com/user-attachments/assets/7cade1b8-275e-4ace-9dca-04a555867363" />

<img width="704" height="394" alt="Image" src="https://github.com/user-attachments/assets/8aaeec80-0828-444d-bb46-aabcc65d4fd9" />

Proposed Solution

能不能加一个功能 , 类似(如下图) , 有一个选项 , 勾选了之后 , enabledPlugins的所有属性都写入到通用模板 或者 你有更好的想法实现

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implement a feature to automatically synchronize or inherit enabledPlugins configurations across different supplier settings to avoid manual reconfiguration.

Guidance

  • Identify the common plugins used across suppliers and consider creating a default or template configuration for enabledPlugins that can be applied or inherited when switching suppliers.
  • Explore the possibility of implementing a synchronization mechanism that updates the enabledPlugins settings in the secondary supplier's configuration file (settings.json) when the primary supplier's configuration is updated.
  • Consider adding an option to manually override or merge plugin configurations when switching suppliers to accommodate unique requirements.
  • Evaluate the feasibility of storing plugin configurations in a centralized location, allowing for easier management and synchronization across different suppliers.

Example

No specific code example can be provided without more context about the existing implementation, but a potential approach could involve creating a function that compares and merges plugin configurations between suppliers.

Notes

The proposed solution aims to reduce manual configuration efforts when switching suppliers. However, the exact implementation details may vary depending on the existing architecture and requirements of the Claude code system.

Recommendation

Apply a workaround by creating a script or tool that manually synchronizes enabledPlugins configurations across supplier settings until a more integrated feature can be developed. This approach allows for immediate productivity gains while a more comprehensive solution is explored.

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