Feature Request: Project Orchestrator Mode

Resolved 💬 6 comments Opened Dec 3, 2025 by ian-klopper Closed Feb 28, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

There's no way to have a persistent planning agent that coordinates multiple cloud agents while maintaining maximum context for decision-making.Current limitations:

Cloud agents work in isolation with no central coordinator tracking them
No agent maintains awareness of all active + historical agent sessions
No visibility into feature branch → dev merge workflow across agents
Planning context gets polluted with implementation details
When using Cursor's "move to background" feature, the entire agent transfers to cloud—there's no stationary orchestrator that stays aware of all work.

Proposed Solution

A dedicated Project Orchestrator Mode where one agent:

Plans only - Cannot use Edit/Write/Bash tools, only dispatch and coordinate
Tracks all agents - Registry of active, completed, and blocked agents with their feature branches
Maximum context - Holds project docs + full agent history + developer conversation
Receives summaries only - Completion reports, not execution logs

Alternative Solutions

Current subagents: Don't persist across sessions, no registry of historical work
Manual tracking: Developer becomes the orchestrator (defeats the purpose)
Cursor background: Moves entire agent, loses the coordinator
File-based coordination: Clunky, requires polling, no real-time awareness

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Example workflow:
Developer: "Add authentication"

Orchestrator:
→ Spawns 3 agents on feature/auth-* branches
→ Updates DECISIONS.md with approach
→ Reports: "Agent-1 merged schema to dev, Agent-2 on middleware, Agent-3 blocked on design"
→ Can explain any agent's approach from summary context

Additional Context

This enables a "tech lead" agent pattern where one agent maintains project-level understanding while delegating implementation to specialized workers.

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗