anomalyco / anomalyco/opencode

AI_APICallError should be communicated via ACP

Open
#42,827 2 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 15, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

It looks like some errors (ex https://github.com/xenodium/agent-shell/issues/774) are not communicated via the ACP protocol and are only communicated via stderr. Could these errors be communicated via ACP as well?

Plugins

No response

OpenCode version

1.18.18

Steps to reproduce
  1. Hit your rate limit on Big Pickle.
  2. Note that the log shows "stream error"
  3. Note that an ACP consumer like agent-shell does not see the end of processing.

From notices that agent-shell collects:

timestamp=2026-08-15T22:01:13.530Z level=ERROR run=4ae39ca7 message="stream error" providerID=opencode modelID=big-pickle session.id=ses_ff88ee9f8ffefmM0eoWz1wh4pG small=false agent=build mode=primary error.error="AI_APICallError: Rate limit exceeded. Please try again later."
timestamp=2026-08-15T22:01:19.399Z level=ERROR run=4ae39ca7 message="stream error" providerID=opencode modelID=big-pickle session.id=ses_ff88ee9f8ffefmM0eoWz1wh4pG small=true agent=title mode=primary error.error="AI_RetryError: Failed after 3 attempts. Last error: Rate limit exceeded. Please try again later."
Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.