Skip to content

Navigating the app

The sidebar is organized from the work down to the administration: sessions and projects first, then the knowledge the agent uses, then the connections and tools it works with, then the control panel. This page explains each area. For the underlying terms, see Concepts.

Good to know

Section titled “Good to know”

Project

One engagement: its tasks, linked systems, files, playbooks, and artifacts.

System

A connection to an ERP, database, file server, or other service. One system serves many clients through separate credentials.

Tool

A saved, repeatable action such as a migration load or a nightly sync. Runs the same way every time.

Playbook

A reusable method the agent follows: inputs, steps, approval moments, and completion criteria.

Artifact

A report, mapping proposal, questionnaire, or spreadsheet the agent produced. Downloads as PDF, Word, HTML, or Excel.

Run

One execution of a tool, recorded with its trigger, credential, input, steps, and result.

Agents

Section titled “Agents”

The project switcher at the top selects the project you work in. It filters the session list, shows the project plan on the right, and sets the project of new sessions. All projects lists all your sessions and starts new sessions without a project. New session (or Cmd/Ctrl+O) starts a conversation in the selected project. The search icon in the New session row (or Cmd/Ctrl+K) finds your past sessions by words in their title or messages; a message match opens the session at that message. The start screen shows the built-in playbooks, so you can pick Migrate data or Start a project directly. A session keeps its project for its whole life.

Inside a session, the right side shows the artifacts, files and tool activity of that conversation. Drop files into the chat to use them in the session.

Projects

Section titled “Projects”

One card per engagement. New project creates an empty project. Create project starts an agent session that plans the engagement with you. A project opens as its Brain folder, with Files and Tasks (Board and Table views).

Brain

Section titled “Brain”

Brain works like a file drive.

  • Setup opens Brain > Setup, where you connect context sources: meeting notetakers, Slack, Microsoft Teams, Notion, Google Drive, SharePoint, Box, Gmail and Outlook. Each person connects their own accounts. Until setup is complete, a banner at the top of Brain links to it.
  • Folders come first. The Documentation folder holds system documentation and pages the agent saved from the web, and the Playbooks folder holds built-in and custom playbooks. Both are marked Managed by superglue and don’t accept drops. One folder per project follows. Custom playbooks open in an editor with an agent sidebar.
  • Files that are not in a project show next to the folders. A project folder opens the project: its Files first, and its Tasks in the next tab. Files include uploads and every artifact the agent produced, such as reports, mappings, questionnaires and spreadsheets, with sharing and downloads. Switch between list view, the default, and grid view; Brain remembers your choice.
  • Drop files anywhere on the page to upload them, or on a project folder to add them to that project. Drag a file onto a project folder to link it to that project; a file can be in several projects.

Capabilities

Section titled “Capabilities”
  • Tools lists saved tools. Open one to test it in the playground, inspect its steps, see its version history, and deploy it on a schedule, webhook, API or MCP server.
  • Connections lists your personal and shared connections. Open one to change its endpoint, authentication, Secure Gateway, usage instructions and secrets. The OAuth apps tab lists your organization’s reusable OAuth apps.
  • Schedules lists every recurring run in the organization.
  • MCP Servers configures named servers that expose selected tools to AI clients.

Control Panel

Section titled “Control Panel”
  • Runs is the execution history with filters, search, and the Investigate and Load Run actions.
  • Activity (admins) shows who created, changed, shared and ran what.
  • Organization manages members, invitations and roles.
  • Access Rules (admins, Enterprise) configures what each role can see and do.
  • API Keys creates and revokes API keys.
  • Settings holds your theme and Agent memory: the notes the agent receives when a conversation starts. Personal notes are visible only to you; Organization notes are visible to every member who can view the note’s system. The agent saves notes when you ask it to remember something. It also learns from your recent conversations: lasting personal preferences, and how you corrected or approved its way of doing a recurring task. Those notes show the source Learned. In Ask mode it asks for approval before it saves or deletes an organization note. For admins, Settings also holds the agent memory switch, the design system, run storage, notifications and timeouts.

Organization menu

Section titled “Organization menu”

The menu at the bottom left holds the organization switcher and sign-out.