Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#1,591 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 44 min
PR fusionados (30 d)
766

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.