anomalyco / anomalyco/opencode

OpenCode Go: Error 400 "Input text data may contain inappropriate content."

Open
#46,561 0 comments 0 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Sep 1, 2026.

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

Description

Description

When doing agentic workflows with an e-mail client project, I get the following error that flat-out prevents all work:

Error from provider (Console Go): Upstream request failed: [data_inspection_failed] <400> InternalError.Algo.DataInspectionFailed: Input text data may contain inappropriate content.

I am at a loss as to what could be triggering it. It seems to be completely erroneous. The project in question does not contain any:

  • Pornographic content or otherwise sexually suggestive content
  • Decompiled proprietary software; all source code is original
  • References to content that might be considered illegal or even just controversial in the United States

It is a completely mundane e-mail client being built in C++.

No more "inappropriate content" is detected after summarising a session and continuing from there, but it is twice that I have gotten this error in the middle of the agent writing C++ code. As such, I am effectively forced to monitor the progress at all times in case the OpenCode Go infrastructure suddenly decides that a request contains "inappropriate content".

In its current form, if this is not fixed, the OpenCode Go subscription appears unusable in production.

Plugins

N/A

OpenCode version

N/A

Steps to reproduce
  1. Purchase OpenCode Go subscrption
  2. Start software development project with Qwen 3.8 Flash or some other model
Screenshot and/or share link
Image
Operating System

Arch Linux

Terminal

Alacritty

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.