intelligent.pageDocs

Platforms and integrations

Where you can work with intelligent.page — the web app, Chrome, chat, shared links and the API — and what you can connect to it.

The task loop runs in one place — your directories on intelligent.page — but you can reach it from several surfaces, and connect it to the tools that hold your facts. This page helps you pick the right surface for the moment and see what you can plug in.

Where to work with intelligent.page

The web app is the complete surface. The Chrome companion adds the two things only a browser can reach — a meeting in progress and a page behind your login. Chat is a way to ask and be told; reading a dossier is a job for a screen. The API drives all of it.

You can mix them on the same directory. A request sent from Slack, a meeting captured by the companion and a task created over the API all land in the same Memory.

Connect your tools

Connectors let the work read the systems that hold your facts. They inform the model; they are read on demand, not copied or indexed in the background. Grant the narrowest access that covers the question.

Search across your tools

Separately from connectors, the search bar can query the tools you use — Slack, GitHub, GitLab, Drive, Gmail, Outlook, Jira, Confluence, Notion, Linear, Trello, Dropbox, Figma and eleven more — live, as you, with no background index. Each person switches their own sources on under Settings → Search. See Search sources.

For a platform not listed here, see the commerce connector reference for how each marketplace and storefront exposes its data, and Connectors for how authorisation and revocation work.

Work when you are not at the screen

Every run continues whether or not the tab is open. Close it; you are told when it finishes or when it has a question.

Surfaces

Integrations