Academy
7. Tools, Browser and Memory
Discover which integrations and knowledge bases @oupi can use, how browser delegation works with the Chrome extension, and how memory and skills improve future missions.
@oupi doesn't work alone — it draws on a rich set of integrations and resources connected to your account. This includes knowledge bases you've uploaded, web search, data sources, Microsoft 365 and Google Workspace, Teams and Slack, MCP servers, and the platform's own capabilities (documents, spreadsheets, code, images, transcription). For each mission, @oupi automatically selects the relevant tools. If it spots an integration that would help but isn't connected yet, it tells you — so you can add it and relaunch. You manage all of this from the Assistant Settings page.
For tasks that require navigating websites, filling out forms, or reading pages behind a login, @oupi can delegate browsing to a dedicated sub-agent — but only when the OUPI Chrome extension is installed and connected. Once active, @oupi hands off the browser work, the sub-agent operates on your behalf, and reports results back into the mission. Without the extension, @oupi falls back on web search and whatever other tools you have connected. This means you stay in control: browser delegation only happens when you've explicitly enabled it.
@oupi learns from you over time through two mechanisms: memory and skills. Memory stores your preferences and recurring contexts — how you like documents formatted, which sources you favor, your usual constraints. Skills are pieces of reusable know-how that you validate; once saved, they're available to all future missions. Together, they mean @oupi gets better the more you work with it. You can review, edit, or delete anything it remembers from the Memory section in your Assistant Settings, so you always stay in control of what it retains.
When @oupi suggests connecting a new integration during a mission, take a moment to do it. The mission can often be retried with the new tool, and every future mission benefits automatically. Clear, well-scoped goals plus the right integrations are the fastest path to accurate results.
After a few missions, visit your Memory settings and review what @oupi has stored. Remove outdated preferences and refine instructions — this keeps future missions aligned with your current needs and avoids stale context creeping in.
Go to your Assistant Settings (dashboard.user.assistant.settings). Check which integrations and knowledge bases are connected. If the Chrome extension isn't installed yet, look at the browser delegation option to understand what it enables. Then open Memory and review any stored preferences or skills.
@oupi selects from your connected tools, knowledge bases, and integrations for each mission — and tells you when a useful one is missing. The Chrome extension unlocks browser delegation for tasks involving site navigation or logins. Memory and skills let @oupi learn your preferences and reuse validated know-how across missions. You control all three from Assistant Settings: connections, browser delegation, and what @oupi remembers.