anomalyco / anomalyco/opencode

Zen: x-preview-f-free fails 100% of attempts from one project directory while sibling directories pass simultaneously

Open
#44,885 1 comment 1 reaction 1 assignee View on GitHub

@fwang is already working on this.

Since Aug 25, 2026.

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

Description

Description

Since ~2026-08-25 01:05 UTC, every request to x-preview-f-free (zen/v1) launched from one specific project directory fails within ~4-8 s with:
503 {"error":{"type":"server_error","message":"Error from provider (Console): Upstream request failed: Endpoint is unavailable."}}
while other directories on the same machine/key/binary pass intermittently during the same minutes.

One day of data, same key/machine/binary, variant max:

dir attempts pass fail
X 302 227 75
Y 164 106 58
Z (affected) 15 0 15

A brand-new session in Z failed on its first try while X passed repeatedly at overlapping timestamps. Sessions in Z on another zen model streamed immediately; switching back resumed instant failures. Z worked normally on this model ~10 h before onset - no local files changed in between.

Suspect something assembled from Z's project context (system prompt / project instructions) trips the Ox Alpha upstream deterministically, stacked on top of the intermittent flakiness tracked in #44300. Fresh-session control rules out sticky-hash luck.

Plugins

slim-tools.ts, caveman, ponytail.mjs (global)

OpenCode version

1.18.21

Steps to reproduce

Not reproducible on demand outside the affected directory - observational over 481 requests:

  1. During the degraded window, send single-turn messages from new sessions in different local directories on x-preview-f-free.
  2. Affected directory fails every attempt; others fail intermittently only.
  3. Switching the affected directory's sessions to another zen model streams immediately; switching back re-fails instantly.
Operating System

Windows 11 x64

Terminal

Windows Terminal

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.