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

task countdown hint promises 0 waits, and in a headless run 0 starts immediately

Abierto Apto para principiantes
  • ¿Algo no está bien?
#1,367 0 comentarios 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
88/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, developer-experience

Línea de trabajo

Empieza en internal/config/settings.go:2298 y revisa internal/session/session.go:1806 para distinguir entre watched/headless. Añade una prueba para la sugerencia de cuenta atrás de la tarea, sin modificar internal/manual/chat/tasks.md. Se considera terminado cuando la sugerencia incluye la condición watched, coincide con tasks.md:1492 y la nueva prueba pasa.

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

Descripción

area:session bug sev:papercut

The defect is one string

The task countdown row's hint promises, unconditionally, that zero waits:

internal/config/settings.go:2298

"how many seconds a proposed task waits for you before it starts on its own. The countdown is your window to redirect it or wave it off, not a gate, 0 waits for your answer instead of starting. A change lands on the next session."

That promise holds only on a watched session. internal/session/session.go:1806 states the other half:

0 IS A CLOCK THAT IS OFF, the proposal waits for Agent.ResolveTask and nothing else, which is only a sentence a WATCHED session can honour: with nobody subscribed to the events (AskConsent false, or no turn hub), the deadline approves whatever this says, because a headless run has no one to wait for.

So on a headless run, zero does not wait for an answer. It approves immediately. The value a person types to make every proposal stop is the value that makes every proposal start.

Why this is the worst place for it

The surface closest to the decision is the one that is wrong. The hint is read at the moment the number is typed. The page a person would have to go looking for is already correct.

The manual is correct and MUST NOT be changed to match

internal/manual/chat/tasks.md scopes the promise properly in both places that tell a person to use zero:

  • :1492 "Use task.autoapprove_seconds in the Safety settings to give yourself a longer window, or set it to 0 so every watched proposal waits for you."
  • :1510 "Set task.autoapprove_seconds to 0 in Safety settings if every proposal on a watched session should wait until you answer."

Reconciling the two surfaces in the wrong direction would delete the only correct statement of the behaviour that exists. If the hint and the page disagree, the page wins.

Not live today, and the reason it is worth fixing anyway

DefaultTaskAutoApprove is 15 (settings.go:1429) and a persisted value is only taken when one is present (settings.go:4256), so nothing reaches zero by default. The hazard arrives the first time somebody types 0 meaning what the row told them it means.

Acceptance

  1. The hint carries the watched condition, in the shape tasks.md:1492 already uses.
  2. A test holds it. A promise in a help string has nothing mechanical behind it today, which is why the two surfaces were free to drift apart: nothing relates the string to the behaviour it describes.

Read at d91bb63ae.

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

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.