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

Sub-team manager naming its own team in team_post gets a misleading refusal

Aberta
  • Algo errado?
#1,591 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
72/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
tooling

Direção de pesquisa

Start in internal/session/tools_team.go:185-201 and trace how teamTarget matches the requested team and builds its refusal. Reproduce the beta manager's team_post call from the issue using the documented dev build and isolated profile. Done means the e2e call identifies beta as the caller's own team and product as the correct target.

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

Descrição

area:session bug sev:papercut

Seen on: dev 837b2b0.

Behaviour

A sub-team manager (@betalead, manager of beta, member of product) called team_post {"to":"manager","team":"beta"} and was told There is no one team called "beta" here. Yours are: "product"., although beta exists and it runs it. The retry with team: "product" worked. The refusal should explain the rule, for example you manage "beta"; team_post is for the team above you, "product".

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. cd $(mktemp -d) && git init -q && codeaf; make a team product with a manager, and ask it to start a sub-team beta with a manager.
  5. Ask the beta manager: Post to your manager with team_post, naming team beta.

Evidence

  • Tool result: There is no one team called "beta" here. Yours are: "product".
  • internal/session/tools_team.go:185-201: the name is matched only against fits (the member roles), and the refusal lists only those.

Guessed cause

A guess from reading the code, not a confirmed diagnosis. teamTarget filters to member roles before matching the name, so a team the caller manages reads as unknown.

Acceptance

  • e2e: the call above returns a refusal that names beta as the caller's own team and product as the right target.

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 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.