anomalyco / anomalyco/opencode

OpenCode App sends periodic background requests to grok-4.3 via custom OpenAI-compatible provider (no such model in config)

Open
#50,059 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

OpenCode Desktop 1.18.31 (macOS 15.8) sends a background request with model=grok-4.3 roughly every 15-35 minutes to my custom OpenAI-compatible provider (baseURL pointing to a self-hosted gateway, provider package @ai-sdk/openai-compatible). The requests have an empty body (0 input / 0 output tokens), reasoning_effort=medium, no user session involved.

Facts:

  • opencode.jsonc defines only grok-4.6 for this provider block; the string grok-4.3 appears nowhere in my config, app logs (main.log/renderer.log), or active sessions (no new sessions for weeks).
  • Root model is a Gemini model, small_model is set to a Gemini model - title/summary paths should not touch Grok.
  • Confirmed at network level (Little Snitch traffic log): the only process opening connections to the gateway is OpenCode Helper; requests go over a long-lived keep-alive connection, cadence is clock-precise (same second each tick).
  • Restarting OpenCode App does not stop it - ticks resume with the new process, so it looks like a built-in background mechanism (healthcheck/warmup?) using a hardcoded/stale default model name (grok-4.3 was xAI's default in the past), not a stuck worker.
  • On the gateway side each tick fails with 402 (empty xAI balance) - pure log noise, but it means the app is polling a model the user never configured.

Expected: background mechanism should use a configured model (e.g. small_model) or not fire against custom providers at all; it should never reference a model ID absent from config/catalog.

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.

Research direction

No source file or test is named. Start by tracing the background request mechanism and searching for the grok-4.3 model string or provider polling path, then reproduce the periodic request with a custom OpenAI-compatible provider. Done means no request targets a model absent from configuration, or the mechanism skips custom providers.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.