Repository navigation
fix(core): avoid plugin reloads from ecosystem state writes #36173
Description
Reproduction
- Run V2 with
~/.claudepresent. - Perform any operation that writes below
~/.claude(for example, routine Claude state updates). - Observe
config.updated, complete plugin reloads, andPlugins reloadednotifications across matching sessions.
Impact
Unrelated operational writes repeatedly reload every plugin generation and notify all sessions sharing the watched location.
Root cause
Commit 99e5230 added discovered .claude and .agents directories wholesale to recursive config watcher targets. These directories are skill discovery sources, not config roots, so every descendant write is treated as a config change.
Expected behavior
Continue discovering ecosystem skill directories and normal OpenCode configuration, but only watch actual config roots/files for config changes. Skill file invalidation should continue through the existing filesystem change path.
Activity
opencode-agent commentedon Jul 10, 2026
Latest huddle context: keep ecosystem dirs discoverable, but don't recursively watch compatibility roots wholesale; watcher policy should be decided from typed config/source entries. Source discussion: https://slack.com/archives/C0BE69AHCQP/p1783640722114279
opencode-agent commentedon Jul 10, 2026
Audit status: #36174 had the right shape and said , but it was closed unmerged (). This issue should stay open until the replacement watcher-scope fix lands.
opencode-agent commentedon Jul 10, 2026
Correction to audit note above: PR #36174 had the right shape and said
Closes #36173, but it was closed unmerged (mergedAt: null). This issue should stay open until the replacement watcher-scope fix lands.opencode-agent commentedon Jul 30, 2026
Addressed by commit f685d7a (
fix(core): narrow ecosystem config watches). V2 still discovers global/project.claudeand.agentscompatibility skill directories as typed config entries, but excludes those directories from recursive Config watcher targets. The focused regression test verifies discovery remains intact while only actual config roots are watched, so unrelated ecosystem state writes no longer trigger plugin/config reloads. Closing as resolved.