Plugin no works with Opencode Server mode

[isturiz]

I usually work in containers with the Opencode server: https://opencode.ai/docs/server/

Locally, with the Opencode server on my machine, it works perfectly, but when I connect to the container from the host (host acting like a client) notifications don't work.

I understood that this probably is not about the plugin, but if you know how to solve this, I appreciate it.

Term: Kitty
OS: macOS Tahoe
Opencode version: 1.2.24
Plugin version (opencode-notifier): 0.1.30

[mohak34]

Hey @isturiz, since the plugin runs inside the OpenCode process and in your setup that process is on the container, there's is currently no way for it to fire local notifications on your host machine. It can only fire the notifications in the container where the opencode server is running in. With the current architecture of the plugin, there doesn't seem to be a simple way to implement anything but if I find anything that could help with this in the future, I'll let you know.

[isturiz]

Thank you so much! The plugin is amazing.

If I have some time, I'll try to make a PR for that.

[rijuyuezhu]

Hi @isturiz, I encountered a similar issue in #62, where I wanted to add desktop notifications for the opencode attach TUI of an opencode server, so that I could interrupt the TUI without disrupting the agent loop. My solution is as follows:

Solution 1. Use the website to connect to the server

The opencode website connection provides native notifications.

Solution 2. Add a ref-count for TUI launch

For my local-to-local scenario, I used an alias for opencode attach that creates a ref-count file. Additionally, I wrote a server-side plugin to check if the valid ref-count number is greater than zero; if so, the plugin triggers notify-send. More details are available at https://github.com/rijuyuezhu/opencode_notify_attach.

For your container-to-host situation, I believe it would be suitable to adapt my plugin with the following modifications:

1. Mount ~/.local/state/opencode-notify-attach to the container.
2. Replace notify-send in my plugin with a network request to a relayer on the host that executes notify-send instead.

Alternatively, you could develop a container-to-host RPC to handle both functionalities above. Vibe-coding such a project is quick—give it a try!

[isturiz]

Hi @rijuyuezhu, I will try your solution.

Thanks for doc the solution for my use case, I really appreciate that.

Btw, why open a new project instead make a PR here? Just curiosity

[rijuyuezhu]

Hi @isturiz. My workaround is quite dirty. It can be seen as a 'downstream' of opencode-notifier (it can be implemented using the custom command functionality in this plugin). I did not implement in this manner because I was seeking a quick-and-dirty prototype.

[rijuyuezhu]

Seems that mohak34/opencode-notifier works for such opencode serve + opencode attach mode in the latest opencode release? @isturiz . Maybe a upstream change helps us!

[isturiz]

@rijuyuezhu Are you sure? I tried, and it doesn't work for me. How do you do it?

versions:

• Opencode 1.4.0

• opencode-notifier 0.2.1

[winstern1998-commits]

@rijuyuezhu Hi Wenrui, I believe this is a common need—many people use the opencode server inside a container and need to expose the port for access from the web, Windows desktop clients, and so on. If you could submit this plugin as a PR and have it merged, the project would gain a practical feature. Honestly, I’m actually looking forward to it~