agent_send reply mishandles parallel and chain background lanes

Chiusa
  • Qualcosa non va?
#183 2 commenti 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
45/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend-api-design

Direzione di ricerca

The issue is in the agent_send reply handling for parallel and chain background lanes. Look at the code that processes replies for background lanes, likely in the agent or session management modules. The fix needs to ensure replies continue the existing transcript and are delivered to all child sessions in a parallel lane. Start by examining the tests mentioned to understand the expected behavior and the current failure.

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

Descrizione

area/agent bug
What happened?

agent_send replies do not behave correctly for multi-task background lanes.

For a completed parallel or chain lane, reply restarts the lane with the original tasks/chain still present, so the new reply prompt is ignored by mode selection and the original work runs again. For a running parallel lane, reply only targets the base sessionId, so sibling child sessions such as sessionId-1 do not receive it.

This conflicts with the documented agent_send behavior that replies continue the lane's existing transcript. I reproduced both cases on clean main @ adcf37b in core subagent tests, without external extensions. I have a local fix and regression tests ready and would like to submit a PR.

Steps to reproduce
  1. Start a background parallel lane: 
    {
  "tasks": [
    { "agent": "general", "task": "A" },
    { "agent": "general", "task": "B" }
  ],
  "run_in_background": true,
  "alias": "lane"
}
  2. Wait for it to complete.
  3. Send agent_send with action: "reply" and prompt C.
  4. The original A/B tasks run again; C is not delivered as the new turn.
  5. The same completed-lane behavior reproduces with chain.
  6. While a parallel lane is still running, a reply reaches the base child but not sibling sessionId-N children.
Expected behavior

A reply should continue the existing lane transcript with the new prompt, preserve the lane topology, and not silently rerun the original prompt. Running parallel replies should not be delivered to only part of the lane.

Version

main @ adcf37b / @step-harness/coding-agent 0.84.4

Lingua principale
TypeScript
Stelle
1k
Fork
71
Merge medio
13h 14m
PR unite (30g)
66

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 stepfun-ai/Step-Code

Tutte le issue di stepfun-ai/Step-Code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.