Skip to main content
AKOS

Route-only screens

Deep-linkable screens that are not in the sidebar — how to reach them from their owner surfaces.

View canonical source

Some screens stay routable (command palette, deep links, notifications) but were removed from the sidebar once their owner surface shipped (issue #3897). They are not hidden — assistants and the palette can still navigate to them by id.

How to open any screen

Press Cmd K / Ctrl K and type the screen id or a keyword (for example plugins, config, coding).

Screen index

Screen idLabel / purposeReach from
configWorkspace settings (copilot, orchestration, privacy, export/import)Top-bar Settings button
pluginsInstalled plugin lifecycleMarketplace › Installed › Manage plugins
bundlesBundle import/export historyGeneral › Export/Import › Full bundle history
topologiesMulti-agent collaboration templatesAgents › How agents collaborate
toolsRuntime tools registry sectionsGeneral runtime sections, or Tools
sandboxSandbox policy shortcutsSecurity or General runtime sections
codingCoding-agent providers and runTaskAgents or Coding guide
templatesStarter flow templates browserWorkflows template picker, or palette templates
oemBrand & licensing (OEM entitlement)Settings › Brand & licensing (when entitled)
flow-editorFull-page flow editorWorkflows — open a flow

Brand & licensing (oem)

Available when your workspace has the OEM entitlement. Open via Settings › Brand & licensing or the command palette (oem).

Typical tabs:

AreaWhat you do
LicenseImport a signed license envelope and review validity / grace state.
TenantsIssue, suspend, or revoke tenant licenses (operator workflows).
Brand kitEdit tokens, logos, and white-label runtime projection.
Vertical packsBrowse and apply OEM vertical YAML packs to the workspace.
Marketplace publishExport/import bundles for the marketplace catalog (publisher permissions).

Cloud-hosted OEM operators also use the separate admin console (apps/admin/) for tenant-wide control; desktop oem is the workspace-local brand + licensing surface.

Aliases (also not sidebar items)

Screen idLands on
runs, traces, observabilityActivity (or Traces / Observability standalone)
audit, break-glassAccess (Governance pillar)
NeedGo to
Owner surfaces (flows, agents, workspace)Using the App index
Sandbox / egress policy detailSecurity
MCP and egress editorTools
Marketplace pluginsMarketplace

For contributors

Route-only screens also have agent implementation guides in the repository contributor docs. Use the internal docs query CLI from a dev checkout (pnpm docs:internal:query screen <id> --agent).

On this page