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

Manager tells the person it asked for approval when nobody was asked

Geschlossen
  • Stimmt etwas nicht?
#1,585 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@santoshkumarradha arbeitet bereits daran.

Seit 27.9.2026.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
72/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
backend, cli

Rechercherichtung

Start at internal/session/tools_team.go:107, where the team-start tool description says the person is always asked first. Reproduce the team_start flow under the default ◇ YOLO approvals and then under ◇ asks using the listed build and isolated-profile steps. Done means the YOLO reply does not claim approval was requested, while ◇ asks shows a card for each start.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:session bug sev:serious

Seen on: dev 837b2b0.

Behaviour

Under the default approvals (◇ YOLO), team_start runs without a card, yet the manager told the person the starts "asked you first for approval": The manager conversations are opening now (they asked you first for approval). The model should not claim a consent step that did not happen.

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; keep approvals on the default (◇ YOLO in the status line).
  5. On /teams make a team and press M; send the manager: Make a platform team with an api sub-team and an infra sub-team.
  6. Read the manager's reply: no card appeared, but the reply says approval was asked.

Evidence

  • Reply: The manager conversations are opening now (they asked you first for approval).; no consent card.
  • internal/session/tools_team.go:107: teamStartDescription = "Start a new member conversation in this team with a handle and a brief. The person is asked first. " ….

Guessed cause

A guess from reading the code, not a confirmed diagnosis. The tool description the model reads states that the person is always asked first; it should say the person is asked only when this conversation's approvals ask.

Acceptance

  • e2e: under ◇ YOLO, the reply above does not claim approval was asked; under ◇ asks, a card appears for each start.

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

🤖 Generated with Claude Code

Vorherrschende Sprache
Go
Sterne
115
Forks
14
Ø Merge
9 Std.
Gemergte PRs (30 T.)
232

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.