1. Create a workspace
A workspace is your unit of context, it holds your sources (repositories or folders), agents, issues and knowledge base. When you open Orkestral for the first time, create a workspace and give it a name (for example, your product’s name).2. Connect a source
Add a source, a local repository or folder. Orkestral reads and maps it so the agents understand your stack, structure and conventions before doing anything.3. Hire your team
Ask the CEO agent (in chat) to assemble a team. It proposes an initial roster, typically a Tech Lead, a Code Reviewer and the specialists your project needs (Frontend, Backend, DevOps…), with a proper reporting hierarchy.4. Ask for something
Talk to the CEO in natural language. Describe what you want, a feature, a fix, a refactor. You don’t need to specify how.Plan
The CEO reads the relevant code, breaks the request into issues, and
delegates to the right specialists.
Execute
Specialists run the work. The Forge applies code changes locally, at no API
cost, and only escalates to a premium model when needed.
Review
The Code Reviewer validates the changes. Verdicts (approved / changes
requested) come back to you in chat.
5. Route to a specialist
Mention an agent with@ to send a turn directly to them, for example
@Code Reviewer take a look at this PR. That agent picks up the chat context and
does the work itself.
Next steps
The agent team
How the CEO, Tech Lead, Code Reviewer and specialists work together.
Forge, local execution
How the local model executes changes at $0 API cost.
More guides (Issues & epics, Code review, Knowledge base, Integrations) are on the
way.