Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

'Run this as a task on <model>' becomes a reading helper; chat misreports it

Offen
  • Stimmt etwas nicht?
#1,569 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
cli, testing-qa

Rechercherichtung

Start with internal/session/readhandoff.go, especially the hand-off admission around lines 150-160 and sweepTitle around lines 324-329, then reproduce the message using the isolated profile and Python repo described. Compare the resulting tasks.json and usage.jsonl with the chat report; done means the request produces a named task proposal or clear refusal, avoids unbranched edits, and reports the task's actual model and usage.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:session bug sev:critical

Seen on: dev 837b2b0.

Behaviour

Run this as a task on glm 5.3 flash: implement parse and humanize … made no proposal and no crew line. A ◆ reading: Run this as a task on glm 5.3 flash … helper ran on z-ai/glm-5.3 ($0.032) and edited durations.py in place (uncommitted, no branch). The chat then said Task ran on glm 5.3 flash … Time: 11 seconds. Cost: $0.055 (estimate $0.203), while glm-5.3-flash spent only $0.003 in that workspace. The same words in another window made a real task on kimi-k3.

A request for a task on a named model should produce a task proposal (or a clear refusal), and the chat's report of model, time and cost must match what actually ran.

Replication

  1. Build dev 837b2b0 (git checkout 837b2b0 && make build, binary bin/codeaf), or install the dev build with curl -fsSL https://agentfield.ai/get/devaf | bash.
  2. Use an isolated profile: export HOME=$(mktemp -d), export OPENROUTER_API_KEY, and keep the default model (~deepseek/deepseek-v4-flash-latest, crew on auto).
  3. On a busy machine set task.max_load to 0 (/settings, Tasks) so the busy-machine gate does not hold tasks.
  4. Make a small Python repo: R=$(mktemp -d) && cd "$R" && git init -q && printf 'def parse(s):\n raise NotImplementedError\n\ndef humanize(n):\n raise NotImplementedError\n' > durations.py && git add -A && git commit -qm init.
  5. codeaf, then send: Run this as a task on glm 5.3 flash: implement parse and humanize in durations.py (parse "1h30m" to seconds, humanize seconds back) and add tests.
  6. Look for a ◆ reading: row instead of a proposal card; read git status (edits in place, no branch) and compare the chat's Cost: line with codeaf logs for the workspace.

Evidence

  • Screen: ◆ reading: Run this as a task on glm 5.3 flash …; chat reply Task ran on glm 5.3 flash … Time: 11 seconds. Cost: $0.055 (estimate $0.203).
  • The session's tasks.json: node 1 titled reading: …, model z-ai/glm-5.3; usage.jsonl shows glm-5.3-flash at $0.003.
  • internal/session/readhandoff.go:150-160 (hand-off admission) and :324-329 (sweepTitle gives reading: <first line>).

Guessed cause

A guess from reading the code, not a confirmed diagnosis. As in the reading-helper issue filed beside this one: the read hand-off fires before propose_task, the quick task runs on the reader's model with a write-capable belt, and the chat's summary is composed by the model rather than from the helper's real model and cost.

Acceptance

  • e2e: the message above produces a task proposal whose card names glm-5.3-flash (or the chat refuses in one line); no file changes outside a task branch.
  • e2e: any cost or model the chat quotes for a task matches the task's usage rows.

Found while writing the public docs; manual text differences are in #1545.

🤖 Generated with Claude Code

Vorherrschende Sprache
Go
Sterne
115
Forks
14
Ø Merge
10 Std. 6 Min.
Gemergte PRs (30 T.)
223

Entwicklungsumgebung

Die Einrichtungsdateien dieses Projekts haben wir noch nicht geprüft. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Agent-Field/CodeAF

Alle Issues in Agent-Field/CodeAF

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.