AgentHub Documentation
AgentHub is TokenDance's multi-agent engineering collaboration product line. It connects AgentHub Desktop, the Web workbench, Hub Server, Edge Server, and Agent Runtime adapters so that coding agents such as Claude Code, Codex, and OpenCode can work inside visible team workflows.
Current status
AgentHub is under active development. The public website and docs are live; Desktop + Local Edge is the preview-ready local path; Hub Server and Web workbench are in progress; Feishu/Lark production integration, Remote/Cloud Edge, full Web + Hub + Edge routing, and several database-backed surfaces are still in development.
Start Here
If you are new to AgentHub, choose the path that matches your role, then use the ordered list as the full tour.
| Reader | Read first | Outcome |
|---|---|---|
| Product evaluator | Product Status -> Comparison -> Roadmap | Understand what is live, what is preview-only, and why AgentHub exists alongside CLI tools |
| Local user | Installation -> Desktop Guide -> Quickstart | Run the smallest Desktop -> Local Edge -> Runtime adapter path safely |
| Runtime integrator | Agent Profiles -> Run Lifecycle -> Adapters -> API And Events | Map a runtime into AgentHub's event, approval, diff, and artifact model |
| Team/workflow owner | Collaboration -> Hub And Edge -> Web Workbench -> Feishu/Lark Integration | Plan shared sessions, Web review, Hub routing, IM entry points, and evidence |
| Release owner | Security -> Operations Runbook -> Deployment -> Release Checklist | Verify docs, visual QA, SEO, public discovery files, and safe release wording |
Full recommended reading order:
- Concepts: understand Desktop, Web, Hub, Edge, Agent Profile, Runtime adapter, Run, and Event.
- Product Status: separate live, preview-ready, contract-shaped, in-progress, and in-development capabilities.
- Quickstart: start the smallest local flow and verify Desktop, Local Edge, and a runtime adapter can work together.
- Installation: prepare a workstation with Git, Go, Node.js, pnpm, Local Edge, Desktop, and a safe runtime path.
- Glossary: align product, runtime, identity, integration, and release terms.
- Workflows: map local runs, reviewable diffs, team collaboration, Feishu/Lark tasks, adapters, and releases to concrete evidence.
- Usage Cookbook: follow concrete recipes for read-only reviews, reviewable diffs, adapter comparison, failed-run triage, team task prep, Feishu/Lark prep, and docs releases.
- Desktop Guide: understand the local workbench, runtime selector, diff review, approvals, and QA evidence.
- Desktop UI Reference: review layout, run states, selectors, diff panels, motion, and screenshot QA.
- Configuration: review local, Hub/Web, runtime profile, and secret ownership before wiring real credentials.
- Identity And Login: confirm TokenDance ID login, callback, browser state, and authorization boundaries.
- Architecture: learn the Hub / Edge / Desktop / Web responsibility boundaries.
- Hub And Edge: check the collaboration/execution split, routing, event contract, and integration entry boundary.
- Web Workbench: understand Hub-backed Web surfaces, local-file boundaries, review flow, and evidence.
- Agent Profiles: define profile metadata, capabilities, approval policy, and adapter boundaries.
- Collaboration: map shared sessions, team roles, approvals, integration entries, and evidence.
- Run Lifecycle: follow run states, event envelopes, approval gates, artifacts, diffs, and failure codes.
- API And Events: review the public REST, WebSocket event, and runtime adapter contract boundaries.
- FAQ: answer common product, setup, identity, runtime, integration, and release questions.
- Design System: follow TokenDance Blue, Desktop mock, icon, motion, and visual QA rules.
- Deployment: use the static-export, smoke, and stale-page triage guide.
Documentation Map
| Area | What it covers | Status |
|---|---|---|
| Concepts | Terms, product surfaces, delivery status, and boundaries | Living document |
| Product Status | Live, preview-ready, contract-shaped, in-progress, and in-development capability map | Living document |
| Glossary | Product, runtime, identity, integration, and release terminology | Living document |
| Workflows | Local runs, diff review, collaboration, Feishu/Lark, adapter, and release workflows | Living document |
| Usage Cookbook | Practical recipes for read-only reviews, diff review, adapter comparison, failed-run triage, team tasks, Feishu/Lark prep, and docs releases | Living document |
| Installation | Workstation setup, runtime CLI preparation, local ports, verification, and first failure triage | Living document |
| Desktop Guide | Desktop surface map, runtime controls, diff review, approvals, theme/language evidence | Living document |
| Desktop UI Reference | Layout model, run states, selectors, runtime picker, diff panels, motion, and screenshot QA | Living document |
| Quickstart | Local preview, configuration, and first agent task | Preview-ready |
| Configuration | Local Edge, Hub/Web, runtime profile, and secret ownership | Living document |
| Identity And Login | TokenDance ID login flow, callback, browser state, authorization boundary, and UI rules | Living document |
| Architecture | Hub, Edge, Desktop, Web, runtime adapters, and event flow | Preview-ready |
| Hub And Edge | Hub/Edge responsibility split, routing, event contract, and integration entries | Living document |
| Web Workbench | Hub-backed Web surfaces, local-file boundary, review flow, UI states, and evidence | In progress |
| Agent Profiles | Profile model, capability vocabulary, selection rules, approval policy, and adapter boundary | Contract shaped |
| Collaboration | Shared sessions, review/approval flow, team roles, integration entries, and evidence | In progress |
| Run Lifecycle | Run state machine, event envelope, approval gates, artifacts, diff metadata, and failure codes | Contract shaped |
| Adapters | Claude Code, Codex, OpenCode, and custom adapter contracts | Contract shaped, public SDK not stable |
| API And Events | Hub API, Edge API, WebSocket events, adapter events | In development |
| Feishu/Lark Integration | Bot, events, cards, H5/workbench, TokenDance ID binding | In development |
| Security | TokenDance ID, Hub-local permissions, secrets, sandbox, and audit | Living document |
| Operations Runbook | Public-site checks, docs route release gate, visual QA, smoke, and failure triage | Living document |
| Deployment | Release source, local build, static export, live smoke, and stale-page triage | Living document |
| Troubleshooting | Setup, login, runtime, Feishu, and static-site failures | Living document |
| FAQ | Product, setup, identity, runtime, integration, docs, and release questions | Living document |
| Release Checklist | Docs, SEO, visual QA, security, and deployment gates | Living document |
| Roadmap | Capability status and conservative release language | Living document |
| Design System | TokenDance Blue, component rules, Desktop mock, motion, icon, and visual QA guidance | Living document |
| Comparison | Positioning against CLIs, chat UIs, and single-agent tools | Living document |
| Changelog | Public docs and product-site changes | Living document |
What AgentHub Is
Most AI coding tools start as a private terminal session: one person launches the agent, watches the logs, and decides whether the result is useful. AgentHub gives that work shared state, review steps, and records that a team can inspect.
In the current design:
- AgentHub Desktop is the local workbench. It connects to Local Edge and is suited for personal development and local execution.
- AgentHub Web is the Hub-backed collaboration workbench for multi-device, team, IM, and remote workflows.
- Hub Server owns identity sessions, projects, devices, IM entry points, sync, and audit.
- Edge Server owns workspaces, run lifecycle, runtime adapters, diff, artifacts, and preview events.
- Runtime adapters host real execution engines such as Claude Code, Codex, and OpenCode.
AgentHub is a controlled workbench for agent work. It shows who requested a task, which runtime executed it, what files changed, which approvals were requested, what record was produced, and what can be reviewed later.
Current Boundaries
You can develop and preview these areas today:
- Desktop connects to Local Edge and can validate mock / Claude Code / Codex / OpenCode preset execution flows.
- Web can run as a Hub-only preview surface. It does not start local CLI processes or bypass the Hub to connect directly to Local Edge.
- Edge Server has the runtime adapter structure and local execution boundaries.
- Hub Server has local development paths for OIDC code exchange, Hub sessions, device routing, and task routing.
Still in development:
- Feishu/Lark production event ingress, card schema, async queues, and account-binding flow.
- Remote/Cloud Edge, device proof, workspace allowlist, and relay/provisioning.
- Database-backed Contacts, Docs, Tasks, Projects, and Settings surfaces.
- Production-grade full Web + Hub + Edge routing E2E verification.
- Public third-party Adapter SDK package and ecosystem submission flow.
When a page says "preview" or "in development", treat that wording literally. Public docs should help contributors and early users understand the intended system without implying that every surface is generally available.
Identity
TokenDance ID is the identity authority for AgentHub. AgentHub does not own a direct GitHub, Google, or Feishu social login, and Feishu OAuth must not be treated as product login. Hub Server can issue AgentHub-local sessions and enforce product permissions; low-risk Desktop/Web personalization is not a Hub API authorization boundary.
Next Step
Continue with Concepts, map your scenario in Workflows, then run the local path in Quickstart.