The Race — Building Democracy in the Age of AI. People race toward a shared finish line.
The Race
← Specific Events

Global

Scorecard

SandboxAQ releases Switch multi-agent collaboration layer — August 26, 2026

What happened

SandboxAQ released Switch, a publicly available, source-available and self-hostable orchestration layer that connects independently chosen AI agents to collaboration environments including Slack, Microsoft Teams, Discord, Telegram and Mattermost. Switch supports agents built with or operating through multiple providers and frameworks, including Claude Code, OpenAI/Codex, Google ADK, LangChain and custom agents. Its shared-room architecture preserves room-specific participants, context and rules while allowing agents to operate across multiple rooms.

Potential direction of power

Dispersion · Dispersion +1 — separates agent choice from workplace distribution

Switch weakens an emerging source of platform lock-in by separating the agent/model layer from the collaboration/distribution layer. Institutions can maintain a common workspace and accumulated organizational context while bringing in agents from competing providers rather than allowing one AI vendor to control both intelligence and the interface through which institutional work occurs.

As agents become embedded in organizations, control over the workplace interface could become as important as control over the underlying model. Switch creates a provider-neutral intermediary at that boundary. The architecture could also support settings involving multiple organizations or constituencies—potentially including public consultations or collaborative civic processes—although such cross-organizational use remains to be demonstrated.

Window of contestability

Opens

Positive, with a licensing qualification. Organizations can inspect and self-host the coordination layer and substitute agents or model providers without rebuilding the workplace interface. However, Switch's Apache 2.0 + modified Commons Clause license restricts commercial resale and some hosted-service uses, so it should be characterized as source-available rather than fully open-source infrastructure.

Supporting sources

  1. sandboxaq.com · Supporting source 1 ↗