~/.orkestral.
Use one workspace per product, client or project. Keeping contexts separate gives your agents sharper focus and cleaner history.
Why workspaces exist
Your agents only work well when they share the right context. A workspace draws that boundary for you, it decides which repositories the team can read, which agents are on the roster, and where new issues and knowledge land.Scoped context
Agents read only the sources in the current workspace, so plans and code changes stay relevant.
Local and private
Each workspace lives on your machine under
~/.orkestral. No server, no telemetry.Trackable work
Issues, code changes, reviews and knowledge are all filed against the workspace.
Visual identity
Give each workspace its own accent color so you always know where you are.
What lives inside a workspace
Sources
The repositories and folders your team can read. This is the codebase context.
Agent team
The CEO orchestrator and specialists assigned to this workspace.
Issues
Every request becomes trackable work, plans, code changes and reviews.
Knowledge base
Notes, decisions and context the team builds up as it works.
Create a workspace
Open the workspace switcher
Click the workspace name in the top of the sidebar to open the switcher.
Choose New workspace
Select New workspace and give it a clear name, usually the product or project name.
Add your sources
Add the repositories or folders the team should read. See Sources for details.
Switch between workspaces
You can keep as many workspaces as you like and move between them instantly.Next steps
Connect sources
Point the workspace at the repositories and folders your team should read.
Meet your team
See who is on the roster and how the reporting hierarchy works.