Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

session-flow: spawned workers stall waiting on their own background work

Aperta
#6,413 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell

Direzione di ricerca

Start from /session-flow:orchestrate imperative 4 and how orchestrate worker builds briefs, then find where dispatching skills inject waiting/background-job rules. Trace the harness notice "waiting on its own background work" and any coordinator SendMessage/poll path. Done when workers always get a bounded foreground-poll (or auto-nudge) so they do not end a turn waiting on their own background job, without relying on the coordinator to paste the rule.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-human needs-triage

Problem

In the 2026-10-04 CI-performance session, spawned general-purpose workers ended their turn to "wait on background work" five separate times: a flaky-test fixer, the standards merge driver, the ci-workflows/medley driver, and the dotfiles/provisioning worker (twice). The harness then reported "waiting on its own background work". Nothing notifies the worker when that work finishes, so each one sat idle until the coordinator sent a SendMessage telling it to poll in the foreground.

/session-flow:orchestrate imperative 4 already says a background command is not a wait. But that text reaches a worker only if the coordinator pastes it into the brief, and these briefs did not carry it.

Ask

Make the rule reach workers without depending on the coordinator's memory. For example:

  • a short "waiting" clause that orchestrate worker export always includes and that dispatching skills inject into every brief: poll in the foreground with a bounded loop, or return what you have; never end the turn to wait on your own background job;
  • and/or a coordinator-side check that turns the harness's "waiting on its own background work" notice into an automatic poll-in-foreground nudge.

Evidence

Session dba79e68-af19-4ecc-a0ce-69d8b1dbefbb: five task notifications reading "This agent has not reported yet: it is waiting on its own background work", each cleared by a manual SendMessage.

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
5h 15m
PR unite (30g)
833

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.