I've been doing something pretty similar, except instead of having a persistent opencode server, I've been using this workflow that runs opencode inside of the Forgejo action runners:

https://codeberg.org/dragonfyre13/forgejo-opencode

Still tinkering with it, but the gist is that I can invoke Opencode with /oc inside of an Forgejo issue, then it will come back with a PR for me to review.

Nice! I've done that with Claude Code + Forgejo but as a small separate app to run Claude in Docker: https://github.com/smithy-ai/smithy-ai