Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte Adaptée aux débutants
  • Quelque chose ne va pas ?
#1,367 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
88/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
go
Domaine
cli, developer-experience

Piste de recherche

Commencez par internal/config/settings.go:2298 et examinez internal/session/session.go:1806 pour la distinction entre watched/headless. Ajoutez un test pour l'indication du compte à rebours de la tâche, en laissant internal/manual/chat/tasks.md inchangé. Le travail est terminé lorsque l'indication inclut la condition watched, correspond à tasks.md:1492 et que le nouveau test passe.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
9 h 38 min
PR mergées (30 j)
749

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.