🎯 What is it?

The Statuspage MCP Server is now generally available across all Dust workspaces. This integration allows your agents to interact directly with Statuspage to manage incident communications. Agents can list pages, components, and incidents, retrieve incident details, create new incidents (including affected components and impact levels), and update existing ones—all through natural conversation.

💡 Why is it useful?

When incidents occur, speed and clarity in communication are critical. Instead of manually switching between Dust and Statuspage to update your status page, you can now delegate this task to your agents. This integration addresses the need for faster incident response workflows and reduces the friction in keeping stakeholders informed during critical moments.

⚙️How does it work?

Workspace admins can configure the Statuspage integration by adding an API Key in Spaces > Tools. Once set up, anyone in the workspace can enable the Statuspage tools on their agents, allowing them to execute Statuspage operations through conversation.

✨ Concrete Use Cases

Here's how you could use it:

Incident Response Agent: Create an agent that monitors your infrastructure alerts and automatically creates and updates Statuspage incidents when issues are detected, ensuring your customers are always informed in real-time.

Status Communication Assistant: Build an agent that helps your support team quickly update incident status, affected components, and impact levels by simply describing the situation in natural language, eliminating the need to navigate the Statuspage interface during high-pressure moments.

📈 Benefits for you

• Faster incident communication: Reduce the time between detecting an issue and updating your status page

• Streamlined workflows: Keep all incident management within your Dust workspace

• Better coordination: Enable your entire team to update status pages through agents, not just those familiar with Statuspage

• Reduced context switching: Stay focused on resolving issues while agents handle status updates

🚀 How to access it?

1. If you're a workspace admin: Go to Spaces > Tools and add your Statuspage API Key

2. Once configured, any team member can enable the Statuspage tools on their agents

3. Your agents can now manage incidents, components, and status pages through conversation

The Statuspage MCP Server has been thoroughly tested over the past few weeks and is now stable and ready for production use.

🎯 What is it?

The Salesloft MCP Server is now generally available in all Dust workspaces. Your agents can now directly retrieve your Salesloft actions, with the ability to filter for due or overdue tasks. This gives sales reps instant visibility into what requires their immediate attention, directly within Dust.

💡 Why is it useful?

Sales teams juggle multiple priorities and tools throughout their day. By connecting Salesloft directly to your Dust agents, you eliminate the need to constantly switch between platforms to check what's on your plate. Your agents can proactively surface what needs your attention, helping you stay on top of your sales activities without the manual overhead.

⚙ How does it work?

Once configured by a workspace admin, any agent in your workspace can access the Salesloft integration. Agents can retrieve your current Salesloft actions and optionally filter to show only what's due or overdue, ensuring you focus on the most time-sensitive tasks first.

✨ Concrete Use Cases

Here's how you could use it:

Daily Sales Assistant: Create an agent that starts your day by pulling all overdue and due Salesloft actions, presenting them in a prioritized morning briefing alongside your calendar and recent emails.

Pipeline Management Agent: Build an agent that monitors your Salesloft activities across all active deals, alerting you when follow-ups are due and suggesting next steps based on your sales playbook.

📈 Benefits for you

• Time savings: No more switching between tools to check your task list

• Better prioritization: Instant visibility into what's overdue or due today

• Proactive workflows: Let agents surface the right actions at the right time

• Seamless integration: Your sales workflow stays within Dust

🚀 How to access it?

Workspace admins can set up the Salesloft integration by navigating to Spaces > Tools and adding the connection with a Salesloft API Key. Once configured, anyone in your workspace can add the Salesloft tools to their agents and start using them immediately.

🎯 What is it?

The Front MCP Server is now available in all Dust workspaces. This integration allows your agents to interact directly with Front, your customer communication platform. Agents can search and read conversations, look up contact histories, manage inboxes and tags, create outbound messages, draft replies, send messages, add internal comments, and organize conversations.

💡 Why is it useful?

Managing customer communications often requires jumping between tools, searching through message histories, and manually drafting responses. The Front MCP Server brings Front's full capabilities directly into Dust, allowing your agents to access customer context, automate routine communication tasks, and maintain consistent follow-ups—all without leaving your workflow.

⚙ How does it work?

Once your workspace admin sets up the Front MCP Server with an API key in the Spaces > Tools section, the tools become available to anyone in your workspace. You can then add these tools to your agents, giving them the ability to interact with Front on your behalf.

✨ Concrete Use Cases

Here's how you could use it:

Customer Success Follow-up Agent: Create an agent that monitors tagged conversations in Front, retrieves customer history, and automatically drafts personalized follow-up messages based on previous interactions and current context.

Support Triage Agent: Build an agent that searches recent Front conversations by topic or contact, identifies patterns or urgent issues, adds internal comments with context for your team, and tags conversations appropriately for routing.

Outbound Campaign Agent: Design an agent that creates outbound conversations in Front, personalizes messages based on contact information and history, and sends them at optimal times while maintaining a consistent brand voice.

📈 Benefits for you

• Time saving: Automate repetitive communication tasks and reduce context switching between tools

• Better efficiency: Access full customer history and conversation context instantly within your agent workflows

• New possibilities: Build intelligent communication workflows that combine Front's capabilities with other tools and data sources in Dust

🚀 How to access it?

1. Admins: Go to Spaces > Tools in your Dust workspace and set up the Front MCP Server using your Front API key

2. All users: Once configured, add the Front tools to any agent you create or modify

3. Start automating: Your agents can now interact with Front conversations, contacts, and messages directly

The integration has been tested and stabilized over the past few weeks and is ready for production use across all workspaces.

🎯 What is it?

The Ashby MCP Server is now available to all Dust workspaces. This integration allows your agents to interact directly with your Ashby recruiting data—search for candidates, access interview feedback, manage notes on candidate profiles, and extract report data as CSV files using just a report URL.

💡 Why is it useful?

Recruiting teams often need to quickly access candidate information, review feedback across multiple interviews, or pull reports for analysis. Instead of switching between Dust and Ashby, your agents can now retrieve this information directly within your workflow, saving time and keeping your recruiting operations seamless.

⚙ How does it work?

Workspace admins can configure the Ashby connection in Spaces > Tools using an Ashby API Key. Once set up, anyone in your workspace can enable these capabilities on their agents to start interacting with your Ashby data.

✨ Concrete Use Cases

Here's how you could use it:

Candidate Research Agent: Build an agent that searches for candidates by name or email and compiles all their interview feedback into a summary before your hiring committee meeting.

Recruiting Analytics Assistant: Create an agent that pulls data from multiple Ashby reports and generates comparative analyses or weekly recruiting metrics dashboards.

Candidate Communication Helper: Set up an agent that reads and adds notes to candidate profiles, helping recruiters maintain context and document important details throughout the hiring process.

📈 Benefits for you

• Faster access to recruiting data: No need to leave Dust to check candidate information

• Better context for decisions: Agents can synthesize feedback and data from multiple sources

• Streamlined workflows: Automate repetitive tasks like pulling reports or updating candidate notes

• Improved collaboration: Share agent-generated insights with your team directly in Dust

🚀 How to access it?

1. Navigate to Spaces > Tools in your Dust workspace

2. Configure the Ashby MCP Server with your API Key (admins only)

3. Enable the Ashby tools on any agent you want to use them with

4. Start querying your recruiting data!

This feature has been tested extensively over recent weeks, and we've refined the configuration process to make setup as smooth as possible.

🎯 What is it?

The Slab MCP Server is now generally available across all Dust workspaces. Your agents can now directly interact with your Slab knowledge base: search for posts using keywords and filters, read full post content, browse topics, and access post metadata—all without leaving Dust.

💡 Why is it useful?

If your team uses Slab to centralize documentation, policies, or processes, this integration eliminates context switching. Instead of manually searching Slab and copying information into Dust, your agents can now retrieve and reference Slab content automatically, ensuring they always work with up-to-date information from your knowledge base.

⚙ How does it work?

Once an admin connects Slab using an API key in the Tools section of a Space, any agent in that Space can search, filter, and read Slab posts directly. The server supports keyword search, filtering by topic or publication status, and full post retrieval.

✨ Concrete Use Cases

Here's how you could use it:

Onboarding Agent: Build an agent that answers new hire questions by searching your Slab onboarding documentation, delivering accurate answers with direct references to published posts.

Policy Assistant: Create an agent that retrieves and explains company policies stored in Slab, filtering by specific topics (HR, Legal, IT) and ensuring only published, current versions are referenced.

Documentation Helper: Deploy an agent that helps teams find technical documentation, API guides, or process workflows from Slab, reducing time spent searching and increasing consistency in how information is shared.

📈 Benefits for you

• Time savings: Agents retrieve Slab content instantly, eliminating manual lookups

• Better accuracy: Agents reference the latest published information directly from your source of truth

• Seamless workflow: Keep your team in Dust while accessing your full Slab knowledge base

🚀 How to access it?

Admins can set up the Slab MCP Server in Spaces > Tools using a Slab API Key. Once configured in a Space, any member can enable it on their agents and start searching Slab content immediately.

🎯 What is it?

Slideshow Frames now come with built-in navigation controls and can be exported as multi-page PDFs. Each slide is rendered as a full page with proper page breaks, making it easy to share and print your agent-generated presentations.

💡 Why is it useful?

When agents create slideshow presentations for you, you often need to share them with colleagues, present them in meetings, or print them for documentation. Until now, exporting these slideshows outside of Dust wasn't straightforward. This update makes it simple to take your agent-generated slide decks anywhere.

⚙️ How does it work?

When you create a new slideshow Frame, it automatically includes navigation controls to move between slides. You can then export the entire presentation as a PDF, where each slide becomes its own properly formatted page.

✨ Concrete Use Cases

Here's how you could use it:

Executive briefings: Ask an agent to create a monthly performance dashboard as a slideshow, then export it as a PDF to email to leadership or print for board meetings.

Client presentations: Generate a project status update slideshow from your latest data, export it as a PDF, and share it directly with clients who don't have access to Dust.

📈 Benefits for you

• Better portability: Share agent-generated presentations outside Dust seamlessly

• Print-ready: Get properly formatted PDFs with each slide on its own page

• Professional output: Navigation controls make it easy to review slides before exporting

🚀 How to access it?

This feature is available now for all new slideshow Frames you create. Simply ask an agent to generate a slideshow, and you'll automatically get the navigation controls and PDF export capability. Note that existing slideshows won't have this functionality—you'll need to regenerate them to use the new features.

Example slideshow Frame

🎯 What is it?

Dust now supports Attio's official MCP server, allowing you to connect your Attio CRM account directly to Dust. Once connected via OAuth, your Dust agents can access and interact with your Attio workspace seamlessly.

💡 Why is it useful?

Managing your CRM often requires switching between multiple tools and manually updating information. With this integration, your Dust agents can handle CRM tasks directly, saving you time and keeping your customer data up-to-date without leaving your workflow.

⚙ How does it work?

You connect your Attio account to Dust through a secure OAuth authentication. Once connected, your agents can read and write data across your Attio workspace, including contacts, companies, deals, tasks, notes, emails, and call recordings.

✨ Concrete Use Cases

Here's how you could use it:

Sales workflow automation: Ask an agent to "Find all companies in my pipeline that haven't been contacted in 30 days and draft personalized follow-up emails based on their latest notes."

Meeting preparation: Before a client call, ask "Pull up all recent interactions, open deals, and tasks related to [Company Name] and create a meeting brief."

Post-call documentation: After a meeting, tell an agent to "Update the deal status for [Company Name], log today's call recording, and create follow-up tasks based on our conversation."

Contact enrichment: Request "Search for contacts without assigned owners and suggest assignments based on territory or relationship history."

📈 Benefits for you

• Time saving: Automate repetitive CRM updates and searches

• Better data quality: Reduce manual entry errors with agent-assisted workflows

• Contextual intelligence: Agents can cross-reference CRM data with other connected sources

• Unified workspace: Manage CRM tasks without switching between platforms

🚀 How to access it?

This feature is available to all Dust users with an Attio account. To get started, connect your Attio workspace through Dust's connections settings using the OAuth authentication flow.

📌 Context

We've migrated Dust's technical architecture from a server-side rendered Next.js application to a standalone React Single Page Application (SPA). Everyone now accesses Dust through a unified URL: app.dust.tt

This change improves the underlying infrastructure that powers your experience with Dust, making the platform faster and more efficient.

🔄 Impact on Dust

Behind the scenes, Dust now handles navigation and page rendering directly in your browser rather than on our servers. This architectural shift brings several technical improvements:

• Faster interactions: The application responds more quickly to your actions

• Smoother navigation: Moving between pages and features feels more fluid

• Better global performance: Multi-region traffic is handled more transparently

• Reduced server load: Lower memory footprint means better scalability

👤 Impact for you

No disruption to your workflow. You'll continue using Dust exactly as before, but you should notice:

• Snappier page transitions when navigating between assistants, conversations, and settings

• More responsive interface interactions

• A generally smoother experience throughout the platform

The transition has been designed to be seamless—most users won't notice anything beyond improved performance.

✅ Actions required

No action required on your part. The change has been automatically deployed for all workspaces.

If you experience any unexpected behavior, the SPA mode can be disabled for your specific workspace. Simply reach out to our support team, and we'll assist you.

🎯 What is it?

Intercom's official MCP (Model Context Protocol) server is now integrated into Dust with native OAuth authentication. You can configure it directly in your workspace, giving your agents secure access to your Intercom data, support tickets, help center articles, and customer interaction history. Only available for US intercom workspace.

💡 Why is it useful?

Many of you asked for deeper Intercom integration to help your support and customer success teams work more efficiently. With this connection, your agents can now pull context from customer conversations, access knowledge base content, and even help manage support workflows—all without leaving Dust.

⚙️ How does it work?

Once configured with OAuth authentication (a secure, one-click setup), your agents can query and interact with Intercom data as part of their workflow. The connection is authenticated through your Intercom account, ensuring secure access to your support data.

✨ Concrete Use Cases

Here's how you could use it:

Customer Success Agent: Build an agent that monitors open tickets, summarizes customer issues, and drafts personalized responses based on conversation history and help center articles.

Knowledge Base Assistant: Create an agent that answers internal team questions by searching your Intercom help center, pulling the most relevant articles, and providing context-aware answers.

Support Triage Agent: Design an agent that reviews incoming tickets, categorizes them by urgency and topic, and suggests appropriate responses or escalation paths based on similar past interactions.

📈 Benefits for you

• Faster support response times by giving agents instant access to customer context

• Better consistency across support interactions with centralized knowledge access

• Reduced manual work through automated ticket summaries and response suggestions

• Seamless workflow with secure, native OAuth authentication—no complex API key management

🚀 How to access it?

1. Go to your Dust workspace settings

2. Navigate to the "Connections" or "Integrations" section

3. Select "Intercom" from the available MCP servers

4. Click "Connect" and authenticate with OAuth

5. Start building or updating agents to leverage your Intercom data

This feature is available to all Dust users starting today. But only for US intercom workspace.

Claude Sonnet 4.6 Now Available in Agent Builder

🎯 What is it?

Claude Sonnet 4.6, Anthropic's most capable Sonnet model to date, is now available for you to use when building custom agents in Dust. This latest model brings significant improvements across coding, computer use, long-context reasoning, agent planning, knowledge work, and design—all at the same pricing as Sonnet 4.5.

💡 Why is it useful?

Sonnet 4.6 represents a major leap forward in AI capabilities, bringing Opus-level intelligence at a more accessible price point. Early testing shows that users prefer Sonnet 4.6 over the previous Sonnet 4.5 roughly 70% of the time, and even prefer it to Opus 4.5 (from November 2025) 59% of the time. It's particularly strong at:

• Better coding: Improved consistency, instruction following, and fewer false claims of success

• Computer use: Near human-level capability at navigating complex interfaces and multi-step tasks

• Long-horizon planning: 1M token context window with effective reasoning across entire codebases or lengthy documents

• Agentic workflows: Excellent at complex, multi-step orchestration with tools and data sources

⚙ How does it work?

When creating or editing an agent in the builder, you can now select Claude Sonnet 4.6 as your model. Once stability is confirmed today, it will also become the default model for Dust's global agents, ensuring you get the best performance automatically.

✨ Concrete Use Cases

Here's how you could use it:

Advanced coding agents: Build agents that can review entire codebases, refactor complex logic, and generate production-quality code with fewer iterations—particularly effective for frontend development and financial analysis.

Document analysis agents: Create agents that can read and reason across dozens of research papers, lengthy contracts, or complex enterprise documents in a single request, with improved accuracy on charts, PDFs, and tables.

Workflow automation agents: Deploy agents for multi-step business processes like contract routing, conditional template selection, or CRM coordination—the model excels at branched reasoning and following through on complex instructions.

Computer use agents: Build agents that can interact with specialized software systems, navigate spreadsheets, fill out web forms, and coordinate across multiple browser tabs with near-human accuracy.

📈 Benefits for you

• Better quality at the same cost: Opus-level performance at Sonnet pricing ($3/$15 per million tokens)

• More reliable execution: Significantly reduced hallucinations, better instruction following, and more consistent multi-step task completion

• Greater context capacity: 1M token context window means your agents can work with much larger documents and codebases

• Stronger agentic capabilities: Built specifically for autonomous tool use and complex workflows

🚀 How to access it?

1. Head to the agent builder in Dust

2. When creating a new agent or editing an existing one, select Claude Sonnet 4.6 from the model dropdown

3. Start building—the model is ready to use immediately

Note: Sonnet 4.6 will automatically become the default model for all global agents later today, once we confirm stability in production.

:cite[a41]