01 — Helicopter View · Scion Series

Scion: The Hypervisor
for AI Agents

Google Cloud's open-source testbed for running multiple AI agents in parallel with isolated containers, git worktrees, and harness-agnostic orchestration

4Harnesses
3Isolation Layers
5Runtimes
The Problem
Multiple agents, one codebase, zero isolation
Running parallel AI agents on the same repo causes merge conflicts, credential leakage, context contamination, and no observability.
40% of agentic projects at risk by 2027
What Is Scion
Manager-Worker orchestration for deep agents
The scion CLI manages agent lifecycles across a Grove (project workspace). Each agent runs in its own container with a dedicated git worktree, credentials, and home directory. Agents dynamically learn the CLI tool and decide coordination themselves via natural language. Open-sourced by Google Cloud, April 2026.
Gemini CLI Claude Code Codex OpenCode
Mental Model
VMware but for AI agents
Each agent gets its own machine (container), its own disk (worktree), its own identity (credentials). The hypervisor manages lifecycle, not the agent's decisions.
Experimental testbed
Grove
Project namespace
1:1 with a git repo. UUID v5 from normalized git URL. Contains .scion/ config. Where agents live and collaborate.
Template
Agent blueprint
System prompt + skills + config. Define roles like "Security Auditor" or "QA Tester". Layered: harness base, template overlay, profile overrides.
Harness
LLM tool adapter
Adapts Gemini CLI, Claude Code, Codex, or OpenCode into Scion. Handles provisioning and execution inside OCI containers.
Runtime
Container backend
Docker, Podman, Apple Container, or Kubernetes. Local or remote via Runtime Broker. Multi-machine via Hub control plane.
Architecture
Manager-Worker with dynamic agent graph
Developer scion CLI Orchestrator AGENT 1 Gemini CLI worktree/feat-auth OCI AGENT 2 Claude Code worktree/feat-api OCI AGENT 3 Codex worktree/fix-tests OCI attach / message start / stop / resume msg msg Git Repository dedicated worktree per agent
Three-Layer Isolation
"Isolation Over Constraints" — agents run unrestricted inside, guardrailed outside
Layer 1: OCI Container
Filesystem, process, and network isolation. Docker, Podman, Apple Container, or Kubernetes pod.
Layer 2: Git Worktree
Dedicated branch at ../.scion_worktrees/<grove>/<agent>. Mounted as /workspace. Same repo history, independent working directory.
Layer 3: Credentials + Shadow Mounts
Separate home dirs. tmpfs shadow mounts block access to .scion/ and other agents. Secrets mounted read-only or via env vars.
90% fewer security incidents No merge conflicts
Agent Lifecycle
Phase + Activity + Detail
Created> Provision> Clone> Running> Stopped
Activity states while running: idle, thinking, executing, waiting, blocked, completed
CLI: start, attach, message, logs, resume, sync, delete
Landscape Comparison
Where Scion fits among multi-agent tools
Tool Architecture Isolation Multi-Agent Harness-Agnostic
Scion Manager-Worker hypervisor Container + worktree Yes, parallel 4 harnesses
OpenHands Event-stream delegation Docker sandbox Delegation model Model-agnostic
CrewAI Role-based DSL Process-level Sequential + parallel Via LiteLLM
LangGraph State machine / graph Cloud sandboxes Graph-based Model-agnostic
Aider Single-agent pair None Single agent Multi-model
Multi-Agent Anti-Patterns
What breaks without orchestration
Five Design Principles
Scion's philosophy for agent orchestration
01 — Helicopter · Scion Series · Detail pages: 02 Architecture · 03 Isolation · 04 Harnesses · 05 Anti-Patterns Scion Series