Google Scion vs Skrun

Google Scion is an open-source "hypervisor for agents" — a runtime that manages groups of AI agents in isolated containers, each with its own identity, credentials, git worktree, and toolset. Think of it as Kubernetes for agent teams: you declare your agent topology, Scion provisions the sandboxes, and agents can collaborate through structured channels without sharing file system or credential state. The isolation-over-constraints philosophy is Scion's core bet: rather than trying to constrain what a single powerful agent can do, give each agent a minimal, scoped environment where the blast radius of any failure or misbehavior is bounded. Harness adapters allow integration with Claude Code, Gemini CLI, and other existing agent runtimes — Scion acts as the orchestration layer above any underlying agent technology. For teams building multi-agent systems at scale, the credential isolation alone is a major feature — no more worrying about one agent leaking API keys to another. The Docker/Kubernetes support means it drops into existing infrastructure. Scion represents Google's opinionated answer to the question every AI platform team is grappling with: how do you run multiple AI agents safely in production without building a custom isolation layer from scratch?

Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.