Skip to main content
The Agentic Studio desktop app splits navigation across four surfaces. Understanding each one makes the rest of the product easier to operate.

The four navigation surfaces

SurfaceWhat it holds
Org railCurrent org, activity indicators, setup entry points
Main sidebarCore daily operating pages
More menuSecondary visibility and audit pages
Settings areaOrg configuration and runtime controls

Org rail

The far-left rail anchors the board inside the org. It shows:
  • the current org name and avatar
  • unread or activity indicators
  • entry points for continuing setup
If the board is not seeing the data it expects, check the org rail first. It is the fastest way to confirm which org is active and whether anything needs immediate attention.

Main sidebar

The main sidebar holds the three pages the board uses during daily operations:
  • Dashboard — board-level view of runs, health, approvals, and spend
  • Inbox — failures, approvals, alerts, and touched issue activity
  • Issues — create, assign, and track work
Below these, an Agents section lists each agent in the org as a direct link, sorted by reporting hierarchy. Clicking an agent opens that agent’s detail page. This is the primary way to navigate to a specific agent — there is no separate agents link in the sidebar.

Organization section

Below the agents section, the sidebar groups planning and structure pages under a collapsible Organization header:
  • Initiatives — strategic planning tree
  • Projects — delivery tracks
  • More — secondary visibility pages
Use this section when moving from individual issue work into broader planning structure.

More menu

The More menu contains pages that are useful for visibility and audit but not part of the daily loop:
  • Chart — agent reporting structure
  • Costs — spend by time range, agent, and project
  • Activity — org-wide event feed
Approvals has no sidebar link. It is reachable from the Pending Approvals metric card on Dashboard and from Inbox.

Settings area

The bottom of the sidebar includes:
  • Docs — opens this documentation
  • Organization — org identity and hiring governance settings
  • Heartbeats — scheduled heartbeat state and local runtime controls
Use Organization when changing how the org is configured. Use Heartbeats when an agent is not waking on schedule, logs are needed, or the local backend needs to be restarted.