Skip to main content
A source is a repository or folder you connect to a workspace. When you add a source, Orkestral reads and maps it before any agent acts. Your agents understand the stack, structure and conventions of your code from the very first request.
Sources stay on your machine. Orkestral reads them locally in ~/.orkestral, nothing is uploaded.

​
Add a source

Open your workspace

Select the workspace you want the team to work in, then open its Sources panel.

Connect a repository or folder

Click Add source and pick a local Git repository or any folder on your disk. Orkestral detects whether the folder is version-controlled.

Let Orkestral map it

Mapping starts automatically. Wait for it to finish, the source is ready once the team has a full picture of your code.
A single repository is enough to get started. You can connect more sources at any time.

​
What mapping does

Mapping is how Orkestral turns a folder of files into context the team can reason about. It runs once when you add a source and refreshes as your code changes.

Detects the stack

Identifies languages, frameworks and tooling so agents speak your project’s dialect.

Reads the structure

Maps directories, modules and entry points to know where things live.

Learns conventions

Picks up naming, patterns and style so generated code matches your codebase.

Indexes for retrieval

Builds an index agents search to pull the right files into context on demand.
Because mapping happens before any agent acts, the CEO orchestrator plans against real structure instead of guessing. Specialists then read the exact files they need.

​
Use multiple sources

One workspace can hold many sources, and agents read across all of them. This is useful when your work spans more than one repository.
Add both repositories to the same workspace so a change that touches the API and the UI is planned and executed with full context on both sides.
Connect your application and a shared package so agents understand how they depend on each other.
Include a docs folder so the team can update documentation in step with the code it describes.
Every source you add is mapped independently, then made available to the whole team in that workspace.

​
Git awareness

For sources under version control, Orkestral surfaces Git status and diffs. Agents see exactly what you have changed, so plans and reviews reflect your working tree, not just the last commit.

Status

See which files are modified, added or untracked at a glance.

Diffs

Inspect line-by-line changes that agents read before they act on a file.
If a source is a plain folder without Git, agents still read and map it, but status and diffs are unavailable until it becomes a Git repository.

​
Next steps

Workspaces

Organize sources and the team into focused workspaces.

Meet the team

See which agents read your sources and how they collaborate.