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

teams: manager conversation initialization, handle fallback, and approval posture inheritance

Cerrado
  • ¿Algo no está bien?
#1,551 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
backend, cli

Línea de trabajo

Read the manager initialization and registration paths under internal/session, then inspect internal/session/team_start.go and internal/session/consent.go. Trace how handles, approval posture, and consentRule formatting are passed during team_start. Done means fallback handles are registered, child meta.json inherits approval posture, and the consent card shows the full cost and lifecycle wording.

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

Descripción

area:session bug sev:serious
Summary

Team manager initialization fails to generate handles on untitled new conversations, omits approval posture inheritance during team_start, and renders incorrect consent card wording.

Items & Observed Behavior
  1. Empty handle on new top-level manager conversation: Creating a new top-level manager conversation via M leaves the conversation without a title until the first turn runs. Handle derivation falls back to empty, preventing global managers from routing messages to it via team_send.
  2. Approval posture not inherited in team_start: When a manager creates a sub-team with team_start, the new team manager's meta.json does not inherit the parent manager's "approval" posture, reverting instead to the profile default (e.g. ask).
  3. Consent card wording mismatch: The team_start consent card renders the literal rule word "default" instead of the cost warning clause ("a new conversation; it spends until it stops").
Expected Behavior
  • Untitled manager conversations should receive a deterministic fallback handle derived from role and creation timestamp.
  • Sub-teams spawned via team_start must inherit the initiating manager's approval posture unless explicitly overridden.
  • The consent card must display the full cost and lifecycle description rather than internal configuration keywords.
Root Cause / Location
  • internal/session: Manager handle derivation and teams.json registration.
  • internal/session/team_start.go: Missing posture propagation from caller session to child meta.json.
  • internal/session/consent.go: consentRule fallback formatting.

—
Drafted with CodeAF · reviewed and owned by the author

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.