Skip to content

Context sources

A context source is a service the agent reads while it answers you: your spec in Notion, a Linear issue, a Figma design, your Kameleoon experiments. Instead of pasting a long page into the chat, you write “build it from my Notion page” or “do issue ENG-42”, and the agent fetches the information itself.

Context sources are for the agent, not for your app: your app doesn’t call them and your visitors can’t access them. For your app to use a service (show your Notion content, measure with Kameleoon), you need a connector.

Notion

The agent searches and reads the pages and databases you shared with Highwind: spec, copy, lists. Connected with your Notion account, read-only. Learn more

Linear

The agent reads the issues, projects and comments you mention. Connected with your Linear account, read-only access requested from Linear. Learn more

Figma

Paste a frame’s link: the agent reads its layers, copy, colors and fonts, and sees it as an image. Connected with a personal token, read-only. Learn more

Kameleoon

The agent reads your sites, experiments, feature flags, goals and results. Connected with API credentials, read-only by default, edits if you allow them. Learn more

Source Connection What the agent can do Billing
Notion Notion account (authorization in a window) Search and read Free
Linear Linear account (authorization in a window) Search and read Free
Figma Personal access token Read a file or a frame, get an image of it Free
Kameleoon Client ID and client secret (API credentials) Read; create and edit if you allow it Included in your Kameleoon subscription

Sources are connected once for your account and then work in all your projects.

  1. Open the Connectors page from the sidebar.
  2. In the filters, pick Used by → The agent (or the Context for the agent category): Notion, Linear, Figma and Kameleoon are shown.
  3. Click the source’s card to open its details.
  4. Follow the instructions in the details:
    • Notion and Linear: click Connect, then authorize Highwind in the service’s window;
    • Figma: paste your Personal access token, then Connect;
    • Kameleoon: paste your Client ID and Client secret, then Connect.
  5. The card switches to Connected. You’re set: go back to your project and mention the source in your request.

To remove a source, open its details and click Disconnect. Tokens are revoked at the service when it allows it, then erased from Highwind.

Just refer to it in your message. You can mention it with @ (or + menu → Connectors, picking the entry in the Context for the agent category) to make sure the agent looks at it:

@Notion Build the landing page described in my "Launch v2" page.
Do Linear issue ENG-42.
Build this page: https://www.figma.com/design/AbCdEf/Site?node-id=12-345
@Kameleoon Wire the sign-up button to the "new-signup" feature flag of my site.

The agent searches, reads what it needs, then builds. In its step details (Show steps), you can see its calls to the source, under their technical name (for example notion_search, kameleoon_request or figma_fetch).

If a source isn’t connected and you mention it, the agent tells you to connect it first from the Connectors page. If a connected source doesn’t answer (service down, expired access), the agent is told and asks you to reconnect it.

  • Read only when your request calls for it. The agent only opens a source while answering, and only when your request refers to it. It never browses your workspaces outside of your requests.
  • Read-only by default. Notion, Linear and Figma are never changed: the agent only gets read tools. Kameleoon stays read-only until you turn on Allow the agent to make changes.
  • Your account’s rights, no more. The agent only sees what your account (or what you shared with Highwind) can see.
  • Sent to the AI model. What the agent reads in a source is treated like your messages: it is sent to the AI model provider to generate the answer. Don’t point it at pages that contain sensitive information.
  • Data, not orders. What the agent reads in a source is reference information to it, never an instruction to follow: a booby-trapped text in a page can’t change how it behaves.
  • Encrypted tokens. Tokens and credentials are encrypted in Highwind and never shown to the agent.