Player profile
Scion
An Apache-2.0 orchestration platform for teams of Claude Code, Gemini CLI, Codex, and OpenCode agents running as independent processes with delegation, messaging, and parallel execution.
Profile
Where it fits
Scion runs coding agents with per-agent configuration and credentials. Teams can use shared workspaces, separate Git worktrees, or clones, and agents can delegate tasks and exchange messages while they execute in parallel.
It belongs in Parallel Coding-Agent Runners because it manages the execution and collaboration environment around existing coding-agent CLIs. The README documents local CLI, Workstation UI, and hosted Hub modes; those modes do not guarantee successful autonomous teamwork.
Builder web analytics
Measure projects built with Scion
After Scion-managed agents ship a reviewed change, separately configured analytics can help assess its user-facing outcome.
This is an optional measurement workflow, not a native Scion integration. Configure product tracking and authenticated Agent Analytics access separately; Scion's agent processes and messages are not product analytics events.
First loop to measure
- a team implements and reviews a product change
- the team deploys it to a separately instrumented surface
- an agent with separately configured analytics access reads the observed results
- the operator uses that evidence to scope the next task
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including deployed page, signup, activation event, or funnel step. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which deployed page, signup, activation event, or funnel step moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.