Plugin setup notification never disappears (plugin not recognized as installed)

[gabszap]

The plugin does not work at all on my setup.

I installed it both via npm and by building it manually, but in both cases the setup notification never disappears from the bar, which indicates that the plugin is not being recognized as installed.

From what I understand, this notification should disappear once the plugin is properly installed, but that never happens.

What I’ve tried:

• Restarted the app multiple times
• Tried project-specific configuration
• Reinstalled the plugin using different methods (npm and manual build)

None of these worked.

Environment:

• OS: Windows 11
• Warp: Latest version
• OpenCode: Latest version

[zachbai]

@harryalbert mind taking a look?

[harryalbert]

Thanks for flagging this @gabszap! Unfortunately, with opencode we can't tell whether the plugin is installed until you actually send your first query (until then opencode doesn't emit any events associated with the plugin that the terminal can recognize).

If you send a query and the chip still sticks around though, could you send me what your ~/.config/opencode/opencode.json file looks like? And could you also confirm if notifications are being correctly sent for your opencode sessions in Warp (meaning the plugin is installed correctly)? Thank you!

[gabszap]

Terminal commands work normally on my side. I tested with sleep and ping, and Warp notifications do appear (after setting “when a command takes longer than 1 second”).

However, I don’t receive any notifications related to opencode.

I also tried triggering permission prompts on purpose (e.g., reading files outside the workspace, writing to protected locations, running commands that require confirmation), but Warp didn’t show any notifications. Only opencode-notify worked correctly.

---

Here is my ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "experimental": {
    "quotaToast": {
      "enableToast": "true",
      "enabledProviders": ["openai", "copilot"],
      "minIntervalMs": 300000,
      "showSessionTokens": "true",
      "toastDurationMs": 10000
    }
  },
  "mcp": {
    "context7": {
      "enabled": true,
      "headers": {
        "CONTEXT7_API_KEY": "{env:CONTEXT7_API_KEY}"
      },
      "type": "remote",
      "url": "https://mcp.context7.com/mcp"
    }
  },
  "permission": {
    "bash": {
      "*": "ask",
      "Get-ChildItem *": "allow",
      "Select-Object *": "allow",
      "Select-String *": "allow",
      "Where-Object *": "allow",
      "bun *": "allow",
      "bun install *": "ask",
      "bunx ava *": "allow",
      "bunx tsc *": "allow",
      "bunx eslint *": "allow",
      "find *": "allow",
      "git branch *": "allow",
      "git checkout *": "ask",
      "git clean *": "ask",
      "git commit": "ask",
      "git commit *": "ask",
      "git diff *": "allow",
      "git fetch *": "allow",
      "git log *": "allow",
      "git merge *": "ask",
      "git push": "ask",
      "git push *": "ask",
      "git rebase *": "ask",
      "git remote *": "allow",
      "git reset *": "ask",
      "git restore *": "ask",
      "git show *": "allow",
      "git status *": "allow",
      "git switch *": "ask",
      "grep *": "allow",
      "ls *": "allow",
      "ls -la *": "allow",
      "mkdir *": "allow",
      "node -c *": "allow",
      "node -e *": "allow",
      "npm *": "allow",
      "npm install *": "ask",
      "npx tsc *": "allow",
      "pip *": "allow",
      "pip install *": "ask",
      "pip install -r *": "ask",
      "tsc *": "allow",
      "where *": "allow"
    }
  },
  "plugin": ["@slkiser/opencode-quota", "@warp-dot-dev/opencode-warp"]
}

---

Quick question:
Do opencode notifications show as native Warp notifications, or via something like SnoreToast?

opencode-notify also uses SnoreToast on Windows, so if Warp uses the same mechanism, that might explain why I don’t notice any difference between them.

---

Also, I attached the wrong screenshot before — this one shows the correct plugins.

---

Off-topic issues:

I’m not sure if this is a Warp bug or something on my side, but I’ve noticed a couple of other issues:

• Sometimes when I exit opencode, the terminal closes immediately
• In some cases, Warp itself crashes entirely (this has happened multiple times)
• It’s not possible to paste images into opencode through Warp (outside of Warp it works fine)

[kauebraghetto]

The notifications from OpenCode are not working for me either

[harryalbert]

Looks like the plugin is installed correctly, I think this might be a windows issue with the plugin.

@gabszap (or @kauebraghetto if you're also experiencing this issue on windows), could you try the fix in this branch and see if it works? Instructions on how to test are:

1. Clone the repo and check out the branch:

   git clone https://github.com/warpdotdev/opencode-warp.git
   cd opencode-warp
   git checkout harry/app-4096-fix-opencode-tty-output-on-windows

2. Install dependencies:

   npm install

3. Point your opencode.json at the local plugin source instead of the npm package. Replace:

"plugin": ["@warp-dot-dev/opencode-warp"]

with a file:// path to the local TypeScript entry point:

   "plugin": ["file:///C:/Users/<you>/opencode-warp/src/index.ts"]

4. Open Warp, run opencode, and send a query. Verify that:
   ◦ The setup chip disappears after the first message
   ◦ Warp notifications appear when OpenCode finishes a task or requests permission
5. When done, revert opencode.json back to "@warp-dot-dev/opencode-warp".

[gabszap]

I tested the branch on Windows, but it’s still not working on my side.

No notifications are received from the agent at all, and the setup chip still remains visible as if the plugin was not installed.

So unfortunately the issue still persists with this fix branch.

"plugin": [
    "@slkiser/opencode-quota",
    "file:///C:/Users/Me/Documents/GitHub/opencode-warp/src/index.ts"
  ]

[kauebraghetto]

Hi @harryalbert , I tested the fix branch on my setup and the issue still persists in both environments.

Environment:

• OS: Windows 11
• Warp: Latest
• OpenCode: 1.4.6

Steps taken:

1. Cloned the repo and checked out harry/app-4096-fix-opencode-tty-output-on-windows
2. Ran npm install
3. Updated ~/.config/opencode/opencode.json (located inside WSL at \\wsl.localhost\Ubuntu\home\kauea\.config\opencode) with:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["file:///mnt/c/Users/kauea/opencode-warp/src/index.ts"]
}

4. Restarted Warp and tested in two scenarios:
   • OpenCode running inside WSL2 (Ubuntu)
   • OpenCode running natively on Windows via PowerShell

Result: No Warp notifications appear in either scenario and the setup chip behavior remains unchanged. The fix does not seem to cover neither the WSL2 nor the native Windows PowerShell scenarios.

Note: the Warp plugin for Claude Code works fine on my setup — just mentioning to clarify that the issue is specific to the opencode-warp plugin, not a general Warp notification problem.