agent_send reply mishandles parallel and chain background lanes

Fermée
  • Quelque chose ne va pas ?
#183 2 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é
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
typescript
Domaine
backend-api-design

Piste de recherche

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.

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

Description

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

Langage dominant
TypeScript
Étoiles
1k
Forks
68
Merge moyen
13 h 14 min
PR mergées (30 j)
66

Préparer son environnement

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

Toutes les issues de stepfun-ai/Step-Code

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

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