Project context

The brain is everything superglue knows about your work. Before the agent can plan or execute an implementation well, it needs the same context you have: what was agreed in the kickoff call, which spreadsheets the client sent, and what the target setup should look like. You connect that context once, and every session can use it.

What the brain holds

• Connected context: Systems the agent reads live, such as meeting notetakers, Slack or Microsoft Teams, Notion, Google Drive, SharePoint, Box, Gmail and Outlook.
• File context: Files you upload directly, and files attached to projects, tasks and playbooks. Legacy exports in Excel, CSV or XML belong here.
• Playbooks: Reusable methods that tell the agent how your firm runs a workstream.
• Artifacts: Reports, mapping proposals, questionnaires and spreadsheets the agent has produced.

Systems and tools are capabilities, not context. They are what the agent can do, and they live under Capabilities in the sidebar.

Connect context sources

1. Open Brain → Setup.
2. Choose a source under Meeting notetakers, Workspace apps or Email and select Connect.
3. Sign in with the provider and approve read access.
4. Ask the agent a narrow question to confirm the connection, for example “What did we agree with Contoso about the chart of accounts?”

Supported notetakers are Circleback, Granola, Fireflies, Fathom, Fellow and Read AI. Google Drive and Gmail need a Google OAuth app owned by your firm; the setup page guides you through it.

!

Context-source credentials are personal. Each consultant connects their own accounts, and the agent reads a source only with the credential of the person asking. A source connected by a colleague shows as not connected for you.

The agent uses connected context only when it is relevant to the task. It does not scan your calendar or channels because access exists.

Upload files

Drop files into the chat to use them in the current session. To keep a file for the whole engagement, upload it under Brain → File context or ask the agent to attach it to the project. Uploaded files are parsed on upload, so the agent can read a legacy customer export in Excel the same way it reads an API.

Typical uploads for an implementation:

• Legacy system exports (customers, vendors, items, open transactions, balances)
• The client’s chart of accounts and dimension definitions
• Your firm’s mapping template and data-conversion checklist
• Statements of work and requirement documents

Files uploaded to the brain are private to their owner, admins and explicitly permitted users. Keep one-off inputs and anything with secrets in the session instead.

Organize engagements as projects

Create a project for every implementation. Projects keep sessions focused on the client’s systems, files and tasks, and they give your team one place to track progress. See Project setup.