OpenCode GitHub Action hangs indefinitely at “Sending message to opencode…” (no output)

[enact-on]

Description

OpenCode GitHub Action starts successfully (installs OpenCode, configures git, asserts permissions, creates session + branch), but consistently hangs at:

Sending message to opencode...

Workflow does not complete and no agent response/output is produced.

Plugins

z.ai

OpenCode version

1.1.31

Steps to reproduce

GitHub Actions runner: ubuntu-latest

Runner version: 2.331.0

OpenCode version: 1.1.31 (installed via curl -fsSL https://opencode.ai/install | bash)

Provider: ZHIPU

Model: zai/glm-4.7

Agent: orchestrator

Trigger: issues: opened/edited

Screenshot and/or share link

Operating System

github runner ubuntu

Terminal

git bash

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• OpenCode Github Agent Stuck! #4672: OpenCode Github Agent Stuck! - Similar symptoms with agent hanging at "Sending message to opencode..."
• opencode run hangs forever on API errors (breaks CLI/automation integrations) #8203: opencode run hangs forever on API errors (breaks CLI/automation integrations) - Related issue where OpenCode hangs on API errors instead of failing fast
• ProviderModelNotFoundError for custom provider in GitHub Action (worked until 07 Jan) #7958: ProviderModelNotFoundError for custom provider in GitHub Action - Similar GitHub Action failure with the zhipuai provider (same config you're using)
• Opencode quits/hangs when models.dev not responding #9493: Opencode quits/hangs when models.dev not responding - Related hanging issue when external services are unavailable

Feel free to ignore if none of these address your specific case.

[enact-on]

Is this an issue?

github workflow uses client.session.chat

opencode/github/index.ts

Line 614 in 9fc182b

const chat = await client.session.chat<true>({

but its not listed here

https://opencode.ai/docs/sdk/#sessions

[github-actions]

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.