Skip to Content
OpenInspect
Working in a session

Inbox, sessions list, and search

How team scope and filters shape the sidebar inbox and Sessions search, without changing session access.

Last reviewed View as MarkdownEdit on GitHubGive feedback

The sidebar inbox shows what needs you now; the Sessions page searches current and archived work within your access and discovery scope. Both apply server-side visibility checks. See Multiplayer and sharing for access rules.

The Sessions page with search, owner, repository, environment, lifecycle, and origin filters above a list of sessions
The Sessions page: full-history search with owner, repository, environment, lifecycle, and origin filters.

Choose a discovery scope

The sidebar's team switcher offers Workspace, an individual team, All my teams, and, for workspace Administrators and Owners, All teams. Selecting a team also exposes a Team page link. See Teams.

Workspace selects sessions with no owning team. A team scope selects sessions owned by that team, including its workspace-visible sessions. All my teams removes the single-team filter and uses your readable session set, including workspace-visible work; it is not a membership-only filter. All teams is the administrative discovery scope and still applies session read checks. A session's Workspace visibility is not the same as Workspace discovery scope: a workspace-visible team session remains team-owned and is excluded from the Workspace scope.

Scope and filters narrow discovery; they do not grant access or change visibility. Private-session checks still apply, and non-private Team read isolation depends on the deployment's enforcement mode (default shadow). See Multiplayer and sharing and Deployment.

The sidebar inbox

The left sidebar groups sessions into three collapsible sections. Each section remembers whether you left it open.

SectionWhat lands here
Needs attentionAny session in the group has a finished turn you have not read yet.
In progressA session in the group is active (a prompt is pending or running) and nothing is unread.
RecentEverything else: completed, failed, cancelled, or draft sessions you have already read.

A session moves between sections on its own:

  • When a turn finishes, the session gets an unread mark for you and moves to Needs attention.
  • Opening the session reads its latest finished turn (while the tab is visible), and it moves to In progress or Recent.
  • Sending a prompt makes it active, so it sits under In progress until the turn ends.

Archived sessions are not shown in the inbox. The Archived link at the bottom of the list opens the Sessions page filtered to archived sessions.

Each section loads a page at a time; use Load more at the bottom of a section to fetch older entries.

Badges and rows

  • An accent dot before the title marks an Unread session.
  • A Failed label appears on sessions whose last run failed.
  • The row also shows relative time, the repository (or repositories), and the base branch when it is not main.
  • A sub-task tag marks an agent-spawned child whose parent is not in the current list.

Child sessions

Sessions the agent spawned are nested under their parent, so a parent and its children are read as one group. A group is placed by its most demanding member: one unread child is enough to put the whole group under Needs attention. See Child sessions.

The owner filter

The All / Mine toggle above the list limits the inbox to sessions you started. When Mine is empty the list reads "No sessions started by you". Mine is a convenience for finding your own work within the active scope, not an access boundary. All does not bypass session visibility or membership checks.

Row actions

Open a row's menu (or long-press it on a phone) for:

  • Rename: edit the title in place. Enter saves, Escape cancels.
  • Mark as read: clears the unread mark without opening the session.
  • Mark all as read: on a parent with unread child sessions, clears the unread mark on the parent and the child sessions nested under it that the current inbox filters include.
  • Archive: opens the confirmation dialog. Archiving the session you are viewing returns you to the home page.

Rename and Archive require session lifecycle permission and access to act on that session, including current owning-team membership for team-owned sessions.

Mark all as read

Hover the Needs attention heading and click the double-check icon to clear every unread mark in that section at once. On a touch device the icon is always shown. A confirmation names how many sessions will be marked, and the active filters (Mine, or the selected team) when they narrow the list. Sessions on pages you have not loaded yet are included. Only the turns that are unread when you confirm are marked, so a turn that finishes afterwards still brings its session back to Needs attention.

The team overview page offers the same action on its Needs attention list, limited to that team's sessions.

The Sessions page

Open Sessions from the sidebar navigation (the /sessions route). It is described as "Find past and current work, including archived sessions and older history."

The search box reads "Search title, ID or repository…". Typing commits to the URL after a short pause, so a filtered view is shareable as a link. Clear it with the X in the box.

Filters

FilterOptions
CreatorAll, Mine
OwnerAnyone, Started by me, Participating
VisibilityAny visibility, Team, Workspace, Private
RepositoryAny repository, or one repository you can access
EnvironmentAny environment, or one saved environment
LifecycleNot archived (default), Archived, All
OriginAny origin, Started by a person, Automation run, Agent sub-task, GitHub bot, Linear bot, Slack bot

Participating includes sessions you own, sessions with an explicit collaborator grant for you, and sessions you have read or marked as read, still subject to access checks. The Visibility filter selects a saved visibility value; it does not change who can read a session.

Origins map to how the session was created: from the web, an automation run, a child spawned by an agent, or one of the GitHub, Linear, or Slack bots. The status text under the filters reports "Showing N sessions", with "More available" when there is another page; Load more fetches it. A link with unsupported filter parameters shows no sessions and offers Reset filters.

Result rows show a lifecycle label: Draft, Active, Completed, Failed, Archived, or Cancelled.

When the Lifecycle filter is Archived, the page adds a Manage archived sessions link to Settings › Data Controls, where you can unarchive sessions.

New session

The New session button at the top of the page (and the plus icon in the sidebar) opens the composer. It is shown only when you can create sessions.

Rename and archive

Rows on the Sessions page open the session; they have no action menu. Rename and archive a session from its row menu in the sidebar, or rename it by clicking the title in the session header. To restore archived sessions, see Data controls.

Keyboard shortcuts

ActionDefault
Open the command menu (quick search of recent sessions)Cmd/Ctrl+K
New sessionCmd/Ctrl+Shift+O
Toggle the sidebarCmd/Ctrl+/
The quick search dialog opened with Cmd or Ctrl+K, listing navigation commands above recent sessions
Quick search: press Cmd/Ctrl+K anywhere to jump to a session, a settings page, or a command.

All of these can be rebound under Settings › Keyboard. See Keyboard shortcuts.

Troubleshooting

SymptomCauseFix
A session stays under Needs attention after you opened itThe latest turn is read only while the tab is visible; a background tab waitsBring the tab to the front, or use Mark as read from the sidebar row menu.
A session you expect is missing from the inboxIt is archived, outside your selected team scope or filters, or no longer readableSelect All my teams in the team switcher, then check the other filters and try Sessions with Lifecycle set to Archived. If still missing, review session access and ask the owning user or team lead.
"You do not have permission to view sessions."Your role has no session read accessAsk a workspace Owner or Administrator. See Workspace access.
Search finds nothing for a repositorySearch matches title, ID, or repository textUse the Repository filter instead of typing the repository name.

Next steps

On this page