Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Page Stop shows an acceptance card and keeps spending

Aberta
  • Algo errado?
#1,350 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
68/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
cli, testing-qa

Direção de pesquisa

Start at app.taskPlanStopTaken in internal/tui3/taskplan.go, then follow Agent.CancelWithReason in internal/session/cancel.go and Agent.settleUnfinished in internal/session/task_run.go. Run the page-stop reproduction in tmux and inspect the e2e and unit acceptance requirements. Done means stopped runs settle once, reject checking, acceptance, and resume, use no new model resources, and the manual and change-entry updates are present.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:chat area:session bug sev:serious

What happened

NEW PRESENTATION defect seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21. Lane A1, item A1-05, stopped a running task from its page. The row said slow counting loop stopped, but the page then showed:

a accept  n not right  s tell it
Working checking

Tokens, cache, and spend continued rising. On v0.3.0 (9258f7052), post-stop spending and automatic resumption were already present, so that part is PRE-EXISTING; the acceptance card after page Stop is new.

Replication

Deterministic (no model).

No no-model reproduction is established; lane A1 reproduced the extra presentation and spend with a live run.

Field (real models).

Set OPENROUTER_API_KEY, then start a fresh local chat:

root="$(mktemp -d)"; export CODEAF_HOME="$root/home"; repo="$root/repo"
mkdir -p "$CODEAF_HOME" "$repo" && git -C "$repo" init -q
git -C "$repo" -c user.name=Test -c [email protected] commit --allow-empty -m base
cd "$repo" && codeaf chat --no-host --yolo --model deepseek/deepseek-v4-flash

Enter /task count slowly from 1 to 2000, sleeping one second between numbers, open its page, choose Stop, and watch the status and spend for 30 seconds. Today stopped is followed by a accept n not right s tell it, Working checking, and rising spend.
Allow about three minutes and $0.05. The v0.3.0 control uses the same steps: it may keep spending after stop, but does not show the acceptance card.

Where

The page-stop and settlement seams are app.taskPlanStopTaken in internal/tui3/taskplan.go, Agent.CancelWithReason in internal/session/cancel.go, and Agent.settleUnfinished in internal/session/task_run.go. The evidence does not establish which transition emits the extra turn.

The fix

Page Stop is terminal for that run. Once the row says stopped, do not open a accept n not right s tell it, do not enter Working checking, do not automatically resume, and stop new model usage for the run.

Acceptance

  • e2e: Through a run page in tmux codeaf chat --no-host, stop a stub long-running task and assert stopped appears while a accept n not right s tell it and Working checking never appear, then exit 0.
  • e2e: Through the same page with metered fake receipts, assert token, cache, and spend fields remain unchanged for ten seconds after stopped.
  • Unit: Every transition caused by taskPlanStopTaken settles unfinished work once and rejects later checking, acceptance, or resume transitions for that run.
  • The manual page internal/manual/chat/task-controls.md says page Stop is terminal, and the change entry's invalidates names the old belief that a stopped run could still enter checking or acceptance.

Filed from the 2026-09-21 staging verification of 17ae56d34; the lane reports, frames and e2e logs are in the owner's handoff folder for this promotion.

Linguagem predominante
Go
Estrelas
115
Forks
14
Merge médio
9h 37min
PRs com merge (30d)
755

Preparar o ambiente

Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Agent-Field/CodeAF

Todas as issues de Agent-Field/CodeAF

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.