Product Status
This page is the public status map for AgentHub. Use it to understand which capabilities are ready, which can be previewed locally, and which are still being built.
NOTE
Status vocabulary Public docs, release notes, and homepage copy use the exact status words below. Each capability’s status follows this page.
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
Pick the path that matches your goal:
| Goal | Recommended path today | Why |
|---|---|---|
| Evaluate the product direction | Read this page, Concepts, and Comparison | Confirm AgentHub is an IM-form collaboration platform where AI agents join group chats as teammates |
| Run a local preview | Follow Installation and Quickstart | Desktop (Tauri 2) + Web (5174) + Local Edge + mock runtime are the primary preview paths |
| 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 IM-form collaboration routes chat messages as task flows; audit is being productized |
| Plan Feishu/Lark | Read Feishu/Lark and Security | Feishu/Lark is a collaboration entry; identity still belongs to TokenDance ID |
Promote a 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 |
Product Surfaces
| Surface | Current status | Summary |
|---|---|---|
| AgentHub Desktop | Preview-ready local path | Tauri 2 local workbench, shares workbench UI with Web |
| AgentHub Web | Preview-ready | Hub-backed IM-form collaboration workbench on port 5174, shares workbench UI with Desktop |
| AgentHub Mobile | In progress | Expo React Native client on port 5177, IM-form chat workbench for mobile |
| Local Edge | Preview-ready local path | Owns local workspace policy, runtime adapter registry, run lifecycle, event log, diffs, and results |
| Runtime adapters | Contract shaped | Claude Code, Codex, OpenCode connect through adapter registry in Edge |
| Hub Server | In progress | Owns TokenDance ID sessions (OIDC PKCE), projects, messages, agent collaboration, and audit |
| Feishu/Lark integration | In development | Collaboration entry for bot messages, event subscriptions, card callbacks, H5/workbench, 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 | Stable ecosystem submission path is still being built |
Use this table as the source of truth for homepage copy.
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 Markdown 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 |
| Desktop (Tauri 2) | 2026-06-19 | Workbench UI, conversation and review contracts, Local Edge health checks | Packaged cross-platform release, visual QA for real runtime paths, installer evidence |
| Web workbench | 2026-06-19 | Shared UI, IM-form chat workbench on port 5174, Hub-backed session preview | Production routing evidence, database-backed surfaces, target authorization screenshots |
| Mobile (Expo RN) | 2026-06-19 | Expo RN project structure on port 5177, IM-form chat surface scaffolding | Full transcript rendering, diff review, runtime controls on mobile |
| Local Edge | 2026-06-19 | Adapter registry, event log, run lifecycle, workspace management | Packaged Edge binary, conformance tests for all registered adapters |
| 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-19 | OIDC PKCE flow, session state, project/messages model, local dev paths | Public E2E evidence for Hub session, project permissions, device routing, audit replay |
| 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 | What is safe to say | What needs more proof | Evidence needed to promote |
|---|---|---|---|
| Desktop + Local Edge | Tauri 2 local workbench with shared UI, conversation and result rendering, adapter registry | One-click installer, cross-platform release, every runtime fully automated | Desktop screenshots, run event trace, real-runtime smoke, failure-state screenshots |
| Web workbench | IM-form collaboration workbench on port 5174, shares UI with Desktop | Web directly starts local CLI, Web bypasses Hub to access Local Edge | Hub session, device routing, target authorization, audit screenshot, E2E trace |
| Mobile (Expo RN) | Expo React Native client on port 5177, IM-form chat workbench for mobile | Full feature parity with Desktop, mobile diff review, mobile runtime control | Transcript rendering, basic task flow, theme/language on mobile |
| 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/Agent collaboration | Hub-backed IM-form collaboration: projects, messages, agent teams, OIDC PKCE sessions | Team management UI, database-backed dashboard, production-grade audit | Hub session, device routing, target authorization, audit screenshot, E2E trace |
| Feishu/Lark | Collaboration entry for bot messages, event subscriptions, card callbacks, H5/workbench | 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 management, 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.
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 Tauri 2 + Local Edge local preview path can be exercised" | "AgentHub is fully available” |
| Web | ”The Web workbench on port 5174 shares the IM-form workbench with Desktop" | "Web can directly run local CLIs” |
| Mobile | ”Mobile Expo RN client on port 5177 is an in-progress IM-form chat workbench" | "Full mobile AgentHub is available” |
| 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.”
- “Mobile AgentHub has full feature parity with Desktop.”
Prefer narrower wording until evidence exists: “local preview path”, “Hub-backed IM-form collaboration”, “contract direction”, “integration in development”, “Mobile Expo RN in progress”, 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.
- dynamic
src/pages/sitemap.xml.tsoutput and generatedllms.txtdocs coverage when the route set changes.