Isolation over constraints sounds like the right philosophy. Containers give you a boundary but not vis into what ran inside them. Curious how much execution context Scion surfaces, w/o that you're still in a position similar to the LiteLLM attack where something can run and cause damage before you know it happened.
Google open-sources experimental agent orchestration testbed Scion
41–50 of 78 posts
Re: Google open-sources experimental agent orchestration testbed Scion
#42Isolation over constraints sounds like the right philosophy. Containers give you a boundary but not vis into what ran inside them. Curious how much execution context Scion surfaces, w/o that you're still in a position similar to the LiteLLM attack where something can run and cause damage before you know it happened.
[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
Re: Google open-sources experimental agent orchestration testbed Scion
#43[flagged]
[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.
Re: Google open-sources experimental agent orchestration testbed Scion
#44This seems to be in the direction of Gas Town but missing some of the core features. Having formulas has been game changing.
[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)
Re: Google open-sources experimental agent orchestration testbed Scion
#45I want to experiment more with agents but my employer only pays for Claude Code, and TOS disallows using the subscription API for other purposes. Anyone else in the same boat? Token based pricing also gets expensive fast.
This runs stock Claude Code in containers, should be completely fine for TOS
Re: Google open-sources experimental agent orchestration testbed Scion
#46Their agent tooling is shaping up to be the well known issue of product cancellation. They have how many different takes on this now? (gemini-cli, antigravity, AI studio, this, Gemini app) I've not been impressed with any of them. I do use their ADK in my custom agent stack for the core runtime. That one I think is good and has legs for longevity. The main enterprise problem here is getting the various agent framewor…
It's all just system prompts under the hood and nothing more.
[primary author and architect of scion here] Actually - there are two other big parts: a CLI and a control plane
Re: Google open-sources experimental agent orchestration testbed Scion
#47[flagged]
Re: Google open-sources experimental agent orchestration testbed Scion
#48Agent orchestration is one side of the problem. The other side
is: where does the data go?
When agents process EU user data (names, emails, IBANs) and
route it to US model providers, that's a GDPR violation.
I open sourced a routing layer that detects PII in prompts and
forces EU-only inference when personal data is found:
https://github.com/mahadillahm4di-cyber/mh-gdpr-ai.euRe: Google open-sources experimental agent orchestration testbed Scion
#49[deleted]
Re: Google open-sources experimental agent orchestration testbed Scion
#50[flagged]
[flagged]