Bug: Plan approval in autopilot+fleet mode triggers execution with fleet dispatch ordering mismatch
- Linguagem predominante
- Shell
- Estrelas
- 11.2k
- Forks
- 1.9k
- Merge médio
- 14h 16min
- PRs com merge (30d)
- 6
Descrição
## Description
When approving a plan in plan mode while using autopilot+fleet, the plan approval immediately triggers execution AND fleet agent dispatch simultaneously. The "Queued (1)" and "Fleet deployed" messages appear while the main agent is still "Analyzing bugs and planning fixes," suggesting a sequencing/ordering issue between the main agent's work and fleet dispatch.
## Steps to Reproduce
1. Enter plan mode and create a plan (e.g., with multiple bugs/features)
2. Switch to autopilot+fleet mode
3. Copilot recommends committing to the plan with autopilot+fleet
4. Approve/select that recommendation
## Expected Behavior
Plan approval should properly sequence execution — the main agent's analysis should be coordinated with fleet agent dispatch, not race against it.
## Actual Behavior
Fleet dispatch ("Queued (1)", "Fleet deployed") fires concurrently with the main agent beginning its "Analyzing bugs and planning fixes" phase. This ordering mismatch suggests the fleet agents are dispatched before the main agent has finished planning/coordinating the work.
## Screenshot
*(Screenshot shows: Plan approved -> "Analyzing bugs and planning fixes" starts -> "Queued (1)" / "Fleet deployed" messages appear simultaneously)*
## Environment
- OS: Windows
- Copilot CLI version: latest (as of April 2026)
- Mode: Autopilot + Fleet (experimental)
## Additional Context
Also submitted private feedback via the `/feedback` command for internal tracking.
Guia de contribuição
Direção de pesquisa
Comece reproduzindo o fluxo de aprovação do plano no Windows autopilot+fleet mode e rastreie a transição da aprovação para a fase de planejamento do agente principal e o dispatch da frota. Compare a ordem dessas operações e identifique onde o dispatch é acionado. Considera-se concluído quando o deployment da frota é coordenado com o planejamento do agente principal, em vez de ocorrer de forma concorrente, e as mensagens de status reportadas aparecem na sequência correta.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- shell
- Domínio
- cli
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 45/100