Two complementary surfaces help builders and agents find what to do next on AgentStack: Compass (⌘K omnibox) and Discovery Hub (capability map).
Where: Developer and User shells — keyboard ⌘K (Ctrl+K on Windows).
What it does:
- Ranks routes, playbooks, and micro-paths (T0–T5 priority bands).
- Deep-links into project hubs (CRM, hosting, storefront, wallet).
- Surfaces playbooks (multi-step guided flows) and capability tasks (≤3 MCP actions).
Compass replaces the legacy raw command palette in dual-shell mode. Integrators do not call Compass directly — agents use MCP discovery and guidance tools below to mirror the same catalog.
Routes:
| Shell | Path |
|---|---|
| Developer | /dev/discover |
| User | /user/discover |
| Project-scoped | /dev/projects/:id/discover |
Tabs:
- Map — topic clusters (hosting, commerce, agents, support, …).
- Reference — former docs-api leaves and REST/MCP pointers.
Sidebar Discover (G D) is the primary entry in modern shells.
Lists canonical platform routes (shell, route kind, topic cluster). Use before deep-linking users or choosing automation targets.
{
"action": "discovery.get_platform_surfaces",
"params": { "limit": 40 }
}Returns up to 200 rows; default 80.
Lists Platform Task Capability (PTC) atoms — comfort tasks with taskId, domain, and comfortBudget (max MCP actions per task, typically ≤3).
{
"action": "guidance.list_capability_tasks",
"params": {}
}Pair with Compass playbooks where kind=capability — see platform/CAPABILITY_TASKS.md.
- Call
discovery.get_platform_surfacesto enumerate routes for your agent’s allowlist. - Call
guidance.list_capability_tasksto pick atomic tasks (hosting.publish,storage.upload, …). - Execute MCP actions via
agentstack.execute— MCP_QUICKSTART.md.
| Surface | Best for |
|---|---|
| Compass ⌘K | Human operators, playbook nudges |
| Discovery Hub | Browsing capabilities by domain |
discovery.get_platform_surfaces |
Agents building navigation manifests |
guidance.list_capability_tasks |
Agents respecting comfort budgets |