Gamma is now available as a Remote MCP Server in Dust

🎯 What is it?

You can now connect Gamma to Dust as a Remote MCP Server. This lets your Dust agents generate—and read—Gamma decks, documents, and webpages directly using the context already available in your workspace. The result is a ready-to-polish Gamma artifact you can refine and share.

💡 Why is it useful?

Building a presentation usually means gathering research, notes, and context, then manually copying everything into a slide tool. This connection removes that back-and-forth: your agent takes the context it already has and turns it into a structured Gamma deck for you, so you can focus on refining the final output rather than assembling it from scratch.

⚙ How does it work?

Once Gamma is connected as a Remote MCP Server in your workspace, your agents can call it to create or read Gamma content. You ask the agent to build a deck (or doc/webpage), and it produces a Gamma artifact you can then open and polish in Gamma.

✨ Concrete Use Cases

Here's how you could use it:

  • Client-ready proposals: Have an agent compile your research and meeting notes into a first-draft Gamma deck, ready for you to tailor before sending.

  • Internal updates: Turn a body of context—project notes, status updates, data—into a structured presentation or webpage without manual slide-building.

📈 Benefits for you

You save time by skipping the copy/paste shuffle, move faster from raw context to a polished draft, and keep your presentations grounded in the information already living in your Dust workspace.

🚀 How to access it?

This feature is generally available to everyone with a Gamma account. To get started, connect Gamma as a Remote MCP Server in your workspace, then ask one of your agents to generate a Gamma deck, document, or webpage.

🎯 What is it?

You can now reference skills and tools directly inside your skill instructions, the same way you already reference knowledge. Skills can call on other skills, letting you build richer, more modular capabilities by combining existing building blocks. As part of this change, the separate "tools" section has been removed, and tools are now inserted inline wherever you need them.

💡 Why is it useful?

Until now, skills stood on their own and couldn't draw on one another, which often meant duplicating the same logic across multiple skills. This update responds to a widely requested ability to compose skills, so you can assemble specialized capabilities into more complete workflows without rebuilding them each time.

⚙️ How does it work?

When editing a skill's instructions, you simply use a dropdown to insert a reference to another skill or to a tool inline, exactly as you would when adding knowledge. The referenced skill or tool becomes part of that skill's behavior, so capabilities can be layered and reused.

✨ Concrete Use Cases

Here's how you could use it:

  • Building on existing skills: Create a "Weekly Report" skill that references your existing "Data Retrieval" and "Summarization" skills, rather than duplicating that logic.

  • Inline tool placement: Insert a specific tool exactly at the point in your instructions where it's needed, making the skill's behavior clearer and easier to maintain.

📈 Benefits for you

Less duplication, easier maintenance, and far more flexibility when designing skills. By composing skills from smaller, reusable pieces, you can build sophisticated agents faster and keep them consistent over time.

🚀 How to access it?

The feature is available to everyone. When editing a skill, use the dropdown within the instructions to insert a reference to another skill or a tool. Your existing skills have already been updated automatically: the list of tools previously associated with a skill now appears at the top of its instructions, so nothing is lost in the transition.


No action is required on your part, your existing skills continue to work as before. This is simply a new way to compose and reuse them going forward.

Builders can now ask the @dust agent to create or edit skills directly from a conversation, no need to open the Skill Builder. Describe the workflow you want to capture, and @dust handles the rest.


Dust Support: Get Instant, Grounded Support Answers from @dust

🎯 What is it?

We've introduced a new discoverable skill that turns @dust into your first line of support. When you ask a support-related question, the agent detects your intent, answers it directly, and grounds its response in trusted sources so you can rely on what it tells you.

💡 Why is it useful?

Until now, getting a support answer often meant leaving your workspace to search documentation, browse community threads, or file a request and wait. This skill brings accurate support answers to you instantly, right where you already work, so you spend less time hunting for help and more time getting things done.

⚙️ How does it work?

The skill recognizes when you're asking a support question and responds with answers grounded in real, up-to-date sources: the public dust-tt/dust GitHub issues and the Dust community. This means responses reflect documented known issues and community knowledge rather than guesswork.

Concrete Use Cases

Here's how you could use it:

  • Troubleshooting a behavior: Ask "Why is my agent not picking up the latest documents from my connected data source?" and get an answer grounded in known issues and community discussions.

  • Checking a known issue: Ask "Is there a reported problem with PDF parsing right now?" and find out whether it's a documented issue with a workaround or fix already discussed.

📈 Benefits for you

Faster, more accurate answers without leaving Dust. You get reliable support grounded in real sources, reduce the back-and-forth of opening tickets, and resolve questions in the flow of your work.

🚀 How to access it?

The skill is discoverable and available to every user. Simply mention @dust and ask your support question. The agent will detect that you need support and respond with a grounded answer.

Speech-to-Text for Audio & Video Files

🎯 What is it?

A new speech-to-text tool is now available in Dust, allowing your agents to transcribe spoken content from both audio and video sources. You can transcribe content from supported URLs or by uploading files directly, with support for most common formats (mp3, mp4, wav, m4a, mov, webm, aac, flac, and more).

💡 Why is it useful?

Audio and video content is everywhere—meeting recordings, interviews, webinars, voice notes—but the information locked inside it is hard to search, reuse, or act on. Transcription has been a recurring request, and with Dust's expanded processing capabilities, your agents can now turn spoken content into text that can be summarized, analyzed, and integrated into your workflows.

⚙️ How does it work?

Your agent can transcribe content in two ways: from a URL (within an approved list of domains) or from a file you upload directly. Once transcribed, the text becomes available for the agent to work with—summarizing, extracting key points, or feeding into other tasks.

✨ Concrete Use Cases

Here's how you could use it:

  • Meeting follow-ups: Upload a recording of a call and ask your agent to produce a clean summary with action items and decisions.

  • Content repurposing: Transcribe a webinar or podcast episode, then have your agent draft a blog post, social snippets, or an internal recap.

  • Interview analysis: Turn recorded user interviews into searchable text and extract recurring themes or quotes.

📈 Benefits for you

Significant time savings on manual transcription, easier reuse of audio/video content, and the ability to make spoken information searchable and actionable—all within your existing Dust workflows.

🚀 How to access it?

The feature is available to everyone now—no activation needed. Simply provide a supported URL or upload an audio/video file in your conversation, and ask your agent to transcribe it.

Pods — A Shared Workspace for Your Team and Your Agents

🎯 What is it?

Pods are dedicated collaborative spaces where your team and your agents work together on a shared initiative. Each Pod brings Conversations, Files, and Tasks into one place — continuously indexed so that agents build on what was already discussed, without you having to re-explain context every time.

💡 Why is it useful?

Work in most teams is fragmented: conversations are scattered across individual feeds, files live in different tools, and every new interaction starts from scratch. Pods solve this by making context persistent and shared — so the next conversation starts smarter than the last, and nothing gets lost between sessions.

⚙️ How does it work?

When you create a Pod, you get a shared environment with four core components:

  • Conversations — All threads related to the initiative stay in one place, and are continuously indexed so agents can reference past decisions automatically.

  • Files — Upload documents or connect Company Data directly into the Pod. Everyone — humans and agents — works from the same shared context.

  • Tasks — Create to-dos, assign them to teammates, or launch agent-run task conversations with the right context preloaded.

  • Governance — Pods can be open (anyone in the workspace can join) or invite-only (editors manage membership). Restricted data sources go through an approval step before results are visible to the whole Pod. Workspace admins can also limit Pod creation to invite-only if needed.

Concrete Use Cases

Here's how you could use it:

Running a client project: Create a Pod for the account, add the relevant files and data sources, and let your agents reuse every past decision and conversation thread — no more copy-pasting context into each new chat.

Managing a recurring initiative: Use Tasks to assign work to teammates or trigger agent-run conversations at the right moment, with all the background knowledge already loaded in the Pod.

📈 Benefits for you

  • No more context re-pasting — agents remember what was discussed and build on it automatically.

  • One place for everything — files, conversations, and tasks are co-located and shared across your team.

  • Agents as true teammates — they can read files, reference past conversations, create and update tasks, and manage Pod members, just like a human collaborator would.

  • Flexible permissions — open collaboration or controlled access, depending on what your initiative requires.

🚀 How to access it?

Pods are available to everyone — no feature flag, no opt-in required. Look for the Pods section in your Dust sidebar. You can create a new Pod directly from there, and the documentation is available at https://docs.dust.tt/docs/pods-overview.

Claude Opus 4.8 Now Available in the Agent Builder

🎯 What is it?

Claude Opus 4.8, Anthropic's latest and most advanced reasoning model, is now available in Dust's agent builder. Enterprise customers can select it as the underlying model when creating custom agents, giving them access to Anthropic's most capable model to date.

💡 Why is it useful?

Opus models sit at the top of Anthropic's model family — they're designed for tasks that demand deep reasoning, sustained multi-step thinking, and the highest quality outputs. As each new version ships, it builds on the last with improved performance and reliability. Opus 4.8 is no exception, and it's now within reach directly from your Dust workspace.

⚙️ How does it work?

When building or editing a custom agent in Dust, you can now select Claude Opus 4.8 as the model powering that agent. The model is not set as a default — it's a deliberate choice available to those who want the highest level of reasoning for specific, demanding use cases.

Concrete Use Cases

Here's how you could use it:

  • Complex analysis & synthesis: Build an agent that processes lengthy, nuanced documents — legal contracts, research reports, financial filings — and produces high-quality structured summaries or recommendations.

  • Advanced code generation & review: Set up a coding agent that not only generates code but critically evaluates logic, identifies edge cases, and suggests architectural improvements across long codebases.

📈 Benefits for you

Access to Opus 4.8 means your most demanding workflows no longer require trade-offs between speed and quality — you can configure dedicated agents that bring the best reasoning available to bear on your hardest problems, while keeping lighter models for everyday tasks.

🚀 How to access it?

This feature is available to Enterprise customers. To get started:

  1. Go to the Agent Builder in your Dust workspace

  2. Create or edit a custom agent

  3. In the model selection step, choose Claude Opus 4.8

  4. Configure the rest of your agent as usual and deploy

🎯 What is it?

Dust agents can now connect to Apify as a remote MCP (Model Context Protocol) server. This means your agents can trigger Apify Actors — pre-built web scraping and automation tools — directly from a Dust conversation, and pull the resulting data back in real time.

💡 Why is it useful?

Getting fresh data from the web or automating repetitive data-collection workflows has historically required custom-built scrapers, dedicated infrastructure, or manual copy-paste work. With Apify connected to Dust, agents can tap into thousands of ready-made scraping and automation tools on demand — no custom code, no glue scripts, no maintenance overhead.

⚙️ How does it work?

Apify is connected as a remote MCP server inside Dust. Once set up, agents can call any Apify Actor (a self-contained unit for scraping or automating tasks on a specific platform or website), wait for it to run, and fetch the structured output directly into the conversation. Authentication is handled via OAuth.

Concrete Use Cases

Here's how you could use it:

  • Competitive intelligence: Ask an agent to scrape a competitor's pricing page or product listings on a weekly basis and summarize changes — no manual browsing required.

  • Lead enrichment: Trigger an Apify Actor to pull public company data, LinkedIn profiles, or job postings and feed the results directly into your CRM workflow through Dust.

  • Social media monitoring: Run an Actor to collect recent posts or mentions from a specific platform and have an agent analyze sentiment or flag trending topics.

📈 Benefits for you

Access to live, structured web data without engineering effort. Your agents become significantly more autonomous on research, monitoring, and data-gathering tasks — eliminating the round-trip between Dust and external scraping tools.

🚀 How to access it?

Available now for teams already using Apify. Connect it in Spaces → Tools, using OAuth to authenticate. Once added, it can be assigned to any agent in your workspace.

🎯 What is it?

Dust just unlocked six new MCP (Model Context Protocol) integrations: Monday.com, Snowflake, Luma, Confluence, Contentsquare, and Praiz are now available for all workspaces. Each integration lets your agents connect directly to these tools and take action — no tab-switching, no copy-pasting, no manual data gathering.

💡 Why is it useful?

Your tools hold critical data — project statuses, warehouse queries, event records, meeting transcripts, wiki pages, digital experience metrics. Until now, getting that data into a Dust workflow meant leaving the conversation. With MCP integrations, agents can reach directly into these tools and surface exactly what you need, right where you're working.

⚙️ How does it work?

Each integration is set up once by an admin in Spaces → Tools. After that, any team member can add the tool to their agents. Authentication is handled via OAuth — secure, and no API key management required.

Concrete Use Cases

Here's what you can do with each new integration:

  • Monday.com — Let agents track project statuses, pull board items, and surface blockers across your team's work.

  • Snowflake — Query your data warehouse directly from a conversation. Agents can retrieve, filter, and analyze data without leaving Dust.

  • Luma — Access event details, attendee lists, and registration data from Luma directly in your agents' workflows.

  • Confluence — Agents can search and read pages and spaces, look up page history and comments, list contributors, create and update pages, and add inline comments — all from Dust.

  • Contentsquare — Query site metrics, funnels, user journeys, and conversion impact data. Turn hours of dashboard navigation into a simple question to your agent.

  • Praiz — Search meetings, pull full transcripts, access timelines, comments, participants, and usage stats. Ideal for turning call insights into follow-ups, account briefs, or CRM updates automatically.

📈 Benefits for you

Less context-switching. Faster workflows. Your agents can now pull live data from the tools your teams already use daily — without anyone needing to leave Dust or manually gather information before a conversation.

🚀 How to access it?

Go to Spaces → Tools in your Dust workspace and look for any of these integrations in the MCP catalog. Admins set them up once; after that, anyone can attach them to their agents. No feature flag — available to all workspaces today.

6 New Integrations Now Available in Dust

🎯 What is it?

Dust just unlocked six new MCP (Model Context Protocol) integrations in the span of 48 hours: Monday.com, Snowflake, Luma, Confluence, Contentsquare, and Praiz are now available for all workspaces. Each integration lets your agents connect directly to these tools and take action — no switching tabs, no copy-pasting. :cite[ej2]:cite[b2w]:cite[bpe]:cite[cu0]

💡 Why is it useful?

Your tools hold critical data — project statuses, warehouse queries, event records, meeting transcripts, wiki pages, digital experience metrics. Until now, getting that data into a Dust workflow meant leaving the conversation. With MCP integrations, agents can reach directly into these tools and surface what you need, right where you're working.

How does it work?

Each integration is set up once by an admin in Spaces → Tools. After that, any team member can add the tool to their agents. Authentication is handled via OAuth — secure, and no API key juggling required.

Concrete Use Cases

Here's what you can do with each new integration:

  • Monday.com — Let agents track project statuses, pull board items, and surface blockers across your team's work. Available to all workspaces.

  • Snowflake — Query your data warehouse directly from a conversation. Agents can retrieve, filter, and analyze data without leaving Dust.

  • Luma — Access event details, attendee lists, and registration data from Luma directly in your agents' workflows.

  • Confluence — Agents can now search and read pages and spaces, look up page history and comments, list contributors, create and update pages, and add inline comments — all from Dust.

  • Contentsquare — Query site metrics, funnels, user journeys, and conversion impact data. Turn hours of dashboard navigation into a simple question to your agent.

  • Praiz — Search meetings, pull full transcripts, access timelines, comments, participants, and usage stats. Ideal for turning call insights into follow-ups, account briefs, or CRM notes automatically.

📈 Benefits for you

Less context-switching. Faster workflows. Your agents can now pull live data from the tools your teams already use daily — without anyone needing to leave Dust or manually gather information before a conversation.

🚀 How to access it?

Go to Spaces → Tools in your Dust workspace, and look for any of these integrations in the MCP catalog. Admins set them up once; after that, anyone can attach them to their agents. No feature flag — available to all workspaces today.