[dependabot]

Bumps the npm-minor-patch group with 3 updates in the / directory: @opencode/plugin, solid-js and vite-plugin-solid.

Updates @opencode/plugin from 2.2.1 to 2.2.5

Release notes

Sourced from @​opencode/plugin's releases.

v2.2.5

Highlights

• Worktree and Shell Mode Shortcuts: Press ⌘⌥O on macOS or Ctrl+Alt+O on Windows and Linux to choose a worktree, and ⌘⌥B or Ctrl+Alt+B to choose its base branch. ⌘⇧X or Ctrl+Shift+X now toggles shell mode in the composer. (#60713)
• Send Quotes From the Comment Popup: Hold ⌘ or Ctrl in the quote popup to turn its checkmark into send, or press ⌘Enter or Ctrl+Enter, to send just that quote and comment while leaving the rest of the composer untouched. (#60640)
• Percentage Compaction Buffer: Set "compaction": { "buffer": "20%" } in opencode.json to keep a share of each model's context window free, so one setting fits models with small and large windows. Token counts still work. (#60647)

Core

Improvements

• compaction.buffer accepts a percentage of the model's context window, such as "20%", in addition to a token count. (#60647)
• When read misses because a folder is missing, the error names that folder and the nearest one that exists. (#60688)
• When edit can't find oldString, the error shows the file's closest lines, or says the change is already there. (#60689)
• Calls to a tool named bash now run as shell instead of failing, with the same permissions. A plugin tool actually named bash still takes precedence. (#60687)

Bug fixes

• MCP servers that send stdio messages larger than 10 MiB no longer get disconnected, and large messages are read much faster. (#60694)
• Idle locations no longer restart their MCP servers right after shutting down. (#60668)
• Compaction now caps its prompt at the model's context window when the input limit is larger. (#60660)
• LiteLLM context window errors now trigger compaction instead of stopping the session. (#60692)
• Reasoning is no longer turned into plain text when you switch models or resume an interrupted response, which caused request errors on some providers. (#60498)

TUI

Bug fixes

• The connect menu no longer lists MCP servers, which are managed in their own place. (#60675)

Desktop

Improvements

• Added keyboard shortcuts to choose a worktree and its base branch, shown in tooltips, and a shortcut to toggle shell mode. The worktree path can be selected to copy the full directory. (#60713)
• Hold ⌘ or Ctrl in the quote popup to send a quote and its comment directly. (#60640)
• Added flat input surfaces and a compact input size. (#60598)

Bug fixes

• The connect menu no longer lists MCP servers. (#60675)
• Added the missing top inset to the search field in the recently closed menu. (#60652)

v2.2.4

Highlights

• Persistent Desktop Terminals: Desktop terminals now belong to the session, survive server restarts with their scrollback, and stay synchronized with the TUI and other windows. Renamed terminals also keep their names across restarts. (#60346)
• Publish Interactive Artifacts: Enable "experimental": { "artifacts": true } in opencode.json to let agents publish, update, and serve HTML or static artifacts through the built-in local provider or plugin-provided storage. (#60351)
• Guided Claude Agent Setup: Select Claude Agent from the provider picker to copy claude auth login, install Claude Code, and verify the connection before continuing to model selection. (#60603)
• Choose a Base Branch Quickly: While creating a worktree, open Choose base branch with ⌘⌥. on macOS or Ctrl+Alt+. on Windows and Linux. The command is also available in the command palette and Settings › Shortcuts. (#60579)

... (truncated)

Changelog

Sourced from @​opencode/plugin's changelog.

v2.2.5 — 2026-10-30

Highlights

• Worktree and Shell Mode Shortcuts: Press ⌘⌥O on macOS or Ctrl+Alt+O on Windows and Linux to choose a worktree, and ⌘⌥B or Ctrl+Alt+B to choose its base branch. ⌘⇧X or Ctrl+Shift+X now toggles shell mode in the composer. (#60713)
• Send Quotes From the Comment Popup: Hold ⌘ or Ctrl in the quote popup to turn its checkmark into send, or press ⌘Enter or Ctrl+Enter, to send just that quote and comment while leaving the rest of the composer untouched. (#60640)
• Percentage Compaction Buffer: Set "compaction": { "buffer": "20%" } in opencode.json to keep a share of each model's context window free, so one setting fits models with small and large windows. Token counts still work. (#60647)

Core

Improvements

• compaction.buffer accepts a percentage of the model's context window, such as "20%", in addition to a token count. (#60647)
• When read misses because a folder is missing, the error names that folder and the nearest one that exists. (#60688)
• When edit can't find oldString, the error shows the file's closest lines, or says the change is already there. (#60689)
• Calls to a tool named bash now run as shell instead of failing, with the same permissions. A plugin tool actually named bash still takes precedence. (#60687)

Bug fixes

• MCP servers that send stdio messages larger than 10 MiB no longer get disconnected, and large messages are read much faster. (#60694)
• Idle locations no longer restart their MCP servers right after shutting down. (#60668)
• Compaction now caps its prompt at the model's context window when the input limit is larger. (#60660)
• LiteLLM context window errors now trigger compaction instead of stopping the session. (#60692)
• Reasoning is no longer turned into plain text when you switch models or resume an interrupted response, which caused request errors on some providers. (#60498)

TUI

Bug fixes

• The connect menu no longer lists MCP servers, which are managed in their own place. (#60675)

Desktop

Improvements

• Added keyboard shortcuts to choose a worktree and its base branch, shown in tooltips, and a shortcut to toggle shell mode. The worktree path can be selected to copy the full directory. (#60713)
• Hold ⌘ or Ctrl in the quote popup to send a quote and its comment directly. (#60640)
• Added flat input surfaces and a compact input size. (#60598)

Bug fixes

• The connect menu no longer lists MCP servers. (#60675)
• Added the missing top inset to the search field in the recently closed menu. (#60652)

v2.2.4 — 2026-10-30

Highlights

• Persistent Desktop Terminals: Desktop terminals now belong to the session, survive server restarts with their scrollback, and stay synchronized with the TUI and other windows. Renamed terminals also keep their names across restarts. (#60346)
• Publish Interactive Artifacts: Enable "experimental": { "artifacts": true } in opencode.json to let agents publish, update, and serve HTML or static artifacts through the built-in local provider or plugin-provided storage. (#60351)

... (truncated)

Commits

• 9bbb8ce release: v2.2.5
• 872f694 release: v2.2.4 (#60664)
• 8f0fc21 feat(core): add experimental artifacts with pluggable providers (#60351)
• b44b716 release: v2.2.3 (#60564)
• f29e281 feat(core): add Claude Agent provider (#58782)
• 8fdf2e5 feat(app): fit the session header at narrow timeline widths (#59512)
• 13e8186 chore(tui): use OpenTUI 0.8.0 (#60385)
• a88d3ca fix(app): match own server loopback port before treating http servers as loca...
• 4efad23 release: v2.2.2 (#60337)
• f74b141 release: v2.2.1 (#60113)
• Additional commits viewable in compare view

Updates solid-js from 1.9.17 to 1.9.18

Commits

• See full diff in compare view

Updates vite-plugin-solid from 2.11.14 to 2.11.15

Release notes

Sourced from vite-plugin-solid's releases.

vite-plugin-solid@2.11.15

Patch Changes

• 62e2b75: Production builds now dedupe solid-js the same way dev does. A dependency with its own nested copy of solid-js no longer adds a second runtime to the bundle, which broke context lookups (#112).
• a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with the jsdom default
• 9e67618: fix: exclude test mode from HMR setup
• a7ec25f: Fix TypeError: Cannot read properties of undefined (reading 'extend') in tests on Vitest before 1.0 with @testing-library/jest-dom 6 or later installed (#141). The plugin now injects jest-dom's ESM vitest entry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.
• 6cc30fe: Only inject the @testing-library/jest-dom Vitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail with Failed to load url .../@testing-library/jest-dom/vitest.
• d0e47f1: Vitest runs keep the jsdom environment and the @testing-library/jest-dom setup file when test.server.deps.external already lists solid-js. The plugin used to drop its whole test config in that case.
• f8439e8: The plugin no longer changes resolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such as vite-plugin-node-polyfills mapping path (#130).
• df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons' ~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#206). Custom extensions are now also matched when the query contains a dot.
• b50c064: Keep $ServerOnly templates in client transforms while HMR is active so hot updates of components using $ServerOnly no longer throw template is not a function. An explicit solid.omitServerOnlyTemplates setting still takes precedence.
• cd79ed9: Without ssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app with ssrLoadModule no longer throws "Client-only API called on the server side" (#64). Vitest keeps DOM output.
• 9c17655: Server builds with ssr.target: 'webworker' now resolve the server build of solid-js. The plugin adds the worker export condition to that build, so renderToString and the other server APIs no longer resolve to their browser stubs (#153). This works on Vite 4 and later.
• 8909380: Vite 8's dependency scan no longer breaks on .tsx files (issue #262). The plugin previously set optimizeDeps.rolldownOptions.transform.jsx: 'preserve' to stop Rolldown from injecting react/jsx-dev-runtime imports during the scan — but the scanner re-parses the transformed output as plain JS (import.meta.glob handling force-tags modules as js), so any .tsx with JSX was a hard PARSE_ERROR: Unexpected JSX expression that aborted the whole scan and skipped pre-bundling. The scan transform now uses the classic JSX runtime, which lowers JSX to bare React.createElement calls without injecting any import: the scan output is never executed, it only exists so rolldown can walk the import graph, so the undefined identifier is harmless. Backport of the fix already on the 3.0.0-next line.
• 5d6846c: When the root config declares test.projects and leaves test.sharedViteServer unset, the plugin now sets it to false so every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option to true, and a shared inline project takes its test options from the raw root block captured before any config hook runs, so it lost everything the plugin injects (the jsdom default, the @testing-library/jest-dom setup file, server.deps). Ports solidjs/solid-vite-plugin#370; refs #369.
• 32adc90: In Vitest DOM tests (the jsdom default, no ssr option), the plugin now inlines solid-js and the packages that import it without a solid export condition, such as @solidjs/testing-library. Before, they stayed external, and the host runtime resolved their own imports. Node gets the browser condition from Vitest's worker --conditions, but Deno does not apply it in worker threads and resolves deno/node. Under Deno, @solidjs/testing-library loaded the server build of solid-js/web and rendersolidjs/solid-vite-plugin#369browser condition and loads one client-build instance. A test.server.deps.inline list is merged with the plugin's, and a test.server.deps.external entry for solid-js still opts out. With ssr: true, tests keep solid-js external as before.
• 765a406: In jsdom and happy-dom tests, Node no longer gets the browser condition for packages that Vitest leaves external. Node-only packages such as msw/node now load under Vitest 4 and later (#125).
• c750c34: Packages with a solid export condition that are declared only in the workspace root's package.json are now inlined for projects in that workspace. Before, Vitest loaded them with Node and failed with Unknown file extension ".jsx" (#157).

Changelog

Sourced from vite-plugin-solid's changelog.

2.11.15

Patch Changes

• 62e2b75: Production builds now dedupe solid-js the same way dev does. A dependency with its own nested copy of solid-js no longer adds a second runtime to the bundle, which broke context lookups (#112).
• a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with the jsdom default
• 9e67618: fix: exclude test mode from HMR setup
• a7ec25f: Fix TypeError: Cannot read properties of undefined (reading 'extend') in tests on Vitest before 1.0 with @testing-library/jest-dom 6 or later installed (#141). The plugin now injects jest-dom's ESM vitest entry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.
• 6cc30fe: Only inject the @testing-library/jest-dom Vitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail with Failed to load url .../@testing-library/jest-dom/vitest.
• d0e47f1: Vitest runs keep the jsdom environment and the @testing-library/jest-dom setup file when test.server.deps.external already lists solid-js. The plugin used to drop its whole test config in that case.
• f8439e8: The plugin no longer changes resolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such as vite-plugin-node-polyfills mapping path (#130).
• df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons' ~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#206). Custom extensions are now also matched when the query contains a dot.
• b50c064: Keep $ServerOnly templates in client transforms while HMR is active so hot updates of components using $ServerOnly no longer throw template is not a function. An explicit solid.omitServerOnlyTemplates setting still takes precedence.
• cd79ed9: Without ssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app with ssrLoadModule no longer throws "Client-only API called on the server side" (#64). Vitest keeps DOM output.
• 9c17655: Server builds with ssr.target: 'webworker' now resolve the server build of solid-js. The plugin adds the worker export condition to that build, so renderToString and the other server APIs no longer resolve to their browser stubs (#153). This works on Vite 4 and later.
• 8909380: Vite 8's dependency scan no longer breaks on .tsx files (issue #262). The plugin previously set optimizeDeps.rolldownOptions.transform.jsx: 'preserve' to stop Rolldown from injecting react/jsx-dev-runtime imports during the scan — but the scanner re-parses the transformed output as plain JS (import.meta.glob handling force-tags modules as js), so any .tsx with JSX was a hard PARSE_ERROR: Unexpected JSX expression that aborted the whole scan and skipped pre-bundling. The scan transform now uses the classic JSX runtime, which lowers JSX to bare React.createElement calls without injecting any import: the scan output is never executed, it only exists so rolldown can walk the import graph, so the undefined identifier is harmless. Backport of the fix already on the 3.0.0-next line.
• 5d6846c: When the root config declares test.projects and leaves test.sharedViteServer unset, the plugin now sets it to false so every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option to true, and a shared inline project takes its test options from the raw root block captured before any config hook runs, so it lost everything the plugin injects (the jsdom default, the @testing-library/jest-dom setup file, server.deps). Ports solidjs/solid-vite-plugin#370; refs #369.
• 32adc90: In Vitest DOM tests (the jsdom default, no ssr option), the plugin now inlines solid-js and the packages that import it without a solid export condition, such as @solidjs/testing-library. Before, they stayed external, and the host runtime resolved their own imports. Node gets the browser condition from Vitest's worker --conditions, but Deno does not apply it in worker threads and resolves deno/node. Under Deno, @solidjs/testing-library loaded the server build of solid-js/web and rendersolidjs/solid-vite-plugin#369browser condition and loads one client-build instance. A test.server.deps.inline list is merged with the plugin's, and a test.server.deps.external entry for solid-js still opts out. With ssr: true, tests keep solid-js external as before.
• 765a406: In jsdom and happy-dom tests, Node no longer gets the browser condition for packages that Vitest leaves external. Node-only packages such as msw/node now load under Vitest 4 and later (#125).
• c750c34: Packages with a solid export condition that are declared only in the workspace root's package.json are now inlined for projects in that workspace. Before, Vitest loaded them with Node and failed with Unknown file extension ".jsx" (#157).

Commits

• 884edff chore: point package metadata at the renamed solid-vite-plugin repo (#502)
• 7c9885d Merge pull request #429 from solidjs/changeset-release/main
• 591c9e4 Version Packages
• 98bf9f7 Merge pull request #491 from solidjs/claude/solid-1x-release-ithwfa
• 7afa18a test: link jest-dom into the fake projects in jest-dom.test.ts
• 4bf407b Merge PR #238
• 9ad07fc Merge PR #452
• 4cdffff Merge PR #426
• e01ce9a Merge PR #412
• dae0ea1 Merge PR #445
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions