Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

A task cannot be sent to a custom provider's model: the task catalog never lists it

未关闭
#1,414 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@AbirAbbas 已经在做这个了。

开始于 2026年9月23日。

评估

这个 Issue 还没有评估数据。

描述

area:session bug sev:serious

What happened

A conversation running on a custom OpenAI-compatible connection (model_sources, written: local, address http://127.0.0.1:8317/v1) talks to its local model with no trouble, and the runner is up and lists that model. Asking for a task on the same model is refused: "no model here is called <local model> — did you mean <three cloud model ids>? Name one of those, or leave model out to run on <another cloud model>."

Every suggestion and the fallback are cloud models. There is no spelling of the local model the door will accept, so a task from a locally-backed conversation always runs on a billed cloud model or not at all.

Where

propose_task's model is resolved by resolveTaskModel against Config.TaskModels (internal/session/taskmodel.go). That list is built by v3TaskModels in cmd/codeaf/chatv3.go, which takes tui3.ChatModels(v3Models(models)) — the chat catalog. The custom source's models are not in it, even though the conversation's own model comes from that source.

The refusal is taskModelUnknown: zero candidates against a non-empty list. When the list is warming and returns nil, the same code takes the named model as written and lets the provider answer for it, so the failure only appears once the catalog has loaded.

Not specific to one branch

v3TaskModels is byte-identical on origin/main and origin/santos/dev2 (git diff shows nothing in it), and the running binary that reproduced it (codeaf 80bdef3, built 2026-09-23 13:47) is an ancestor of santos/dev2. Whatever fixes it belongs on the line that lands, not on a side branch.

Acceptance

  • A task proposal naming a model the custom connection serves resolves to that model and runs on it, the way the conversation already does.
  • A model the connection does not serve is still refused, with the connection's own models among the suggestions rather than only the cloud catalog.
  • A conversation on a cloud model is unchanged: naming an unknown id is still refused, and an empty model still falls back as it does today.

Reproduced 2026-09-23 on darwin/arm64 against the local runner at 127.0.0.1:8317, which was listing the conversation's model at the time.

主要语言
Go
星标
115
派生
14
平均合并
9 小时 38 分钟
30 天内合并 PR
749

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。