Here's the thing about "summarize my folder" - it's only half the job. Your work doesn't just live in files. It lives in Sentry tickets, in Mixpanel dashboards, in Figma frames. Connectors are how your AI gets invited into those rooms too.

Most connectors are a permission you grant, one tool at a time, on the Connectors page in settings. Connect a tool, following the sign-in, key, or setup flow it uses - some tools need extra setup before they appear - and from then on your AI can reach into it during tasks, with your approval on anything that matters.

Two tools ship built in instead: Figma, for reading designs, and Auth0, for teams that manage their sign-in systems with it. Each waits as a "Turn on" card at the end of the Suggested list on the Connectors page - off until you turn it on. For Figma, that means switching on the Dev Mode MCP server in the Figma desktop app. Once a built-in tool is on, it joins your connectors like the rest. Not for you? Leave it off, or turn it off from the same page any time.

One connector, one job

Each connector exists because your AI can be genuinely useful there - not because integrations look good on a checklist. A few examples, by what they're actually for:

Sentry - know what broke, how often, and what it cost you.
Mixpanel - pull the product numbers behind your decisions.
Langfuse - see how your AI features are actually performing.
Elastic - search across your team's data like it's one file.
Figma - find the design something should be built against.

You don't need all of them. Connect the two or three where your team spends its day, ignore the rest, and add more later when a task calls for it.

What it makes possible

With a connector on, the questions you'd normally open five tabs to answer become one chat message:

You: What broke most often in Sentry this week, and draft a summary I can paste into our channel.

Your AI: The top offender this week is the checkout timeout - 41 events, up from 12 last week, mostly on mobile. I've drafted a short summary with the trend and the affected release. Want me to paste it here or trim it first?

"What's our top error this week?" - answered, with a draft summary attached.
"Pull the latest numbers for the deck" - real data, not last week's screenshot.
"Find the design I should build against" - the right Figma frame, linked.

You're the one holding the keys

The connectors you add are opt-in, top to bottom: you choose which tools to connect, and a connector only joins the tasks it's connected for. The built-in tools, Figma and Auth0, stay off until you turn them on from the same page - and switch off from there too. And by default, connector actions that change anything go through the same approval cards that protect your files. Change your mind? Disconnect any time, from the same page.

When in doubt, chat

If a connector needs attention - say a sign-in expired - your AI tells you plainly instead of failing quietly. And if you're ever unsure what it can reach, just ask: "what can you see right now?"

Start small

Connect the one tool you check first every morning. Then ask one real question about it in a Work task. That single loop - question in, real answer out - is usually all it takes to see what the rest of your stack is worth.

Keep Reading

Product Update

Bring your stack into the conversation

Connect a tool on the Connectors page, then ask your first real question in a Work task.

Explore ASI:Work

ASI:Work Connectors: Bring Your Tools Into the Room