[Bug]: Commit & push doesn't work with opencode

[razzeee]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Setup only opencode
2. Do some changes
3. Try to use the "Commit & push" button
4. It errors

Expected behavior

It shouldn't error and generate a message

Actual behavior

Text generation failed in generateCommitMessage: OpenCode session.prompt request failed.

Impact

Major degradation or frequent failure

Version or commit

0.0.40

Environment

Fedora Linux

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[juliusmarminge]

Thanks for the report — this looks like a real OpenCode commit-message generation failure, not a web-button bug.

What we know

The toast text is produced only in OpenCodeTextGeneration when the SDK session.prompt call throws after a successful session.create:

Text generation failed in generateCommitMessage: OpenCode session.prompt request failed.

That is a different failure than:

• [Bug]: OpenCode returns "no structured output" error during commit message generation #2199 (OpenCode returned no structured output) — fixed in fix(server): handle OpenCode text response format in commit message g… #2202
• [Bug]: GIT Text generation failed in generateCommitMessage. When Codex not installed. #5182 (Codex spawn / default writer) — different error; setting Settings → Source Control → Source control writer model was the workaround there
• [Bug]: Thread title and branch-name generation fail silently when the text generation provider is unhealthy #5359 (silent title / branch generation) — same text-gen family, different surface

Commit & push (git.runStackedAction → generateCommitMessage) has no fallback. If generation throws, the whole commit/push is aborted.

Likely cause

Chat already talks to OpenCode with session.promptAsync. Commit/PR/title/branch generation still uses blocking session.prompt on a throw-on-error SDK client (@opencode-ai/sdk@1.15.13 in 0.0.40). Newer OpenCode (1.17+ / v2) changed that prompt endpoint so it no longer returns a completed message body. A parse/schema/HTTP throw then gets rewritten to this generic toast, hiding the real cause. Official OpenCode 2 support is still open (#8207).

Workaround

Type a commit message in the git dialog before Commit & push — a non-empty custom message skips generation.

Ask

Please add:

1. opencode --version (and whether this is OpenCode 1 or 2)
2. Whether OpenCode chat still works in the same setup
3. The matching server log line around the failure (the SDK cause is stored but not shown in the toast)

Next

Treat as accepted. Fix belongs in apps/server/src/textGeneration/OpenCodeTextGeneration.ts: align with the chat adapter’s promptAsync + wait path, and surface the SDK/HTTP error in the toast.

[razzeee]

❯ opencode --version
1.18.29

1. It's opencode 1
2. Regular chat works with github-copilot/gpt-5.6-sol or similar

created ... title="T3 Code generateCommitMessage"
ERROR ... ProviderModelNotFoundError:
Model not found: openai/gpt-5.
Did you mean: gpt-5, gpt-5.4, gpt-5.6?

I do not have an openai subscription on this system (or ever had)
Settings show Haiku to be configured, but I don't remember doing that or it was ages ago. Guess this might be a different setting anyway.

[Destreyf]

@razzeee do you use opencode go or zen, i have seen a similar error when the model is disabled?

The model definition openai/gpt-5 would definitely point to an opanai key/sub of some sort typically.

The "Text generation model" I think is what was used for generating thread titles and commit messages depending on how it's configured at the bottom of the "Source Control" settings page, which by default falls back to the global text generation model.

[razzeee]

I don't use go or zen.

[Destreyf]

If you modify the source control writer model do you get the same error?

[razzeee]

Works with that enabled

[ciphrnotfound]

I’ll take this. I’ll keep it scoped to OpenCodeTextGeneration: align commit-message generation with the existing promptAsync + wait flow and improve error propagation, with focused regression coverage.