Authenticated AgentStack ships three chrome contexts behind one account:
| Shell | Route prefix | Audience |
|---|---|---|
| User Hub | /user/* |
End users — wallets, messaging, project workspaces |
| Developer Hub | /dev/* |
Builders — APIs, logic, sandboxes, support staff tools |
| Platform | /platform/* |
Ecosystem operators — diagnostics, economy hubs |
| Hosted mini-app | /app/dev/:id, /app/prod/:id |
AI Builder / hosted app shells (not the main dashboard chrome) |
Navigation picks a shell using audience + capabilities — not duplicated accounts.
Your REST and MCP tokens are unchanged across shells; only which shortcuts appear in the hosted UI differs.
Human-readable design constraints (mobile-first 320 px, tap targets): see the dual-shell design doc on GitHub docs (DESIGN_LANGUAGE_DUAL_SHELL.md in the AgentStack repository).