What is Scion? A guide to three different projects
Understand Anthropic’s internal source control system, the independent OpenScion implementation, and Google’s unrelated agent orchestration project.
Scion is the name Anthropic gives its internal version control system. It is also a name used by an unrelated agent orchestration project. OpenScion is a separate community implementation inspired by Anthropic’s published design. These are three different projects; downloading one does not give you another.
ScionHub is an independent reference site. It does not operate Anthropic’s system or provide hosted repository storage.
Identify the project first
| Name | Owner | What to expect |
|---|---|---|
| Scion source control | Anthropic | An internal system described in an engineering article |
| OpenScion | tinyhumansai/openscion contributors | Public Rust source code and an early implementation |
| Scion agent orchestration | GoogleCloudPlatform/scion contributors | A platform for coordinating agents, rather than a new source control format |
Anthropic describes a server-centered design for a very large monorepo and always-connected agents and jobs. Source control operations happen on the service, while clients request the data they need. The article supplies architecture and migration experience, not a downloadable public Scion release. It also explains why a broadly useful public version would be difficult; that is more precise than claiming the company has promised never to release it. Anthropic engineering article
The GoogleCloudPlatform repository describes agent collaboration and execution infrastructure. Its “Hub” is part of that project’s control plane. Instructions for its scion CLI should not be used to install OpenScion. The repository also says it is not an officially supported Google product. Scion orchestration repository
What can you actually try?
For source control experiments, OpenScion provides the opnscn client and an HTTP server. At the revision reviewed here, the client can import a directory, commit edits, and clone a full snapshot or one directory. That makes it useful for exploring an object protocol and a small working-copy lifecycle. Its import command is a directory snapshot import, not Git history migration. Pinned client documentation
Before running an example, record the repository owner, commit ID, client version, and intended task. “Scion supports this” is too ambiguous for a dependency decision. “OpenScion at 00e92ab, using opnscn clone --path, supports this local experiment” is a claim another engineer can check.
Choose a useful next question
If your CI spends time obtaining code, first measure that step separately from dependency installation and build execution. If your interest is agent coordination, follow the orchestration project’s documentation instead. If you are considering private code hosting, start with the OpenScion status review: running a server process and entrusting it with the only copy of source code require very different evidence.
The architectural ideas are worth studying without assuming you need to replace Git. A small experiment should answer one workload question and leave the authoritative repository recoverable.