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

senior-dev silently ignores --max-cost and other flags after the brief

Aberta
  • Algo errado?
#1,567 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
85/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
cli

Direção de pesquisa

Start with delegate.Parse in internal/delegate/cli.go:79-118 and the senior-dev synopsis in cmd/codeaf/carried.go:566. Reproduce the flags-after-brief command, then inspect how fs.Parse and fs.Args handle the remaining arguments. Done means the unit and e2e cases parse the caps and JSON flag correctly, or reject misplaced flags without running under default limits.

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

Descrição

area:headless bug sev:critical

Seen on: dev 837b2b0.

Behaviour

codeaf senior-dev "<brief>" --max-cost 0.5 --max-hours 0.3 --json ignores every flag after the brief. The header read up to $10.00 and 3h, the output was readable lines instead of JSON, and the exit was 0. The same flags placed before the brief work. A script that caps cost this way is not capped. Flags after the brief should either be parsed or refused with an error; they must never be silently dropped.

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 repo: R=$(mktemp -d) && cd "$R" && git init -q && printf 'package main\n\nfunc main() {}\n' > main.go && printf 'module demo\n\ngo 1.22\n' > go.mod && git add -A && git commit -qm init.
  5. Run codeaf senior-dev "add a README.md with one line" --max-cost 0.5 --max-hours 0.3 --json.
  6. Read the first lines: the header says up to $10.00 and 3h and the output is not JSON.
  7. Control: codeaf senior-dev --max-cost 0.5 --max-hours 0.3 --json "add a README.md with one line" shows the $0.50 cap and prints JSON.

Evidence

  • Header text up to $10.00 and 3h for the flags-after-brief form; the flags-first form honours the caps.
  • internal/delegate/cli.go:79-118: flag.NewFlagSet(...) then fs.Parse(rest); Go's flag stops at the first non-flag argument, and fs.Args() (line 118) carries --max-cost 0.5 ... into the brief.
  • cmd/codeaf/carried.go:73 calls delegate.Parse(program, args, ...); carried.go:566 documents the synopsis as "<brief>" [--dir dir] [--max-cost usd] [--max-hours h], that is, flags after the brief.

Guessed cause

A guess from reading the code, not a confirmed diagnosis. The parser uses Go's flag package, which stops at the first positional argument, and nothing checks the leftover arguments for flag-shaped words, although the documented synopsis puts the flags after the brief.

Acceptance

  • e2e: the flags-after-brief command above prints JSON and its header says up to $0.50; or it exits non-zero naming the misplaced flag. It never runs with the default cap.
  • Unit: delegate.Parse with ["brief", "--max-cost", "0.5"] yields max-cost=0.5 (or an error), never a brief that contains --max-cost.

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

🤖 Generated with Claude Code

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

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.