🎯 What is it?

Agents can now proactively pause and ask you structured questions mid-conversation when they need clarification. Instead of guessing or making assumptions, they'll present you with single or multi-select options to help guide their next actions.

💡 Why is it useful?

Until now, when an agent faced ambiguity, it would either guess (sometimes incorrectly), take a random path, or get stuck trying to interpret unclear instructions. Now, agents can simply ask you directly—turning uncertainty into a quick, interactive exchange. This prevents wasted time, reduces errors, and makes conversations feel more collaborative and intuitive.

⚙️ How does it work?

When an agent needs input to proceed, it will pause and present you with a clear question and predefined answer options (single-choice or multiple-choice). You select your answer, and the agent continues with exactly the information it needs.

Concrete Use Cases

Here's how you could use it:

Research workflow: You ask an agent to "analyze our competitors." Instead of picking arbitrary companies, it asks: "Which competitors should I focus on?" with options like [Company A, Company B, Company C, All of the above].

Content formatting: You request a report summary. The agent asks: "What format do you prefer?" with options like [Bullet points, Paragraph form, Executive summary].

Data prioritization: You ask for insights from multiple sources. The agent clarifies: "Which data sources should I prioritize?" offering [Internal reports, Public data, Customer feedback, All sources].

📈 Benefits for you

  • More accurate outputs: Agents work with your explicit input instead of assumptions

  • Faster resolution: No back-and-forth to correct misunderstandings

  • Better control: You guide the agent's direction at key decision points

  • Richer interactions: Conversations feel more natural and collaborative

🚀 How to access it?

This feature is available by default for all agents on Dust and Deep Dive, and works seamlessly in Slack conversations as well. No configuration needed—your agents will automatically ask questions when they need clarification.

🎯 What is it?

Workspace admins can now configure Dust conversations to be private by default. When this setting is enabled, conversation URLs are only accessible to participants—anyone else who tries to access the link will see a 404 error, ensuring the conversation's existence isn't even revealed to non-participants.

💡 Why is it useful?

This feature addresses the risk of accidentally sharing sensitive conversations through URLs. While Dust conversations are powerful collaboration tools, sometimes conversation links get shared unintentionally (in Slack, email, or screenshots). With private-by-default URLs, you get an extra layer of protection against accidental leakage while maintaining flexibility when you explicitly need to share.

⚙️ How does it work?

When a workspace admin enables this setting, all new conversations automatically become private—only people directly participating can access them via URL. Participants can still use @mentions to invite others to join conversations, and if needed, anyone in the conversation can flip it back to "accessible to workspace members" from the conversation menu.

Concrete Use Cases

Here's how you could use it:

HR and sensitive discussions: When discussing performance reviews, salary negotiations, or confidential employee matters, conversations stay strictly between participants even if someone accidentally copies the URL.

Strategic planning: When working on confidential product launches, M&A discussions, or competitive analysis with a small team, you can ensure the conversation doesn't leak to the broader workspace if a link is shared out of context.

📈 Benefits for you

  • Enhanced security: Reduce the risk of sensitive information leakage through shared URLs

  • Peace of mind: Know that conversations stay private unless you explicitly choose to share them

  • Flexible control: Keep the ability to make specific conversations workspace-accessible when collaboration requires it

  • Maintain collaboration: @mentions still work seamlessly, so you can invite people without compromising privacy

🚀 How to access it?

Workspace admins can enable this feature by navigating to Admin → Workspace Settings and toggling the private-by-default conversation URLs setting. Once enabled, all new conversations will be private by default, while participants can override this on a per-conversation basis from the conversation menu.

🎯 What is it?

You can now import skills directly into Dust from a GitHub repository or by uploading a .zip file from your computer. This new capability gives you more flexibility in how you manage and deploy your skills across your workspace.

💡 Why is it useful?

If you're managing multiple skills or working with a team that maintains skills in a version control system, you previously had to manually copy and paste code into Dust. This new import feature allows you to centralize your skills in GitHub (or any other repository) and keep them in sync with your CI/CD pipeline, ensuring your Dust agents always use the latest versions.

How does it work?

Simply provide a GitHub repository URL or upload a .zip file containing your skill files. Dust will import the skill structure and make it available in your workspace.

Concrete Use Cases

Here's how you could use it:

Development teams maintaining shared skills: Your engineering team maintains a repository of company-specific skills (e.g., data formatting, internal API integrations). When you update the skill in GitHub, you can quickly re-import it to Dust to keep all agents synchronized.

Distributing skills across workspaces: You've built a powerful skill for market research and want to deploy it across multiple Dust workspaces (different departments or clients). Export it once as a .zip and import it wherever needed.

📈 Benefits for you

  • Version control: Keep your skills in Git alongside your other code, with full history and collaboration features

  • Automation: Integrate skill updates into your existing CI/CD workflows

  • Portability: Easily share and duplicate skills across workspaces without manual copying

  • Consistency: Ensure all team members are using the same version of your custom skills

🚀 How to access it?

This feature is available to everyone. When creating or updating a skill, look for the new import options that allow you to specify a GitHub repository URL or upload a .zip file.

🎯 What is it?

Steering transforms how you interact with Dust agents by allowing you to send messages while the agent is working. You can now see every step of the agent's work in real-time—thinking, tool calls, searches—and redirect it on the fly without canceling or losing progress. Additionally, messages are now scoped to one agent at a time, displayed in the input bar, so you no longer need to use @mentions.

💡 Why is it useful?

Previously, conversations with agents were strictly turn-based: you'd send a message, wait for the complete response, and only then could you course-correct if needed. This made it difficult to guide the agent early when you saw it heading in the wrong direction, and you had no visibility into what was happening behind the scenes. Steering solves this by letting you shape the output as it's being built, not after it's done.

How does it work?

As soon as an agent starts working, you'll see live updates of each step it takes. If you notice it's going off track or you want to add context, simply send a new message—the agent will incorporate your input immediately without restarting from scratch.

Concrete Use Cases

Here's how you could use it:

Research and analysis: You ask an agent to research a topic, but after seeing the first few searches, you realize you need a different angle. Instead of waiting for the full response, you immediately steer it: "Actually, focus on European regulations instead."

Data exploration: An agent starts querying multiple data sources, and you see it's pulling from the wrong database. You send a quick message to redirect it before it completes unnecessary work, saving time and getting accurate results faster.

📈 Benefits for you

  • Save time: Redirect agents early instead of waiting for full responses you'll need to regenerate

  • Better control: Guide the conversation dynamically based on what you see happening

  • Full transparency: Understand exactly what the agent is doing at each moment

  • Smoother workflow: No more @mentions needed when working with a single agent

🚀 How to access it?

Steering is now available to everyone automatically. Start a conversation with any agent and try sending a follow-up message while it's working. For complete details and examples, visit the full documentation.


🎯 What is it?

The Dust browser extension is now officially available on Firefox! You can install it directly from the Firefox Add-ons store and enjoy the same seamless Dust experience across all major browsers.

💡 Why is it useful?

Many of you use Firefox as your primary browser, and until now, the Dust extension was only available on Chromium-based browsers. We've expanded our support to ensure all teams can access Dust's capabilities directly from their preferred browser, regardless of which one they use.

How does it work?

Simply visit the Firefox Add-ons store and install the Dust extension. Once installed, you'll have quick access to your agents and Dust features right from your browser toolbar, just like on Chrome or Edge.

Concrete Use Cases

Here's how you could use it:

For Firefox users: Finally get the same browser integration your Chrome-using colleagues have been enjoying—quick access to agents, easy content sharing, and seamless workflows without switching browsers.

For mixed-browser teams: Ensure everyone on your team can use Dust extension features regardless of their browser preference, making collaboration more consistent and inclusive.

📈 Benefits for you

  • Browser flexibility: Use Dust on Firefox, Chrome, Edge, or any Chromium-based browser

  • Consistent experience: Same features and functionality across all supported browsers

  • No workflow changes: Firefox users can now integrate Dust into their daily browsing without switching browsers

🚀 How to access it?

Visit the Firefox Add-ons store: https://addons.mozilla.org/en-US/firefox/addon/dust/ and click "Add to Firefox". The extension will be ready to use immediately after installation.

🎯 What is it?

We've expanded our Microsoft Teams integration with two new capabilities: agents can now list your Teams meetings and retrieve their transcripts directly within Dust. This means your meeting content is now accessible to your agents, just like your other connected data sources.

💡 Why is it useful?

Meeting discussions contain valuable information—decisions made, action items assigned, key insights shared—but this knowledge often stays locked in transcript files or requires manual review. By making transcripts accessible to your agents, you can automatically extract value from your meetings without manual work.

⚙️How does it work?

Once your workspace admin reconnects the Microsoft Teams tool (to approve the new permissions), agents can access meeting transcripts using two new tools: one to list meetings, and another to retrieve transcript content when available.

Concrete Use Cases

Here's how you could use it:

Meeting Follow-up Agent: Create an agent that reviews your leadership team's weekly sync, extracts action items, and sends a summary to relevant stakeholders automatically.

Cross-team Knowledge Capture: Build an agent that monitors product planning meetings, identifies feature decisions and requirements, and updates your product documentation or project tracker.

Personal Meeting Assistant: Set up an agent that summarizes all your meetings from the past week, highlighting decisions you participated in and tasks assigned to you.

📈 Benefits for you

  • Save time: No more manual note-taking or transcript review

  • Capture knowledge: Turn meeting discussions into searchable, actionable insights

  • Enable new workflows: Automate meeting follow-ups, summaries, and action item tracking

  • Connect the dots: Let agents reference meeting decisions alongside your other company knowledge

🚀 How to access it?

Action required: A workspace admin must reconnect the Microsoft Teams tool in your Dust workspace to approve the new permissions (OnlineMeetings.Read and OnlineMeetingTranscript.Read.All). Once reconnected, the new meeting transcript tools will be available to all agents in workspaces using Microsoft Teams.

🎯 What is it?

You can now invite specific people to view a Frame by sending them an email invitation. Recipients receive a direct link to access the Frame, even if they're not part of your Dust workspace.

💡 Why is it useful?

Previously, Frame sharing was all-or-nothing at the workspace level. This new capability gives you granular control over who can see your Frames, making it much easier to collaborate with specific stakeholders, partners, or team members. You can also track who has viewed your Frame.

How does it work?

When sharing a Frame, you can now enter email addresses of people you want to invite. Each person receives an email with a secure link to access that specific Frame. This respects your workspace sharing policy settings.

Concrete Use Cases

Here's how you could use it:

Executive reporting: Share a sales dashboard Frame with your CEO and CFO without giving them access to all workspace Frames.

Client presentations: Send a project status Frame directly to external clients or partners for review, while keeping other internal Frames private.

Cross-team collaboration: Share specific data visualizations with stakeholders from other departments who need visibility on just that information.

📈 Benefits for you

  • Precise control: Share Frames on a need-to-know basis instead of workspace-wide

  • Better collaboration: Work seamlessly with external partners and selective internal stakeholders

  • Visibility tracking: See who has actually viewed your Frame

  • Time-saving: No more screenshots or manual exports—just send a direct link

🚀 How to access it?

This feature is now available to everyone. When viewing any Frame, look for the sharing options and select "Invite by email" to start sharing with specific people.

🎯 What is it?

Dust now connects directly to Amplitude through their remote MCP (Model Context Protocol) server. Your agents can now access Amplitude's product analytics platform to query data, analyze experiments, manage dashboards, create cohorts, and more—all through natural language conversations.

💡 Why is it useful?

Amplitude is a leading product analytics platform that holds critical data about how users interact with your product. Until now, accessing this data required switching contexts, learning the Amplitude interface, or writing queries manually. With this integration, you can ask your Dust agents to retrieve and analyze Amplitude data conversationally, making product insights more accessible to your entire team.

How does it work?

The integration uses Amplitude's official remote MCP server. Simply connect the appropriate server (US or EU, depending on your data residency requirements) to your Dust workspace's MCP catalog, and your agents can start querying Amplitude directly.

Concrete Use Cases

Here's how you could use it:

Product Manager reviewing experiment results: "Show me the conversion rate for the checkout experiment we launched last week and compare it to the control group."

Customer Success analyzing user behavior: "Create a cohort of users who completed onboarding in the last 30 days but haven't returned since."

Executive reviewing dashboard data: "Pull the key metrics from our weekly product dashboard and summarize any significant changes from last week."

📈 Benefits for you

  • Democratize product data: Make Amplitude insights accessible to anyone on your team through natural language, not just analytics experts

  • Faster decision-making: Get answers about product performance without leaving your workflow

  • Automated reporting: Build agents that regularly pull and synthesize Amplitude data for stakeholder updates

🚀 How to access it?

Connect Amplitude to your Dust workspace by adding the appropriate remote MCP server to your MCP catalog:

  • US residency: https://mcp.amplitude.com/mcp

  • EU residency: https://mcp.eu.amplitude.com/mcp

Once connected, your agents will be able to interact with Amplitude's capabilities through conversation. You'll need your Amplitude credentials to complete the setup.

📌 Context

When you create a new Notion MCP tool in Dust, it will now use Notion's official MCP server instead of our previous implementation. We've made this change to improve both the user experience and the reliability of Notion integrations.

🔄 Impact on Dust

We've transitioned to Notion's official MCP server, which brings two significant improvements:

Better authentication model ("run as you"):

  • The tool now has access to everything you can access in Notion—no need to manually select which pages to share

  • When you modify a document or add a comment through Dust, it appears as coming from you, not from the Dust integration

Improved reliability:

  • Better handling of page relations and databases

  • Faster searches and fewer loops when finding related pages

  • Overall more stable performance

Early feedback from users has been very positive, with reports of faster and more reliable operations.

👤 Impact for you

If you're creating new Notion MCP tools:

You'll automatically benefit from the improved official implementation. The authentication flow will be simpler, and you'll experience better performance.

If you already have Notion MCP tools:

Your existing tools will continue to work exactly as before using the previous implementation. There's no disruption to your current workflows.

Important clarification:

This change only affects Notion MCP tools (created under Spaces / Add Tools). Your Notion Connector remains completely unaffected and continues to work as usual.

✅ Actions required

No action required on your part for existing tools—they'll keep working as-is.

If you have agents that used Notion tools before, you can edit them and replace them with the new tools (once you have added them to your workspace).

🎯 What is it?

Workspace admins now have access to a comprehensive analytics dashboard directly in Dust, plus a new public API endpoint to export all your workspace data. The dashboard gives you real-time visibility into how Dust is being used across your organization—from daily active users to agent performance—all with interactive charts and CSV export capabilities. The public API (GET /api/v1/w/{wId}/analytics/export) lets you programmatically pull 7 different data tables (usage metrics, active users, sources, agents, users, skill usage, and tool usage) to integrate with your own BI tools.

💡 Why is it useful?

As a workspace admin, you need clear visibility into adoption and ROI to justify investment and drive Dust usage across your organization. Until now, getting this data required manual CSV exports or reaching out to Customer Success for custom reports. This dashboard brings Dust in line with what you expect from enterprise tools—self-serve analytics that help you make data-driven decisions.

How does it work?

The interactive dashboard is available directly in your Dust workspace. You can select flexible time ranges (7, 15, 30, or 90 days), view activity trends over time, monitor adoption metrics (DAU/WAU/MAU), see usage by source (web, Slack, extension, API), explore tool usage patterns, and identify your top-performing agents. Every chart can be exported to CSV for deeper analysis. The API endpoint works with simple GET requests and returns data in CSV format for easy integration.

Concrete Use Cases

Here's how you could use it:

Executive Reporting: Pull monthly analytics showing DAU growth and top 10 agents by usage to demonstrate ROI to leadership and secure budget for broader rollout.

Adoption Campaigns: Identify departments with low WAU rates and channels where engagement is highest, then target outreach through those preferred channels (Slack vs. web vs. extension).

Agent Optimization: Track which agents are being used most frequently and by whom, then deprecate underused agents and promote high-value ones in your internal communications.

BI Integration: Feed the API data into Tableau, Power BI, or your internal dashboards to combine Dust metrics with other productivity KPIs across your tech stack.

📈 Benefits for you

  • Save time: No more manual exports or waiting for CS reports

  • Make informed decisions: Real-time data on what's working and where to focus your efforts

  • Prove value: Concrete metrics to demonstrate ROI to stakeholders

  • Flexibility: Use the dashboard for quick insights or the API for deep integrations

🚀 How to access it?

The analytics dashboard is available now to all workspace admins on all plans. Look for the Analytics section in your workspace settings. The API endpoint is live at GET /api/v1/w/{wId}/analytics/export—check our API documentation for authentication details and available data tables.


⚠️ API Deprecation Notice

📌 Context

Two legacy API endpoints (/api/v1/w/{wId}/usage and /api/v1/w/{wId}/workspace-usage) are being deprecated and will be sunset on June 1, 2026. These are being replaced by the new /api/v1/w/{wId}/analytics/export endpoint, which provides all the same data plus additional metrics (skill usage, tool usage, per-agent and per-user breakdowns).

🔄 Impact on Dust

We're consolidating analytics endpoints to provide a single, more powerful API that covers all workspace analytics needs while maintaining consistency with the new dashboard experience.

👤 Impact for you

If you're using the old endpoints: You need to migrate to the new endpoint before June 1, 2026. After that date, the legacy endpoints will stop working.

If you're not using the API: No impact—the dashboard works out of the box with no changes needed.

Actions required

Before June 1, 2026:

  1. Audit any integrations, scripts, or BI tools currently calling /api/v1/w/{wId}/usage or /api/v1/w/{wId}/workspace-usage

  2. Update them to use /api/v1/w/{wId}/analytics/export with the appropriate data table parameter

  3. Test the new endpoint—the new API is a strict superset, so you'll get everything you had before plus more

Need help with migration? Reach out to your Customer Success Manager or [email protected]—we're here to help ensure a smooth transition.