microsoft / microsoft/vscode

"Fleet deployed" shows as user message

Open
#335,172 0 comments 0 reactions 1 assignee Claimed by @DonJayamanne View on GitHub
agent-host copilot-cli-agent
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

Image

Not sure how we are supposed to handle this, but there is more code with special handling for /fleet than I expected. In events.jsonl I see this

```
{"type":"user.message","data":{"content":"Fleet deployed","transformedContent":"2026-09-02T11:02:45.743-07:00\n\nYou are now in fleet mode. Dispatch sub-agents (via the task tool) in parallel to do the work.\n\n**Getting Started**\n1. Check for existing todos: `SELECT id, title, status FROM todos WHERE status != 'done'`\n2. If todos exist, dispatch them in parallel (respecting dependencies)\n3. If no todos exist, help decompose the work into todos first. Try to structure todos to minimize dependencies and maximize parallel execution.\n\n**Parallel Execution**\n- Dispatch independent todos simultaneously\n- Never dispatch just a single background subagent. Prefer one sync subagent, or better, prefer to efficiently dispatch multiple background subagents in the same turn.\n- Only serialize todos with true dependencies (check todo_deps)\n- Query ready todos: `SELECT * FROM todos WHERE status = 'pending' AND id NOT IN (SELECT todo_id FROM todo_deps td JOIN todos t ON td.depends_on = t.id WHERE t.status != 'done')`\n\n**Sub-Agent Instructions**\nWhen dispatching a sub-agent, include these instructions in your prompt:\n1. Update the todo status when finished:\n - Success: `UPDATE todos SET status = 'done' WHERE id = ''`\n - Blocked: `UPDATE todos SET status = 'blocked' WHERE id = ''`\n2. Always return a response summarizing:\n - What was completed\n - Whether the todo is fully done or needs more work\n - Any blockers or questions that need resolution\n\n**Coordination**\n- After sub-agents return, check todo status in SQL (source of truth)\n- If status is still 'in_progress', the sub-agent may have failed to update - investigate\n- Use the sub-agent's response to understand context, but trust SQL for status\n\n**After Sub-Agents Complete**\n- Check the work done by sub-agents and validate the original request is fully satisfied\n- Ensure the work done by sub-agents (both implementation and testing) is sensible, robust, and handles edge cases, not just the happy path\n- If the original request is not fully satisfied, decompose remaining work into new todos and dispatch more sub-agents as needed\n\nNow proceed with the user's request using fleet mode.\n\n\nConsider updating plan.md to reflect current progress and next steps.\n\n\nAvailable tables: todos, todo_deps\n\n\n\nTodos: 18 done (18 total)\nUse sql tool to query ready todos and update status as you work.\n\n","supportedNativeDocumentMimeTypes":[],"agentMode":"autopilot","delivery":"queued","interactionId":"263c9f8e-e48b-4fc2-9bdc-604d8458b039","turnId":"0","parentAgentTaskId":"6d7ce70e-c967-4ec9-8a0b-ea9c4979dcf9"},"id":"058541b1-f51e-4cdf-8ac9-ff5160bf9d67","timestamp":"2026-09-02T18:02:45.744Z","parentId":"f841fceb-5121-4c40-9141-8cf729ca1b37"}
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.