core: plugin event subscriptions receive events from every location #57474

Activity

1. opencode-agent commented on Oct 20, 2026

   

   opencode-agentBot

   on Oct 20, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed write-up and for tracking down the cause.

   I think this is a duplicate of #56290. That issue reports the same ctx.event.subscribe() problem, and its reproduction found that the multiplier is the number of loaded locations, as you describe. Possible duplicates and related items, most likely first:

   • plugins: event subscribers fire once per client connection — N× side effects, undocumented #56290: same issue. Plugins start once per loaded location, and each copy's ctx.event.subscribe() receives events from every location, because plugin activation drops Location.Service.
   • fix(core): preserve location scope for plugin event subscriptions and catalog reloads #57186 (open PR): restores the location for plugin subscriptions. It also stamps the location on catalog notify publishes such as command.updated when a plugin calls ctx.<domain>.reload(), which is your second point about events carrying no location.
   • fix(core): scope plugin events to their location #56346 (open PR): scopes plugin event streams to the plugin's location (closes plugins: event subscribers fire once per client connection — N× side effects, undocumented #56290).
   • core: located Bus events visit unrelated Location subscribers #52921: related. Location-scoped bus subscribers still get visited for events from other locations (a performance problem, not a plugin one).
   • Plugin instances accumulate across config reloads (no teardown) — system-reminder injected N times #54140: related. Plugin instances pile up across config reloads, with a similar N× symptom but a different cause.
   • core: long-lived V2 server enters persistent allocation loop #36677: the allocation-loop report you linked. Possibly made worse by this, but a separate report.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 20, 2026
3. WilliamAGH commented on Oct 20, 2026

   

   WilliamAGH

   on Oct 20, 2026

   Author

   More actions

   Duplicate of #56290; the fix is tracked in #57186.
4. WilliamAGH

   closed this as not plannedon Oct 20, 2026
5. opencode-agent

   closed this as duplicateon Oct 21, 2026
6. opencode-agent commented on Oct 21, 2026

   

   opencode-agentBot

   on Oct 21, 2026 – with OpenCode Agent

   Contributor

   More actions

   Closing this as a duplicate of #56290, since we haven't heard back. Both reports are about ctx.event.subscribe() in a plugin receiving events from every loaded location, because plugin activation drops Location.Service. Please follow #56290 for progress. Two open PRs address it: #56346, and #57186, which also stamps the location on command.updated and similar events published when a plugin calls ctx.<domain>.reload(). If your case turns out to be different, reply here and we can reopen it. Thanks for the detailed analysis.