Skip to main content

​
The Agents workspace map

/agents is the home of your AI workspace in the Orbit dashboard. Everything you do with AI agents (building, grounding, monitoring, reviewing transcripts) either lives on this page or hangs off it as a dedicated route. This guide is the orientation: what each card and tab is for, when to open it, where the older URLs now go, and which workspace role sees what. For agent concepts and the create-to-deploy lifecycle, use AI agents on Orbit. For the rest of the dashboard, see the dashboard map.

​
The card row

Across the top of /agents, a row of cards links the sibling surfaces that are full workflows of their own rather than tabs inside the hub. The current cards, left to right: The cards are discoverability hops: each target has its own full console, listed again in the cross-hub routes table below.

​
The four canonical tabs

Below the card row, the page is a tab strip. Four tabs do the day-to-day work: A fifth tab, Live, is the deep drill-down for in-flight conversations. It is shown only to owner, admin, and supervisor roles; other roles never see the tab trigger, and navigating to a live conversation directly is refused for them. See Roles on this workspace. Tabs are addressable: selecting one sets ?tab= in the URL, so /agents?tab=conversations opens the hub with Conversations preselected. Use these URLs to point a teammate at an exact surface.

​
Cross-hub routes

Every card and tab has a canonical route, and the hub’s deeper surfaces each have one too. Route for route:

​
Old URLs and redirects

Three legacy addresses forward to the hub automatically, so old bookmarks and deep links keep working: There is no standalone /ai or /agents/conversations page anymore; the hub and its tabs are the canonical surfaces. Bookmark the targets.

​
Roles on this workspace

The console hides tabs and controls your role cannot use, so a missing tab is usually a role question, not a bug. The hiding is a courtesy: the API enforces the same rules server-side, so a direct link to a gated surface returns 403 regardless of what the navigation shows.

​
Troubleshooting

  • A tab or control I expect is missing. Check your workspace role against the table above. The Live tab in particular only renders for owner, admin, and supervisor. Ask an owner or admin to raise your role if the job needs it.
  • I followed a deep link and got a 403. The navigation hide is UX; the surface enforces roles server-side. This happens when a link to a gated route such as /agents/live/... is shared with a role that cannot open it.
  • An old bookmark lands somewhere unexpected. The legacy addresses in Old URLs and redirects forward automatically; if a link predates them, use the ?tab= form, for example /agents?tab=conversations.
  • A tab’s count badge says “Couldn’t load this count”. The badge’s count fetch failed transiently; the tab itself still works. Refresh, and if the badge keeps failing while the tab loads, your session’s read scope for that count is the thing to check.
  • Agent runtime errors (422s, 429s, quota codes). Those are API-side, not navigation-side; work through the agent error reference.

​
Next steps