The Orchestrator chat
The Orchestrator is the chat inside CodeSpring. You use it to generate tasks, docs and features for a feature you have tagged, and to control the map without doing everything by hand. It is powerful, but it works best once a plan already exists.
What it is
The Orchestrator is CodeSpring's in-app agent: a chat panel that works directly on your mind map. Instead of clicking through nodes, you tell it what you want in plain language and it does the map work for you. It can generate tasks for a feature, write docs, add new features to the canvas, and make changes to the map you would otherwise make by hand.
Generate build tasks for the Scanner feature so I can hand them to Cursor.
On it. I pulled the Scanner card and its sub-features from your map and split the work into six tasks, ordered by priority:
- Index the local video library (thumbnails + hashes)
- Perceptual-hash duplicate detection
- Near-frame similarity scoring
- Results grid with side-by-side compare
- Bulk select and delete flow
- Background re-scan when new files land
All six are on To Do in the Kanban board. Want me to draft the Scanner PRD next?
Everything it produces lands in the same places you already know. Tasks show up on the board covered in Kanban and tasks, and generated docs live in the map like the PRDs covered in Docs and PRDs.
Add to context
The Orchestrator does not guess which part of your app you mean. You use Add to context to tag a core feature, and the chat focuses on that feature when it generates. Tag your login feature and ask for tasks, and the tasks it writes are about login, grounded in the notes and plan already attached to that feature, not about your app in general.
This is the habit worth building: tag first, then ask. A tagged feature turns a vague request into a focused one, the same way pointing at a node on the map does.
Chat history
Every conversation is saved. Open the history from the panel header to search your past chats and jump back into one, so the plan you talked through last week is still there when you come back to it.
This month
Project Planning
2 Jul
Checkpoints
Checkpoints are version control for your plan. Before you let the Orchestrator make a big change, create a checkpoint from the panel header. It saves the state of your map, so if a generation goes somewhere you did not want, you can roll back to exactly how things were.
The habit is simple: checkpoint before big changes, then explore freely. You never have to worry about losing a version of the plan you were happy with.
Plan first, then chat
Heads up. If you are building your first app, do not lean on the Orchestrator chat to do your planning. Lay the app out on the map by hand first, feature by feature, then use the chat to refine and generate from that plan. Chatting before you have a plan puts the thinking back in the AI's hands, which is exactly what the map is there to prevent.
Mapping by hand costs nothing and forces you to get clear on what you are actually building. Once the shape of the app exists on the canvas, the Orchestrator becomes a fast way to fill it in: generate the tasks, write the docs, add the next feature. New to that flow? Start with Build from scratch.