Product Status
This page is the public status map for AgentHub. It separates the website and docs that are live, the local product paths that can be previewed, and the capabilities that are still being built.
Status vocabulary
Use the exact status words below in public docs, release notes, and homepage copy. Do not turn a preview or in-development capability into a launch claim without implementation and smoke-test evidence.
Status Levels
| Status | Meaning | Public wording |
|---|---|---|
| Live | Public surface is deployed and can be opened by users | "is live", "available" |
| Preview-ready | Works as a local or controlled preview path, usually with setup constraints | "can be previewed", "preview path" |
| Contract shaped | Interface direction exists, but SDK/package/compatibility is not stable | "contract direction", "not stable SDK" |
| In progress | Implementation exists or is being wired, but evidence is incomplete | "in progress", "being productized" |
| In development | Planned or partially implemented; not generally available | "in development", "not yet stable" |
How To Use This Status Map
This page is a public commitment boundary, not a marketing page. Use it to decide what is safe to try now:
| Goal | Recommended path today | Why |
|---|---|---|
| Evaluate the product direction | Read this page, Concepts, and Comparison | Confirm AgentHub is a coordination layer, not a replacement for one CLI |
| Run a local preview | Follow Installation and Quickstart | Desktop + Local Edge + mock runtime is the safest preview path |
| Connect a real runtime | Read Agent Profiles, Run Lifecycle, and Adapters | Map events, permissions, diffs, and failures before packaging an SDK |
| Plan team workflows | Read Hub And Edge, Web Workbench, and Collaboration | Web/Hub routing and audit are still being productized |
| Plan Feishu/Lark | Read Feishu/Lark and Security | Feishu/Lark is a collaboration entry; identity still belongs to TokenDance ID |
If a capability is marked "in development" here, homepage copy, FAQ, roadmap, and README should keep using conservative wording. Promote the status only after implementation, tests, screenshots, or smoke evidence can be reproduced.
Public Surfaces
| Surface | Current status | Notes |
|---|---|---|
| AgentHub Home | Live | Product homepage, bilingual copy, Desktop-style mock, TokenDance ID login entry |
| AgentHub Docs | Live | Bilingual documentation, docs search, TOC, sitemap, llms.txt |
| TokenDance ID redirect | Live as identity entry | Login redirects to TokenDance ID; public site session is low-risk personalization only |
| Public GitHub link | Live | Points to TokenDanceLab/AgentHub; implementation details remain in the repository |
Public surfaces can be called live only when the route opens, the localized copy renders, discovery files link to it, and cache-busting smoke confirms the currently deployed version. A local build alone is not a live claim.
Product Surfaces
| Surface | Current status | What is safe to say |
|---|---|---|
| AgentHub Desktop | Preview-ready local path | Local workbench for workspace selection, runtime controls, diff/file review, approvals, theme, and language |
| Local Edge | Preview-ready local path | Owns local workspace policy, runtime adapter startup, run lifecycle, events, diffs, artifacts, and previews |
| Runtime adapters | Contract shaped | Claude Code, Codex, OpenCode, and custom runtimes connect through adapter boundaries |
| Hub Server | In progress | Owns TokenDance ID sessions, projects, devices, task routing, and audit for team workflows |
| Web workbench | In progress | Hub-backed collaboration surface; does not bypass the Hub to access Local Edge or local files |
| Feishu/Lark integration | In development | Collaboration entry for bot, events, cards, H5/workbench, async queues, and TokenDance ID binding |
| Remote/Cloud Edge | In development | Requires device identity, target authorization, relay/provisioning, workspace policy, and audit evidence |
| Public third-party Adapter SDK | In development | Do not describe as a stable ecosystem submission path yet |
Use this table as the source of truth for homepage copy. If a marketing section mentions Web, Feishu/Lark, Remote Edge, or third-party adapters, it should repeat the status language here rather than smoothing it into a launch claim.
Current Evidence
This table records what the public docs can point to without exposing private deployment state. It is deliberately conservative: a missing evidence cell means the capability should stay at its current status.
| Surface | Last public verification | Evidence public readers can check | Missing before promotion |
|---|---|---|---|
| AgentHub Home | 2026-06-09 | Live /en and /zh routes, TokenDance Blue homepage, localized navigation, sitemap, robots.txt, llms.txt | Keep release tag and visual QA evidence current for each public deploy |
| AgentHub Docs | 2026-06-09 | Bilingual docs routes, sidebar, TOC, docs search, GFM tables, localized sitemap alternates | Automated MDX heading/search extraction and route drift checks |
| TokenDance ID login entry | 2026-06-09 | Login redirects into TokenDance ID; static-site session remains low-risk personalization | Hub-owned product session proof before claiming Hub API authorization |
| Desktop + Local Edge | 2026-06-09 | Mock-first quickstart, Desktop UI reference, local Edge health checks, run lifecycle vocabulary | Packaged cross-platform release, visual QA for real runtime paths, installer evidence |
| Runtime adapters | 2026-06-09 | Adapter contract preview, event vocabulary, failure-code guidance, Claude Code/Codex/OpenCode positioning | Published SDK/package, conformance tests, versioning policy, third-party submission rules |
| Hub Server | 2026-06-09 | Architecture, Hub/Edge boundary, authorization model, Web workbench status language | Public E2E evidence for Hub session, project permissions, device routing, audit replay |
| Web workbench | 2026-06-09 | Hub-backed design boundary, local-file denial rule, review flow docs | Production routing evidence, database-backed surfaces, target authorization screenshots |
| Feishu/Lark integration | 2026-06-09 | Integration boundary, event names, card action timing, TokenDance ID binding rule | Tenant app setup evidence, HTTPS gateway smoke, retry/dedup proof, failure cards |
| Remote/Cloud Edge | 2026-06-09 | Architecture requirements and safety wording only | Device proof, relay/provisioning, workspace policy, target authorization, audit chain |
Capability Boundary Matrix
| Capability | Safe public description | Do not promise yet | Evidence needed to promote |
|---|---|---|---|
| Desktop + Local Edge | Local preview for tasks, events, diff/file review, approvals, theme, and language | One-click installer, cross-platform release, every runtime fully automated | Desktop screenshots, run event trace, real-runtime smoke, failure-state screenshots |
| Runtime adapters | Adapter contract direction for Claude Code, Codex, OpenCode | Stable third-party SDK, marketplace submission flow, compatibility SLA | Conformance tests, version policy, example adapter, breaking-change rules |
| Hub/Web | Hub-backed collaboration model and Web surface are being productized | Web directly starts local CLI, Web bypasses Hub to access Local Edge or files | Hub session, device routing, target authorization, audit screenshot, E2E trace |
| Feishu/Lark | Collaboration entry for bot/event/card/H5/workbench is in development | Feishu OAuth replaces TokenDance ID login, cards carry full prompts or secrets | HTTPS gateway, callback under 3 seconds, queue retry, account binding, failure states |
| Remote/Cloud Edge | Target architecture and safety requirements are defined | Arbitrary remote workspace execution, relay without device proof, unaudited file access | Device proof, workspace allowlist, target authorization, relay/provisioning, audit chain |
Release Evidence
Before a status moves upward, collect evidence:
- Live: deployed route, cache-busting smoke URL, HTTP status, rendered keyword, discovery-file coverage, and rollback owner in private ops docs.
- Preview-ready: reproducible local command sequence, screenshot or test output, expected success criteria, and known constraints.
- Contract shaped: interface document, event examples, error semantics, compatibility notes, and implementation references.
- In progress: owning repo/area, current blocker, missing evidence, and public wording that does not overpromise.
Evidence should include both language variants when the surface is public. For UI surfaces, keep desktop and mobile screenshots, theme/language states, and at least one failure-state screenshot where the user needs to make a decision.
Public Wording Examples
| Scenario | Prefer | Avoid |
|---|---|---|
| Local preview | "Desktop + Local Edge local preview path can be exercised" | "AgentHub is fully available" |
| Web | "The Web workbench is Hub-backed and production routing is in progress" | "Web can directly run local CLIs" |
| Feishu/Lark | "Feishu/Lark is in development as a collaboration entry" | "Feishu login for AgentHub" |
| Adapter | "Adapter contract is shaped; public SDK is not stable" | "Third-party runtimes can publish plugins today" |
| Remote execution | "Remote/Cloud Edge is a planned controlled execution path" | "Agents can run remotely on any machine" |
Do Not Claim Yet
These claims need more evidence before public copy can use them:
- "Remote Edge is available for any workspace."
- "AgentHub Web can run local CLI agents directly."
- "Feishu OAuth is AgentHub login."
- "The Adapter SDK is stable for third-party marketplace submissions."
- "TokenDance API keys are the same as TokenDance ID sessions."
Prefer narrower wording until evidence exists: "local preview path", "Hub-backed design direction", "contract direction", "integration in development", or "planned remote-edge path".
Update Rules
When this page changes, update:
- Roadmap for milestone wording.
- Architecture if component responsibilities changed.
- Release Checklist if the evidence gate changed.
public/sitemap.xmlandpublic/llms.txtwhen the route set changes.