# AgentHub

> AgentHub is TokenDance's IM-form multi-agent collaboration platform. Add AI agents as teammates in group chats; three native clients (Desktop, Web, Mobile) share a v4 workbench backed by Hub and Edge servers.

Canonical site: https://hub.vectorcontrol.tech/en

GitHub: https://github.com/TokenDanceLab/AgentHub

Identity provider: https://id.vectorcontrol.tech

## Key Links

- [Chinese home](https://hub.vectorcontrol.tech/zh)
- [English home](https://hub.vectorcontrol.tech/en)
- [Chinese docs](https://hub.vectorcontrol.tech/zh/docs/overview)
- [English docs](https://hub.vectorcontrol.tech/en/docs/overview)
- [GitHub repository](https://github.com/TokenDanceLab/AgentHub)

## English Documentation Index

Generated from the English Astro docs collection.

- [System Architecture](https://hub.vectorcontrol.tech/en/docs/architecture): AgentHub uses a 5-layer modular, event-driven architecture so AI agents can act as first-class collaborators in IM-form group chats across Desktop, Web, Mobile, Hub, Edge, and integration surfaces.
- [Hub And Edge](https://hub.vectorcontrol.tech/en/docs/hub-edge): AgentHub splits collaboration from execution. Hub owns identity, projects, routing, and audit. Edge owns local workspaces, runs, runtime adapters, diffs, artifacts, and approvals.
- [Web Workbench](https://hub.vectorcontrol.tech/en/docs/web-workbench): AgentHub Web (port 5174) is the Hub-backed IM-form collaboration surface. It shares the same workbench UI with Desktop, so your team can see projects, shared sessions, run history, review state, and integration-created tasks.
- [Agent Profiles](https://hub.vectorcontrol.tech/en/docs/agent-profiles): Agent Profiles describe how a coding agent is presented, selected, authorized, and connected to a runtime adapter. They are the bridge between product UX and execution details.
- [Collaboration](https://hub.vectorcontrol.tech/en/docs/collaboration): AgentHub collaboration turns a local agent run into a visible team workflow. This page describes the intended product boundary for shared sessions, reviews, approvals, and integration entries.
- [Run Lifecycle](https://hub.vectorcontrol.tech/en/docs/run-lifecycle): A run is one execution attempt for a task, agent profile, target Edge, workspace, and runtime adapter. The lifecycle matters because AgentHub promises visible, reviewable, and auditable agent work, not just a terminal transcript copied into a webpage.
- [Adapter Contract Preview](https://hub.vectorcontrol.tech/en/docs/adapters): The examples on this page are illustrative until the public Go SDK package is stable. They describe the Agent Runtime adapter contract inside Edge Server and do not promise a current stable import path.
- [API And Events](https://hub.vectorcontrol.tech/en/docs/api-reference): AgentHub public contracts are split into REST APIs, WebSocket events, runtime adapter events, and IM integration events. This page describes the intended boundaries; complete OpenAPI, event schemas, and SDK packages are still in development.
- [Feishu/Lark Integration](https://hub.vectorcontrol.tech/en/docs/feishu): AgentHub uses Feishu/Lark as a collaboration surface: bot messages, event subscriptions, interactive cards, and an H5/workbench entry. Product login and account binding still belong to TokenDance ID.
- [AgentHub Documentation](https://hub.vectorcontrol.tech/en/docs/overview): AgentHub is TokenDance's IM-form multi-agent collaboration platform. Users add AI agents as teammates in group chats. Three native clients — Desktop (Tauri 2), Web, and Mobile (Expo RN) — share a v4 workbench backed by Hub and Edge servers.
- [Product Status](https://hub.vectorcontrol.tech/en/docs/product-status): AgentHub public status map showing which capabilities are live, which can be previewed locally, and which are still in development.
- [Quickstart](https://hub.vectorcontrol.tech/en/docs/quickstart): This guide starts the local preview path: AgentHub Desktop -> Local Edge -> Runtime Adapter, plus Web on port 5174. Mobile Expo RN is a separate path.
- [Installation](https://hub.vectorcontrol.tech/en/docs/installation): This page explains the local development setup for AgentHub Desktop (Tauri 2, port 5173), Web (port 5174), Mobile (Expo RN, port 5177), Local Edge, Hub Server, and runtime adapters.
- [Concepts](https://hub.vectorcontrol.tech/en/docs/concepts): This page defines the terms used across AgentHub docs and separates preview-ready work from features still in development.
- [Glossary](https://hub.vectorcontrol.tech/en/docs/glossary): Use this glossary when reading AgentHub docs, issues, and release notes. The goal is to keep product, runtime, identity, and deployment terms precise.
- [Workflows](https://hub.vectorcontrol.tech/en/docs/workflows): This page maps AgentHub concepts to the work people actually perform: local runs, team-visible reviews, Hub-backed collaboration, Feishu/Lark entry points, runtime adapter development, and release evidence.
- [Usage Cookbook](https://hub.vectorcontrol.tech/en/docs/usage-cookbook): This cookbook turns the higher-level AgentHub docs into task recipes. Use it when you know what you want to do and need the shortest safe path through Desktop, Local Edge, Hub, Web, runtime adapters, or public release work.
- [Desktop Guide](https://hub.vectorcontrol.tech/en/docs/desktop): AgentHub Desktop is the Tauri 2 native local workbench for running, reviewing, and approving agent work. It shares the same workbench UI with Web and Mobile.
- [Desktop UI Reference](https://hub.vectorcontrol.tech/en/docs/desktop-ui): AgentHub Desktop is the Tauri 2 native local control surface for visible agent work. It renders the v4 shared workbench from the v4 shared workbench. This reference maps expected UI regions, states, and interactions.
- [Configuration](https://hub.vectorcontrol.tech/en/docs/configuration): AgentHub configuration is split by responsibility. Keep local execution settings close to Desktop/Edge, keep identity and team settings in Hub, and keep provider credentials out of frontend code.
- [Identity And Login](https://hub.vectorcontrol.tech/en/docs/identity-login): AgentHub uses TokenDance ID as the identity authority. The public AgentHub Home site should link users into TokenDance ID instead of implementing a separate local password card.
- [Security Boundaries](https://hub.vectorcontrol.tech/en/docs/security): AgentHub separates identity, product authorization, local execution, IM events, and model API credentials. Public docs describe boundaries and principles only; they do not publish production hosts, secrets, rollback paths, or private evidence.
- [Data And Privacy](https://hub.vectorcontrol.tech/en/docs/data-privacy): AgentHub coordinates local files, runtime output, team review, and product identity. This page explains where data should live, what public docs can say, and what must stay local, server-side, or private.
- [Operations Runbook](https://hub.vectorcontrol.tech/en/docs/operations-runbook): This runbook covers public-site, docs, local preview, and integration evidence for AgentHub. It is intentionally secret-free: production host paths, rollback commands, keys, and private logs belong in the private operator workspace.
- [Deployment](https://hub.vectorcontrol.tech/en/docs/deployment): This page explains the public-site deployment boundary for AgentHub Home and docs. It intentionally avoids private host paths, SSH aliases, rollback commands, and secrets.
- [Troubleshooting](https://hub.vectorcontrol.tech/en/docs/troubleshooting): This page lists troubleshooting paths for the AgentHub website, Desktop/Web, Hub/Edge, runtime adapters, and Feishu/Lark integration.
- [FAQ](https://hub.vectorcontrol.tech/en/docs/faq): This page answers common product, setup, identity, runtime, and documentation questions.
- [Release Checklist](https://hub.vectorcontrol.tech/en/docs/release-checklist): Use this checklist before publishing AgentHub Home, docs, or public packaging changes. It keeps public docs useful while preventing accidental leakage of private deployment details.
- [Contributing](https://hub.vectorcontrol.tech/en/docs/contributing): AgentHub is moving quickly, so contributions need to preserve product boundaries as much as code quality. This page explains how to choose work, what evidence to attach, and how to avoid turning in-development product ideas into public launch claims.
- [Roadmap](https://hub.vectorcontrol.tech/en/docs/roadmap): This roadmap explains the public status of AgentHub capabilities. It is intentionally conservative: a capability is marked stable only after implementation, tests, docs, and visible verification evidence exist.
- [Design System](https://hub.vectorcontrol.tech/en/docs/design-system): AgentHub Home follows the shared TokenDance design contract while preserving the product-specific Desktop workbench feel. This page documents the public-site design rules so homepage, docs, mock UI, icons, and motion stay aligned.
- [AgentHub vs Alternatives](https://hub.vectorcontrol.tech/en/docs/comparison): This page explains AgentHub's product direction against adjacent tools. It is not a claim that every listed AgentHub capability is production-complete today.
- [Changelog](https://hub.vectorcontrol.tech/en/docs/changelog): This page records public website and documentation changes plus high-level AgentHub development milestones. It is not a substitute for release notes in the AgentHub repository.

## Chinese Documentation Index

Generated from the Chinese Astro docs collection.

- [系统架构](https://hub.vectorcontrol.tech/zh/docs/architecture): AgentHub 采用 5 层模块化事件驱动架构，让 AI 智能体成为 IM 式群聊中的一等队友，覆盖 Desktop、Web、Mobile、Hub、Edge 和集成入口。
- [Hub 与 Edge](https://hub.vectorcontrol.tech/zh/docs/hub-edge): AgentHub 把协作和执行拆开。Hub 管身份、项目、路由和审计；Edge 管本地 workspace、run、runtime adapter、diff、artifact 和审批。
- [Web 工作台](https://hub.vectorcontrol.tech/zh/docs/web-workbench): AgentHub Web（端口 5174）是 Hub 驱动的 IM 式协作界面。它与 Desktop 共享同一套工作台 UI，团队可以在这里查看项目、共享 session、run 历史、审查状态和集成创建的任务。
- [Agent Profile](https://hub.vectorcontrol.tech/zh/docs/agent-profiles): Agent Profile 描述一个编码 Agent 如何展示、选择、授权并连接到 runtime adapter。它是产品 UX 和执行细节之间的桥。
- [团队协作](https://hub.vectorcontrol.tech/zh/docs/collaboration): AgentHub collaboration 把本地 Agent run 变成团队可见工作流。本页说明 shared session、review、approval 和 integration entry 的产品边界。
- [Run 生命周期](https://hub.vectorcontrol.tech/zh/docs/run-lifecycle): Run 是某个 task、Agent Profile、目标 Edge、workspace 和 runtime adapter 的一次执行尝试。生命周期很重要，因为 AgentHub 承诺的是可见、可审查、可审计的 Agent 工作，而不是把终端 transcript 复制到网页里。
- [适配器契约预览](https://hub.vectorcontrol.tech/zh/docs/adapters): 以下 Agent Adapter SDK 示例在公开 Go SDK 包稳定前仅作说明。它们描述 Edge Server 内的 Agent Runtime adapter 契约，不承诺当前已有稳定 import path。
- [API 与事件](https://hub.vectorcontrol.tech/zh/docs/api-reference): AgentHub 的公开契约分为 REST API、WebSocket event、Runtime adapter event 和 IM integration event。当前文档描述稳定方向和边界；具体 OpenAPI、事件 schema 和 SDK 包仍在开发中。
- [飞书/Lark 集成](https://hub.vectorcontrol.tech/zh/docs/feishu): AgentHub 把飞书/Lark 作为协作入口：机器人消息、事件订阅、交互卡片，以及 H5/工作台入口。产品登录和账号绑定仍归 TokenDance ID。
- [AgentHub 文档](https://hub.vectorcontrol.tech/zh/docs/overview): AgentHub 是 TokenDance 的 IM 式多 Agent 协作平台。用户把 AI Agent 作为队友加入群聊。三个原生客户端——Desktop（Tauri 2）、Web、Mobile（Expo RN）——共享由 Hub 和 Edge 支撑的 v4 工作台。
- [产品状态](https://hub.vectorcontrol.tech/zh/docs/product-status): AgentHub 公开状态地图，区分已上线的官网/文档、可本地预览的产品链路，以及仍在开发中的能力。
- [快速上手](https://hub.vectorcontrol.tech/zh/docs/quickstart): 本指南先跑通本地预览链路：AgentHub Desktop -> Local Edge -> Runtime Adapter，再加 Web（端口 5174）。Mobile Expo RN 是独立路径。
- [安装与本地环境](https://hub.vectorcontrol.tech/zh/docs/installation): AgentHub Desktop（Tauri 2，端口 5173）、Web（端口 5174）、Mobile（Expo RN，端口 5177）、Local Edge、Hub Server 和 runtime adapter 的本地开发环境说明。
- [核心概念](https://hub.vectorcontrol.tech/zh/docs/concepts): 本页定义 AgentHub 文档里反复出现的术语，并明确哪些能力已经可预览、哪些仍在开发。
- [术语表](https://hub.vectorcontrol.tech/zh/docs/glossary): 阅读 AgentHub 文档、issue 和发布记录时使用本术语表。目标是让产品、runtime、身份和部署术语保持精确。
- [工作流](https://hub.vectorcontrol.tech/zh/docs/workflows): 本页把 AgentHub 的概念落到真实工作场景：本地运行、团队可见审查、Hub 协作、飞书/Lark 入口、Runtime adapter 开发和发布证据。
- [使用 Cookbook](https://hub.vectorcontrol.tech/zh/docs/usage-cookbook): 这份 cookbook 把 AgentHub 的架构、API、Desktop、Hub/Edge 和发布文档转成任务配方。你已经知道要做什么时，从这里找最短且安全的执行路径。
- [Desktop 使用手册](https://hub.vectorcontrol.tech/zh/docs/desktop): AgentHub Desktop 是 Tauri 2 原生本地工作台，用来运行、审查和批准 Agent 工作。它与 Web 和 Mobile 共享同一套工作台 UI。
- [Desktop UI 参考](https://hub.vectorcontrol.tech/zh/docs/desktop-ui): AgentHub Desktop 是 Tauri 2 原生本地可见 Agent 工作的控制界面。它渲染来自 the v4 shared workbench 的 v4 共享工作台。本页映射预期 UI 区域、状态和交互。
- [配置](https://hub.vectorcontrol.tech/zh/docs/configuration): AgentHub 的配置按职责分层。本地执行配置靠近 Desktop/Edge，身份和团队配置放在 Hub，provider 凭据不能进入前端代码。
- [身份与登录](https://hub.vectorcontrol.tech/zh/docs/identity-login): AgentHub 使用 TokenDance ID 作为身份权威。AgentHub Home 公开站点的登录按钮应把用户带到 TokenDance ID，而不是自己实现一套本地密码登录卡片。
- [安全边界](https://hub.vectorcontrol.tech/zh/docs/security): AgentHub 的安全模型把身份、产品权限、本地执行、IM 事件和模型 API 凭据分开处理。公开文档只描述边界和原则，不记录生产主机、secret、回滚路径或私有证据。
- [数据与隐私](https://hub.vectorcontrol.tech/zh/docs/data-privacy): AgentHub 会连接本地文件、runtime 输出、团队审查和产品身份。本页说明数据应该归谁、公开文档能写到哪里、哪些内容必须留在本地、服务端或私有运维文档中。
- [运维 Runbook](https://hub.vectorcontrol.tech/zh/docs/operations-runbook): 本 Runbook 覆盖 AgentHub 公开站点、文档、本地预览和集成证据。它刻意保持 secret-free：生产主机路径、回滚命令、key 和私有日志属于私有运维 workspace。
- [部署](https://hub.vectorcontrol.tech/zh/docs/deployment): 本页说明 AgentHub Home 和文档站的公开部署边界。它故意不写私有主机路径、SSH alias、回滚命令和 secret。
- [排障指南](https://hub.vectorcontrol.tech/zh/docs/troubleshooting): 本页按症状列出 AgentHub 官网、Desktop/Web、Hub/Edge、Runtime adapter 和 Feishu/Lark 集成的排查路径。
- [FAQ](https://hub.vectorcontrol.tech/zh/docs/faq): 本页回答常见产品、设置、身份、runtime 和文档问题。
- [发布检查](https://hub.vectorcontrol.tech/zh/docs/release-checklist): 发布 AgentHub Home、文档或公开包装变更前使用这份清单。目标是让公开文档真正可用，同时避免把私有部署细节带进公开仓库。
- [贡献指南](https://hub.vectorcontrol.tech/zh/docs/contributing): AgentHub 迭代很快，所以贡献不仅要看代码质量，也要守住产品边界。本页说明如何选择工作、提交什么证据，以及如何避免把开发中的产品想法写成公开上线承诺。
- [路线图](https://hub.vectorcontrol.tech/zh/docs/roadmap): 本页说明 AgentHub 能力的公开状态。这里刻意保守：只有实现、测试、文档和可见验证证据齐全后，能力才会标为 stable。
- [设计系统](https://hub.vectorcontrol.tech/zh/docs/design-system): AgentHub Home 遵循 TokenDance 共享设计契约，同时保留 AgentHub Desktop 工作台的产品气质。本页记录公开站点的设计规则，让首页、文档、mock UI、图标和动效保持一致。
- [AgentHub 与其他方案对比](https://hub.vectorcontrol.tech/zh/docs/comparison): 本页说明 AgentHub 与相邻工具的产品方向差异，不表示表中所有 AgentHub 能力都已经生产可用。
- [更新日志](https://hub.vectorcontrol.tech/zh/docs/changelog): 本页记录公开官网、文档系统和 AgentHub 产品线的高层开发节点。具体实现提交、tag 和验证证据仍以 AgentHub 仓库的 release notes 与 roadmap 为准。

## Agent Notes

- [AgentHub](https://hub.vectorcontrol.tech/en/docs/concepts): multi-agent collaboration platform; TokenDanceCode owns local coding-agent execution and SDK delivery
- [Hub and Edge architecture](https://hub.vectorcontrol.tech/en/docs/architecture): Hub Server provides API/WebSocket backend; Edge Server handles relay and local execution routing
- [Data and privacy](https://hub.vectorcontrol.tech/en/docs/data-privacy): public-safe boundaries; do not infer private deployment paths, server IPs, provider secrets, admin tokens, or rollback commands