anomalyco / anomalyco/opencode

opencode web部署linux内网服务器,存在部分回答不进LLM,无回复的问题

Open
#38,268 2 comments 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Jul 22, 2026.

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

Description

Description
Image 该bug在localhost部署时不会出现,一切正常。我只在远程部署web服务时发现该bug(我自己可以100%复现)。 我访问http://192.168.xxx.xxx:5173/(服务器地址)可以正常访问,通常第一次提问是可以正常回复的,当我在第3次提问时,大概率就会出现大模型不回复的问题(opencode提供的免费模型,和我内网部署的小模型都不回复)。

opencode版本:
我l.17.20源代码安装运行,以及npm latest(1.18.1)都存在这个问题

当正常回复时,日志如下:
timestamp=2026-07-21T09:04:58.272Z level=INFO run=c51c8138 message=loop session.id=ses_07c34971fffeVQtR7uylyHQJzb step=0
timestamp=2026-07-21T09:04:58.328Z level=INFO run=c51c8138 message=process session.id=ses_07c34971fffeVQtR7uylyHQJzb messageID=msg_f83ebd3a3001XGuzStuQHPPJNG
timestamp=2026-07-21T09:04:58.329Z level=INFO run=c51c8138 message=stream providerID=fm-local modelID=Qwen3.6-35B-A3B session.id=ses_07c34971fffeVQtR7uylyHQJzb small=false agent=build mode=primary
timestamp=2026-07-21T09:04:58.345Z level=INFO run=c51c8138 message="llm runtime selected" llm.runtime=ai-sdk llm.provider=fm-local llm.model=Qwen3.6-35B-A3B
timestamp=2026-07-21T09:04:59.910Z level=INFO run=c51c8138 message=loop session.id=ses_07c34971fffeVQtR7uylyHQJzb step=1
timestamp=2026-07-21T09:04:59.913Z level=INFO run=c51c8138 message="exiting loop" session.id=ses_07c34971fffeVQtR7uylyHQJzb

当我发了消息,opencode web没回我时,日志会打印:
timestamp=2026-07-21T09:03:40.066Z level=INFO run=c51c8138 message=loop session.id=ses_07c34971fffeVQtR7uylyHQJzb step=0
timestamp=2026-07-21T09:03:40.068Z level=INFO run=c51c8138 message="exiting loop" session.id=ses_07c34971fffeVQtR7uylyHQJzb

Plugins

No response

OpenCode version

1.18.4

Steps to reproduce
  1. opencode web
  2. 访问网页
  3. 选择项目,新建会话
  4. 输入“你好”,此时第一次提问可以收到回答
  5. 再次输入“你好”,大模型不再回答(我能确定内网模型可以正常调用)
Screenshot and/or share link
Image
Operating System

Ubuntu 24.04.4 LTS(docker container) and Ubuntu 22.04.4 LTS(host machine)

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.