ptone

it’s true. Google rarely has just one of anything

thanks for the kind comments (lead Scion architect here), Scion is still very much meant for teams of people to interact with teams of agents. it is not just about scheduling agents on infrastructure. it’s been getting some new UX improvements: https://youtu.be/1WYsoSXt9QQ

[primary author and architect of scion here] The reason this is a testbed is because this is a new and emerging area of replacing things like codified graphs in tools like langraph with pure agent instruction where agents manage agents with a lot more autonomy. These patterns are not well explored, and are not ready for production in most cases. The goal of a testbed is to have an easy and quick way to try out N of these patterns.

[primary author and architect of scion here] Actually - there are two other big parts: a CLI and a control plane

This runs stock Claude Code in containers, should be completely fine for TOS

[primary author and architect of scion here] The missing features are mostly by design - this is closer to what the gastown plans as "gascity" - bring your own orchestration characters and definition.

If you look at this orchestration example

https://github.com/ptone/scion-athenaeum

its just markdown - Scion is the game engine

(a port of gastown to run on scion is in progress)

[primary author and architect of scion here] Part of this will be pushing that cognitive overhead increasingly onto agents. By how much and when is what Scion is here to explore.

[primary author and architect of scion here] There are several layers of state and telemetry - first is provided by the hook system available in most harnesses, then for those that provide OpenTelemetry -that is normalized and forwarded raw (preserving both) to a cloud collector. Finally - some activities are "self reported" by agents using a built-in toolset that can be reflected in the control plane

Been working on this, and should now be resolved https://github.com/google-gemini/gemini-cli/discussions/2064

Try it out with 0.1.5 https://github.com/google-gemini/gemini-cli/discussions/2064

This should be resolved: https://github.com/google-gemini/gemini-cli/discussions/2064

Things should be better now: https://github.com/google-gemini/gemini-cli/discussions/2064