The rules of development changed. Work is simultaneous now — across every project at once.

Instead of checking each silent session in turn, you can read the workload as a whole. Names, colors, and reported states make each agent easy to place; a short recap restores the thread when it is time to step back in.

• Read each agent's state. Reported states keep active, finished, and "Awaiting input" work distinct, so the session needing you stands apart.
• Keep everything in view. Zoom out across the canvas or check the minimap to read the whole workload together.
• Recognize every terminal. Names and colors distinguish each session; worktree and task-group colors keep related work together.

Orkestra ships a fully integrated MCP server — Full-Surface MCP — a control registry of many tools covering projects, task boards, terminals, launchers and harnesses, working files, version control, and scheduling. Flip one toggle and every agent you launch can operate the environment it runs in: create tasks, open terminals, provision worktrees, launch siblings. Every human-operable capability has an agent-operable MCP equivalent.

• Sub-agents with a UI. An agent calls open_agent_terminal — a new window appears on your canvas, task created, agent launched. The caller commands it, answers the prompt it's stuck on, waits for it to go idle, reads its output, recaps it. Harness choice does not set the collaboration boundary: through Orkestra, one agent can launch, guide, and message another on any other harness. You see both sides; you can take either over.
• One switch. Launch is controlled by a single switch; an integrated launcher loads the MCP configuration and the skills the agent needs automatically.
• Scoped per project. The MCP surface is configured per project — with per-project restrictions on what an agent may reach.

After a quit, crash, or reboot, Orkestra fully restores the workspace you were using, so you return to the work instead of rebuilding it. Every session comes back dormant, with its history readable. When you choose, one click reconnects it and the agent continues from its own saved conversation.

• Power cut, workspace restored. Reopen to every window and readable thread, with sessions waiting dormant.
• Yesterday is still findable. Find a closed session by what it was doing, then reopen its conversation.
• Continue mid-thread. The agent returns to its own saved conversation, not a blank prompt.

Creating a worktree used to mean copying tracked files into another directory. Orkestra turns that action into a working version of the project: it brings across the environment you declared, assigns separate ports, and lets the agent run the app and test its change before you merge.

• The environment arrives too. Declared env files, local config, certificates, and data directories come across with the new branch.
• The app starts here. After dependencies install, the new worktree boots the real application on ports of its own.
• Test before the merge. The agent runs integration tests, e2e flows, or manual checks inside the worktree it changed.

Telegram provides remote control of the development environment itself — not a single harness's remote — so you can open any project, check every agent, and direct the one that needs you. And across every project, one Orkestra scheduler launches a task or group on any integrated harness, regardless of provider.

• The ADE has the remote. Through Telegram, open any project, inspect every agent, and send the selected agent a command.
• Not a harness remote. Telegram remote control covers the environment itself: every project and every agent, whatever its harness.
• Scheduling stays harness-agnostic. One Orkestra scheduler launches tasks or groups on any integrated harness, from any provider, across projects.

Orkestra reduces the process and memory cost of running many agents on one machine. An idle terminal can end its process tree without losing its place or conversation; hidden output gets lighter handling. It tracks each agent's load live, automatically sleeps long-idle terminals, and wakes them with one click, handling the resource work for you.

• Sleep frees memory, not access. Orkestra automatically ends long-idle process trees; last output, recap, and transcript remain readable.
• Wake in one click. The agent resumes the same conversation from the harness's own transcript, with its window and task link intact.
• See every load live. Follow each agent's resource use in real time without inspecting processes yourself.