Getting started

Your first session

Install the free extension, configure your models and give the team a small task. Start with the roles your task needs and your account supports. A formal Project is optional; you can begin by chatting about the open workspace.

1 · Install and open the chat

First, get an early-access package. In VS Code, open Extensions → … → Install from VSIX…, choose the file you received and reload if prompted. You do not need the source repository or npm install to use the extension.

Open a small local folder. Any of these opens the chat:

The AI Orchestra view in the sidebar; its location varies with your VS Code version
Ctrl+Alt+O / Cmd+Alt+O
The AI Orchestra button in the status bar
Command Palette → AI Orchestra: Open Chat — or Open Chat Window to pop it out as a tab

2 · Add your provider keys

Start with one provider key and a Drafter. Local chat does not require an AI Orchestra account. Your provider bills API usage; configure API access in the provider’s developer account.

Type /settings in the composer. For each provider — Anthropic, OpenAI, Google, xAI or OpenRouter — pick it from the dropdown, paste the key, Save Key, then Fetch Models and assign a role.

Keys are stored in vscode.SecretStorage on your machine. They are never logged, never proxied, and never sent anywhere except direct to the provider.

Already keep keys in a .env.local? Put it in the project folder and click Import keys from .env.local. Vendor-doc and SDK spellings are recognised; near-misses such as OPENAI_API_ADMIN_KEY are deliberately ignored.

3 · Choose your team

For your first collaboration, assign a Drafter and Reviewer within your available seat capacity. One provider can fill both roles. Add an Indexer or Architect when you need more context or coordination; three roles are not required to begin.

Seat	Put here	Why
`drafter`	Your best code model	The default writer, subject to your Project policy and edit permissions.
`reviewer`	A model for review; the same provider is fine	Checks the writer’s work and raises concerns.
`indexer`	The longest context window	Maps the context it can actually access and surfaces cross-file risks.

Choose models for the job you want each to do. A strong Reviewer can catch issues a strong writer misses. A model’s name does not establish which tools or connections are available through its selected interface.

4 · Prepare the environment

Paste this prompt into the Orchestra chat after configuring your models. It asks the team to verify the source location, available tools and target dependencies before building. If the participant cannot execute setup commands, it must report that gap rather than claim the environment is ready.

Read the setup prompt

Set up this workspace for AI-Orchestra before starting the real task.

Read the current goal, Project constitution and relevant handoff if available.
Identify the installed build, open folder and actual source-write location.
Do not create a Project unless I want one; chat and vibe coding can start without it.

Use my configured AI team. Architect is the AI Coordinator; identify the writer.
If Architect is unavailable, report the missing seat rather than reassigning its role.
Verify each participant's tools, execution access and authorized context connections.
A model API key does not automatically bring its vendor application's tools.

For a Project, record local, cloud or hybrid only where implemented.
Declare one authoritative workspace. Preserve existing files and Git changes.
Verify where writes actually land before editing an existing repository.
Cloud storage does not itself provide a shell or build runner.

Inspect the target's manifest and setup instructions. Through available authorized
tools, check and prepare only its required dependencies and run its relevant checks.
Never print secrets, install unrelated tools or claim a command ran without evidence.
Use the supported settings/sign-in UI for credentials.

Confirm my selected permissions and cost/time/round limits before paid work.
Report READY, PARTIAL or BLOCKED with actual versions, paths, checks and gaps.
If execution or cloud access is unavailable, identify the missing capability.
Save a dated setup handoff where persistence is configured. Do not deploy or change
production data as part of setup. Then state the exact next action.

5 · Try one bounded task

Set your spending limit with /cost cap 1, select /plan, then /mode raise-hand. Send a normal message such as “Propose a three-step plan for a small README improvement. Explain the tradeoffs before making edits.” The Drafter should stream a reply and a configured Reviewer can raise a concern. If you get a system message instead, it names what is missing: usually an unassigned role or an unsaved key.

The header shows your build, seated roles, recorded cost, and the estimated token and input cost of the latest provider payload. Keep the default approval setting for edits and use /context to see how Project instructions, repeated history and current evidence contribute. Use /context save to refresh compact CONTEXT.md memory before a long session. Press Esc to stop a response.