Skip to content

Route map

The app shell (ControlCenterLayout) wraps every in-workspace route via a ShellRoute. Every in-shell destination is workspace-prefixed — /workspaces/:workspaceId/… — and the workspace id in the URL is the single source of truth for the active workspace. Only the pre-context surfaces have no prefix: /splash, /onboarding and the bare /workspaces picker, all full-screen and outside the shell.

The gate is complete when at least one forge is connected for the signed-in user and at least one workspace exists.

A missing credential and a missing setup are treated differently, and the discriminator is users.onboarding_finished_at read off the caller’s own identity.me — never “workspaces exist”, which is wrong the moment someone is invited into a workspace they never created. With no forge connected, an account that has onboarded stays in the app: the workspace shell shows a warning with a link to Settings → You → Profile, where the sign-in lives. One that has not onboarded goes to /onboarding. While the flag is still unknown the guard holds the splash rather than guessing, because it never redirects back out of onboarding.

Path Screen
/splash Startup splash that resolves the onboarding gate
/onboarding Connect a forge, create or join a workspace, sandbox, default adapter, then voice. The workspace step is dropped when the account already belongs to one
/workspaces Workspace list and picker
/workspaces/:workspaceId Redirects to /workspaces/:workspaceId/inbox

Paths below omit the /workspaces/:workspaceId prefix.

Path Query params Screen
/inbox — Unified inbox: PRs classified by review lifecycle plus non-PR work blocking the operator. The post-guard landing route; a bare /workspaces/:workspaceId redirects here
/spaces — Space surface, no space selected
/spaces/:spaceId ?m=<messageId>, ?tab=<key> One space; m deep-links to a message and is consumed once on open
/tickets — Ticket board
/tickets/:ticketId — Ticket master-detail
/projects/:projectId — Project overview
/pull-requests ?repo=<owner/name> PR list; repo selects that repository in the left rail
/pull-requests/compose ?space=<spaceId> Compose a new pull request; space names the space whose isolated worktree supplies the branch
/pull-requests/:owner/:repo/:prNumber ?tab=<key>, ?comment=<id> PR detail with diff viewer; comment is the numeric REST id of one comment
/pipelines — Pipeline run list
/pipelines/run ?templateId=<id> Manual run launcher
/pipelines/:runId — Pipeline run detail (step timeline)
/plans — Plan Studio hub: active plans, plan documents, playbooks
/plans/:kind/:id — Plan Studio for one plan; kind is orchestration or document
/meetings — Meetings list
/meetings/record — Live meeting recording screen
/meetings/:meetingId — Meeting detail: notes, transcript, action items, decisions
/calendar — Calendar: month, week and agenda views
/calendar/:eventId — Calendar event detail (sibling route; shares the calendar page key)
/newsfeed — Newsfeed list
/newsfeed/article/:articleId — Article reader
/observability — Observability hub: Usage, Insights, Live and Quality tabs over the workspace run-log feed. Defaults to the Usage tab
/users/:login — GitHub user profile
/teams/:organization/:slug — GitHub organisation team profile
/api-keys — API key management. No navigation entry point — reachable only by URL
/settings/… — Settings screens (below)

Conversations and threads have no route of their own — a thread is a conversation inside /spaces/:spaceId, opened as an editor tab rather than addressed by URL.

There is no /dashboard route and no dashboard screen. The analytics surface is /observability, reached from the sidebar footer.

There is no “Plans” sidebar item. Plan Studio opens as an editor tab from the plan’s row in the conversation that produced it; /plans and /plans/:kind/:id are deep links.

/observability and /pull-requests/compose have no entry in the route-title or breadcrumb registries, so both show the bare app name in the window title and no breadcrumb trail.

/settings redirects to /settings/you/profile. The sidebar’s settings button and Cmd/Ctrl + , both go to /settings/you/profile.

Settings paths are namespaced by scope — you/, workspace/, server/ — because the segment states who a change affects. Two paths predate the namespacing and are not scoped in the URL: /settings/memory and /settings/pipelines.

Path Screen
/settings/you/profile Your account on this server: name, username, picture and sign-in (the settings landing)
/settings/you/profile?section=accounts Connected accounts: your own code hosting, ticketing, calendar and chat sign-ins, and ticket drafts from chat
/settings/you/appearance Theme, language, typography, editor theme
/settings/you/audio Microphone, dictation, meeting detection and soundscape output
/settings/you/notifications Per-event toggles, quiet hours
/settings/you/commits Who is credited on commits from work you start, and your commit signing key
/settings/you/desktop Desktop app only: the tray icon, closing the window and opening at login
/settings/you/devices Paired phones and remote control
/settings/you/newsfeed Feed management: sources, refresh, read state
/settings/you/links Where links from outside Control Center open
Path Screen
/settings/workspace/profile Profile and identity in this workspace: name, email, git author
/settings/workspace/general Name, logo, secret globs, review concurrency, branch naming, danger zone
/settings/workspace/integrations Connect choice, the GitHub App and automation tokens, ticketing vendor and automation, sync health, the workspace’s own provider apps, chat bridges, GIFs. Each provider group names your own account and links to Connected accounts
/settings/workspace/meetings Meeting note templates and saved voice profiles
/settings/workspace/members Roster and invites
/settings/workspace/repositories Repositories registered in this workspace
/settings/workspace/environments Environment definitions: what spaces can start and the tasks their worktrees run
/settings/workspace/agents Registered agent identities
/settings/workspace/skills Skill configuration
/settings/memory Workspace memory: facts, policies, knowledge graph
/settings/workspace/permissions Agent permissions: guardrail matrix and what-if probe
/settings/pipelines Pipeline templates
/settings/pipelines/:templateId Pipeline template editor (drag-and-drop canvas)
Path Screen
/settings/server/connection Connection and status
/settings/server/sso Single sign-on (SAML, OIDC, SCIM provisioning)
/settings/server/providers Model providers and adapters
/settings/server/mcp Built-in and external MCP servers
/settings/server/voice Voice and meeting models (ASR, diarisation)
/settings/server/rigs Rigs: what this host can boot, base images, custom images, running machines
/settings/server/sandbox Sandbox exec grants: programs agents may run from their working copy of your repositories
/settings/server/diagnostics Diagnostics and privacy: sandboxing, embedding, logging, crash reporting
/settings/server/people People on this server and whether each address is confirmed (server owner only)
/settings/server/audit Audit log: the server’s, and the workspaces you administer
/settings/server/backup Backup and restore: install snapshots, per-workspace export, import and delete
/settings/server/about About and updates

kSettingsNav in lib/features/settings/settings_nav.dart is the single source of truth for this list. settings_nav_test.dart pins unique ids, unique routes, flattened J/K order and the three scopes. It does not walk every registered GoRoute.

Concern File
Router lib/router/app_router.dart
Route builders lib/router/routes.dart
Auth guards lib/router/guards.dart
Onboarding gate lib/features/auth/providers/onboarding_providers.dart
Settings navigation lib/features/settings/settings_nav.dart