Subagent Briefs Are Live in DeerDawn

AI coding agents are getting better at splitting work across subagents. The handoff is still the weak point. A worker either receives too little context and repeats discovery, or receives the entire conversation and burns tokens sorting through information it does not need.

A brief for one job

The new build_subagent_brief tool turns DeerDawn’s main project brief into a smaller handoff for one concrete assignment. The orchestrator provides the task, role, deliverable, success criteria, focus paths, and token budget. DeerDawn adds the most relevant project decisions, constraints, debugging notes, commands, and known files.

Built for isolated subagents

Each generated brief starts with a stable DeerDawn marker and ends with an explicit return contract. That lets an orchestrator launch the worker without forwarding the whole conversation. The worker knows what to change, what success means, where to work, what to avoid, how to verify the result, and what to report back.

Token efficient by design

Subagent briefs are deterministic and token-budgeted. DeerDawn ranks project-scoped context, removes duplicate paths, redacts secrets, neutralizes prompt-injection-like text, and reports how much source material was omitted. The first release defaults to a roughly 250-token package and supports budgets from 120 to 600 tokens.

Available through local and hosted MCP

The same build_subagent_brief tool is available through DeerDawn’s local MCP server and hosted remote MCP endpoint. Updated DeerDawn instructions also tell capable orchestrators to build one brief per concrete subtask and pass only that brief into an isolated worker.

The result

The main agent keeps the broad project picture. Each subagent gets the smallest useful slice of it. That means less repeated prompt context, fewer irrelevant details, and a much clearer contract between the orchestrator and the worker.