switch README

项目的 README,来自 github.com/sandbox-quantum/switch。合并为一个 markdown 文件:README.md。

Agent Switch

Open-source AI teammates, working alongside your team in Slack, Teams, Discord, Telegram and Mattermost. Self-host it or run it on Switch Cloud Coming soon, with any agent and any model.

Switch - #1 Product of the Day on Product Hunt

Website Product Hunt License: Apache 2.0 + Commons Clause Documentation PRs welcome Release CI Discord

Switch demo — agents and humans collaborating in Slack

More than a single AI bot you ask questions to: Switch turns each channel into a room where your team and everyone's AI teammates work together, with shared context.

Get started in two steps

  1. Install Switch Console, the desktop app, for your platform.
  2. Open it and talk to switch-buddy, your AI assistant in Switch. Choose Switch Cloud Coming soon or your own server, then tell switch-buddy what you want: it creates your first agents and rooms, helps you connect the messaging app your team uses, and answers anything about Switch. New to Switch? Start here.
Platform Install
macOS Apple Silicon · Intel
Windows Installer
Linux x64 AppImage · DEB
Linux ARM64 AppImage · DEB

See the latest release for all desktop builds.

Watch it work

The same incident, in the apps teams already use. Someone reports checkout failing, an agent opens an incident channel, pulls the error rate and finds the deploy behind it — with a second agent doing the charting. Under a minute each, no narration.

Slack

https://github.com/user-attachments/assets/d7db7859-c1e0-4d2c-9675-1cc3966a1bfd

Discord

https://github.com/user-attachments/assets/e114cf81-41b0-4cce-a06f-5e78830bf99d

Mattermost

https://github.com/user-attachments/assets/51918de4-4283-4717-bdfa-d63f9da8eae1

Why Switch

Your agents can do far more for your team than answer one question at a time. Switch is what unlocks it.

You do not have to start big. Each level builds on the one before it, the first works on day one, and each one gets more out of your agents than the last.

⚡ Level 1. Your everyday agents move into your messaging app.
  • Work on a feature with a colleague and your Claude Code agent, all in one channel.
  • Pull a colleague in to review what you and your agent have been doing. The whole trail is already there, nothing to paste or re-explain.
  • Stand up a Codex agent that knows one slice of the system well, and let any colleague ask it questions directly.
  • Open a channel for a feature and put the people and agents that feature needs into it.
⚡⚡ Level 2. You start encoding how the work runs.
  • A bootstrap channel where anyone asks a manager agent to start a piece of work. It opens the channel, brings in the right people and agents, attaches the context they need, and gets it moving.
  • A feature request channel where an agent triages what comes in, asks the questions you would have asked, and files it in Jira, Confluence or Notion.
  • A bug report channel where an agent reproduces what it can, collects the logs and versions, and either files the ticket or tells the reporter what is still missing.
⚡⚡⚡ Level 3. Your team runs on Switch.
  • Someone reports a bug, the triage agent reproduces it, a coding agent fixes it in a channel of its own, a person reviews the fix, and the deployment agent puts it on the test environment.
  • The triage agent files a feature request, a coding agent builds it in a work channel with the ticket and design already in it, and whoever asked for it signs it off.
  • An alert lands in the on-call channel, whoever holds the role that week picks it up, it goes down the same path as any bug, and an agent writes up what happened into the team's knowledge.
  • Someone asks a question in the support channel, the support agent answers from the runbooks, and when a runbook turns out to be wrong that agent corrects it in the channel that owns it.
⚡⚡⚡⚡ Level 4. Your company runs on Switch.

Every person, team and department works alongside agents, and work crosses between them the same way it crosses between channels.

What Switch is not

Most tools in this space want to become the place your team works. Switch does not replace the stack you already have. It connects it.

Getting humans and agents to work as one team is the part nobody has solved yet. That is where our effort goes, rather than into rebuilding chat apps and coding agents that already work well.

Docs

Let an agent walk you through them

Rather than working through the documentation yourself, connect an agent to it and have it take you through the steps, answering your questions as they come up. The docs are served over MCP at https://docs.switchagents.ai/mcp.

Connect your agent to the MCP server and ask it:

How do I get started with Switch?

Claude Code

Run the following command in a terminal.

claude mcp add switch-docs --transport http https://docs.switchagents.ai/mcp

OpenAI Codex CLI

Run the following command in a terminal.

codex mcp add switch-docs --url https://docs.switchagents.ai/mcp

OpenCode

Run the following command in a terminal.

opencode mcp add

Then follow the procedure and provide https://docs.switchagents.ai/mcp as the MCP server URL.

Read them yourself

Telemetry

Switch Console collects anonymous usage analytics to help us understand how the app is used and improve it. Telemetry is opt-out — it is on by default, you are told about it on first run, and one toggle turns it off.

What we collect:

Data Example Purpose
Event name session_started, room_created Understand which features are used
App version 0.9.14 Track adoption of new releases
Release channel stable Separate pre-release from released usage
Operating system darwin, 23.6.0 Prioritise platform support
Agent provider claude, codex Understand which agents people run
Outcome and error code failure, docker_daemon_down Prioritise bug fixes
Counts and flags agent_count: 3, has_initial_prompt: true Size features without seeing content
Anonymous client ID 3f2a9c41-… (random UUID) Count unique installations

Every field is drawn from a fixed vocabulary of enumerated values, numbers and booleans — free text cannot be transmitted.

What we never collect: source code, prompts, file paths, working directories, repository or project names, room or agent names, server URLs or hostnames, usernames, emails, API keys or credentials, model outputs, search queries, error messages or stack traces, IP addresses, or any personally identifiable information.

Events are sent to a relay we operate (telemetry.switchagents.ai), which forwards them to our analytics providers; no vendor credentials ship in the app.

Opting out: turn off Share usage data on the first-run notice, or in Settings → General at any time. Sending stops immediately — the setting is checked before every event, so there is no queued backlog.

For the complete field-by-field list of every event, how collection is enforced, where the data goes and why it cannot be traced to a person, see docs/TELEMETRY.md.

Switch Core (the server) sends usage telemetry only when TELEMETRY_ENABLED=true, and it is off by default. When on, it reports counts, durations and fixed categories (which chat platform, which agent runtime, success or failure) to the same relay. Each event is tagged with a per-deployment UUID and fixed facts about the server: its version, its release environment, and whether it is one of our own deployments. Nothing identifies a room, tenant, agent, user or message, and nothing is free text; docs/old/telemetry-events.md lists every event.

A server Switch Console runs for you follows Share usage data, with one exception: a "yes" is not applied to a server other people use unless it is already reporting. The server reads the setting when it starts, so a change reaches a running server at its next restart. Console says when a server is out of step and offers to restart it.

Contributing

Switch is being built in the open, with the people who use it. Nobody knows yet what an organization looks like once agents are part of it, we certainly do not have all the right answers, and we would rather work them out with you than guess. There is a lot still to shape here, so come and join in: questions, ideas, arguments and pull requests are all welcome.

CONTRIBUTING.md covers the development setup, the repository layout and how to get a change merged. Participation is governed by our Code of Conduct, and security vulnerabilities go through SECURITY.md rather than a public issue.

switch (sandbox-quantum/switch)

正在搜索数据库…

4.5K ·GitHub
这是什么?Switch 是一个开源平台,让 AI 智能体直接在 Slack、Microsoft Teams、Discord、Telegram 和 Mattermost 中与你的团队协作,使频道成为人与智能体共享的房间。
Switch 会取代我团队的聊天工具,还是与之连接?它不会取代 Slack、Teams、Discord、Telegram 或 Mattermost,而是与它们连接,把你现有的智能体和工作流引入你已经在用的频道。
我该如何让它运行起来?为你的系统安装 Switch Console 桌面应用,打开它,然后与 switch-buddy 对话。switch-buddy 是内置助手,会帮你创建第一个智能体和频道,并协助连接你的聊天工具。
它支持哪些智能体和模型?任何支持该协议的智能体都可以加入,比如你自己的 Claude Code 智能体、同事的 Codex 智能体,或你服务器上的 LangChain 智能体;任何模型或服务提供商也都可以接入,因为 Switch 本身不提供任何智能体或模型。
Switch 不能做什么?Switch 不是即时通讯应用,不是智能体提供商(它本身不附带任何智能体或模型),也不是封闭的自助服务平台。它的代码对所有人公开,任何人都可以查看并参与贡献。
Switch Console 桌面应用支持哪些平台?Switch Console 提供 macOS(Apple Silicon 和 Intel 芯片)、Windows(安装程序)以及 Linux x64/ARM64(AppImage 或 DEB)版本。
Switch 的遥测功能实际收集哪些内容?Switch Console 默认开启、可随时关闭的遥测功能,只发送固定、可列举的事件数据,例如计数和错误代码;它从不收集源代码、提示词、文件路径、房间或智能体名称、消息、凭据或任何个人可识别信息。
switch-buddy 是什么?switch-buddy 是 Switch 内置的助手,会帮你创建第一个智能体和频道,协助连接你的聊天工具,并回答关于 Switch 的问题。
这和直接在 Slack 频道里加一个机器人有什么不同?Switch 不是让你向单个机器人提问,而是把每个频道变成一个房间,多个人和智能体在其中共享同样的上下文、决策和文档,每个智能体都有各自的角色、指令和工具。
智能体能使用 Jira 或 GitHub 等外部工具吗?可以。每个智能体都可以被赋予角色、指令和工具,例如 Google Workspace、Jira 和 GitHub。由于智能体只能看到它所属的房间,上下文会随工作一起流转。
我能只通过询问智能体来学习如何使用 Switch 吗?可以。文档通过 MCP 提供,你可以把 Claude Code、OpenAI Codex CLI 或 OpenCode 等智能体连接到 MCP 服务器,然后让它带你完成入门步骤。
有哪些类似的项目?brigade, claude-code, nanobot, hive, Raven, starnet, nocobase, open-swe
大小
92 MB
星标
4.5K
时长
4个月
提交 · 90 天