Plugins deadlock on startup when calling `client.app.log()` (v1.4.8 regression)

[ghost91-]

Description

v1.4.8 deadlocks when plugins call client.app.log() during initialization. The TUI renders but never shows the active model.

Plugins

Any plugin using client.app.log() during initialization

OpenCode version

1.4.8, 1.4.9

Steps to reproduce

1. Save the following as ~/.config/opencode/plugins/my-plugin.ts:

   import type { Plugin, PluginModule } from "@opencode-ai/plugin"
   
   const server: Plugin = async ({ client }) => {
     await client.app.log({
       body: { service: "my-plugin", level: "warn", message: "hello" },
     })
     return {}
   }
   
   export default { id: "my-plugin", server } satisfies PluginModule

2. Start opencode
3. TUI renders but hangs before showing the active model

Screenshot and/or share link

No response

Operating System

Arch Linux (irrelevant)

Terminal

Alacritty (irrelevant)

Root Cause

v1.4.8 moved InstanceMiddleware before ControlPlaneRoutes in packages/opencode/src/server/server.ts:

// v1.4.8 (broken)
app: app
  .use(InstanceMiddleware())
  .route("/", ControlPlaneRoutes())
  ...

// v1.4.7 (working)
app: app
  .route("/", ControlPlaneRoutes())
  .route("/", InstanceRoutes(runtime.upgradeWebSocket))
  ...

InstanceMiddleware calls Instance.provide({ init: InstanceBootstrap }) on every request. InstanceBootstrap calls Plugin.init(), which loads all plugins. The deadlock:

1. InstanceMiddleware runs InstanceBootstrap → Plugin.init() → plugin server() runs
2. Plugin calls client.app.log() → in-process fetch to Hono
3. Hono routes the request through InstanceMiddleware again
4. Instance.provide() awaits the same bootstrap promise from step 1
5. Deadlock: step 4 waits for step 1, which waits for step 2, which waits for step 4

Possibly related: #23103, which may be the same deadlock triggered by a different code path through InstanceMiddleware.

[thdxr]

confirmed - fixing

[jlongster]

@ghost91- thanks for this report, will be fixed in #23150. We'll get a release out in the next 1-2 hours

If you want to try that branch, or dev when it's merged to confirm the fix, lmk. I'm pretty sure this will fix it. Thanks for the details

[ghost91-]

@jlongster i can confirm it’s fixed in 1.4.10. Thanks a lot for the quick fix!