Give better context
Create and manage custom subagents from Android
Subagents are useful when the work has separable specialties. FireCursor can discover, create, edit, and delegate to project-defined agents while the main project session remains the control point.
Quick answer
The shortest useful version.
Give each subagent one durable specialty, a narrow tool and file boundary, and a concrete return contract. Delegate independent work, then review its evidence in the parent task.
Step by step
Do this with confidence.
- 01
Define the specialty
Use a role that changes the workflow—such as accessibility audit or release verification—not a vague label like ‘helper.’
- 02
Set boundaries
State the files, tools, authority, and external actions the subagent may use, plus what requires escalation.
- 03
Specify the handoff
Require findings, changed files, commands run, and unresolved risks in a compact return.
- 04
Review centrally
The parent operator owns integration. Compare all outputs, resolve conflicts, and run whole-product verification.
When delegation is worth it
- Two tasks can run independently
- A specialty has a distinct verification method
- Context can be bounded cleanly
- The parent has time to integrate and review
- Shared files will not be edited concurrently
Avoid agent theater
More agents do not automatically produce a better product. Delegation adds coordination cost, duplicated context, and possible conflicts. Use it when independence and specialization are real.
FireCursor’s project and evidence surfaces should make ownership visible, not celebrate activity for its own sake.