TUI crash: PluginProvider is missing #50415

Activity

1. cauezinho2008 commented on Sep 21, 2026

   

   cauezinho2008

   on Sep 21, 2026

   Author

   More actions

   happened when i tried to ask using /btw
2. 1994rstefan commented on Sep 23, 2026

   

   1994rstefan

   on Sep 23, 2026

   More actions

   Seems to be a duplicate of #49777.

   Fixed in 2.0.9 thx
3. brettanthonysjoberg179-lab commented on Sep 27, 2026

   

   brettanthonysjoberg179-lab

   on Sep 27, 2026

   More actions

   This is a duplicate of #49777 (tui: /btw crashes when rendering answer dialog), which was closed as fixed in 2.0.9. Suggest closing this one as a duplicate.

   Adding root-cause details and a new environment data point (Linux, and notably zero plugins configured), which isn't yet covered by the existing confirmations in #49777 (those are macOS x2 and Windows).

   Environment

   • opencode version: 2.0.8
   • OS: Linux 6.6.141-09476-g954adab60416 (linux x64)
   • Terminal: TERM=xterm-256color, no COLORTERM / TERM_PROGRAM set
   • Shell: /bin/bash
   • Install/channel: latest release
   • Active plugins: none

   Reproduction

   1. Open an existing session in the TUI.
   2. Run /btw <question> (or /btw and answer the prompt).
   3. When the answer is rendered, the TUI crashes.

   Not currently able to confirm consistency across repeated runs, since I'm on 2.0.8 and expect to upgrade first.

   Actual Behavior

   Error: PluginProvider is missing
       at sa (/$bunfs/root/chunk-vbstx86m.js:2593:2804)
       at Uc (/$bunfs/root/chunk-x0cbprj9.js:4:248)
       at Jr (/$bunfs/root/chunk-zr6pz3ag.js:2:7348)
       at children (/$bunfs/root/chunk-vbstx86m.js:2590:118420)
       ...
   

   Same offsets as #49790 and #50415's other reports — only the chunk hash differs per build.

   Root cause, from the shipped bundle

   I extracted the relevant code from the 2.0.8 binary. The throw site is the PluginProvider context accessor:

   function sa(){let t=Xn(ZW);if(!t)throw Error("PluginProvider is missing");return t}

   The frame directly beneath it, Uc, is the /btw answer dialog. Note that it calls the accessor unconditionally at the top of the component body, before any plugin-conditional logic:

   function Uc(t){let r=Je(),o=Vt(),i=QH(),u=sa(),l=He("elevated"),m=He("overlay"),h=Zn().currentSyntax,
     p=Ct().data,D=et(),b=c(()=>Math.max(3,Math.floor(D().height/2))),[x,w]=v(!1),...

   Because the read happens during component setup rather than inside a lazy computation, the dialog throws on render whether or not any plugin is installed. This is consistent with the diagnosis in #49777 that PluginProvider is mounted beneath DialogProvider while dialogs render outside that subtree.

   There are 11 call sites of this accessor in the TUI bundle; any of them mounted outside the provider would fail the same way, so this may affect more surfaces than /btw alone.

   Note on the "Active plugins" field

   Worth calling out for triage: the crash screen / auto-report doesn't capture plugin state, which makes this look like a plugin bug. It isn't. I reproduced it with no plugins configured at all — no plugin key in opencode.jsonc, and no .opencode/plugin/ or .opencode/plugins/ directory. PluginProvider here is internal to opencode, not something a user installs.
4. neriousy commented on Oct 20, 2026

   

   neriousy

   on Oct 20, 2026

   Member

   More actions

   Thanks for the report. The /btw answer dialog now receives its markdown renderer without accessing the missing plugin context, fixing this crash. I'm closing this; if it comes back on the latest v2, please open a new issue with your version and steps.
5. neriousy

   closed this as completedon Oct 20, 2026