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
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.
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.
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.
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).
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:
Audit any integrations, scripts, or BI tools currently calling /api/v1/w/{wId}/usage or /api/v1/w/{wId}/workspace-usage
Update them to use /api/v1/w/{wId}/analytics/export with the appropriate data table parameter
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.
Workspace admins now have access to a comprehensive analytics dashboard directly within Dust, plus a new public API endpoint for programmatic data access. The dashboard provides real-time visibility into adoption metrics (DAU/WAU/MAU), activity trends (messages, conversations), usage breakdown by source (web, Slack, extension, API), tool usage patterns, and top-performing agents. Each chart supports CSV export and offers flexible time ranges (7, 15, 30, or 90 days).
For teams that need to integrate Dust data into their own business intelligence tools, the new GET /api/v1/w/{wId}/analytics/export endpoint enables programmatic access to 7 data tables: usage metrics, active users, sources, agents, users, skill usage, and tool usage.
💡 Why is it useful?
Enterprise teams need self-service visibility into how Dust is being adopted across their organization to measure ROI and drive engagement. Until now, getting this data required manual CSV exports or reaching out to Customer Success for custom reports. This brings Dust's analytics capabilities in line with enterprise expectations for modern SaaS tools.
✨ Concrete Use Cases
Here's how you could use it:
Executive reporting: Export monthly adoption metrics to include in your quarterly AI transformation reports, showing DAU/MAU trends and demonstrating ROI to leadership.
Usage optimization: Identify which agents are most popular and which sources drive the most engagement, then use those insights to optimize your Dust rollout strategy and training programs.
BI integration: Pipe Dust analytics data into your existing Tableau, Looker, or PowerBI dashboards alongside other tools to create a unified view of productivity tool adoption.
📈 Benefits for you
Self-service insights: No more waiting for manual reports—get instant visibility into adoption patterns
Data-driven decisions: Use concrete metrics to guide your Dust rollout strategy
Flexible export: Download charts as CSV or pull data programmatically via API
Executive-ready: Generate adoption reports that demonstrate value to stakeholders
🚀 How to access it?
The analytics dashboard is available now to all workspace admins across all plans. Access it from your workspace admin panel. For API access, refer to the documentation for the new /api/v1/w/{wId}/analytics/export endpoint.
⚠️ API Deprecation Notice
📌 Context
The legacy analytics endpoints /api/v1/w/{wId}/usage and /api/v1/w/{wId}/workspace-usage are now deprecated and will be sunset on June 1, 2026.
🔄 Impact on Dust
We've built a new, more comprehensive analytics API that supersedes these legacy endpoints, providing richer data and better functionality.
👤 Impact for you
If you or your team are using the old endpoints: You'll need to migrate to the new /api/v1/w/{wId}/analytics/export endpoint before June 1, 2026. The new endpoint is a strict superset—it covers everything the old endpoints provided plus adds skill usage, tool usage, and detailed per-agent and per-user breakdowns.
If you're not using these endpoints: No impact—no action needed.
✅ Actions required
Review your integrations: Check if any of your systems or scripts are calling /api/v1/w/{wId}/usage or /api/v1/w/{wId}/workspace-usage
Plan your migration: Update those integrations to use the new /api/v1/w/{wId}/analytics/export endpoint before June 1, 2026
Reach out if needed: If you need assistance with migration, contact your Customer Success team
Three improvements to how Dust agents respond in Slack, shipping together.
🔄 Smoother streaming
Agent responses now appear in real time as they're being generated, using Slack's native streaming. The experience feels faster and more alive, no more waiting for a full response to land before you can start reading !
🔎 See what your agent is doing
While an agent works, a live progress indicator shows which tools it's using and what it's doing with them. For web searches, you can see the query it ran. For browsing, you can see the sites it visited and the sources it pulled from. Once the agent is done, the indicator disappears cleanly.
✨ Better formatted responses
Tables, dividers, and code blocks now render properly in Slack. Agents that output structured content like pipeline summaries, incident reports, or side-by-side comparisons will now display the way they were meant to, without workarounds.
⚠️
Responses that include file uploads use the previous format for now.
🔥 Concrete Use Cases
All your current slack use cases, enhanced !
🚀 How to access it?
This feature is rolling out progressively to all Slack users this week. No action required on your part, you'll automatically see these improvements in your Slack workspace when they're available.
We've released a new official GitHub Action called dust-github-action that lets you manage your Dust Skills and Agent configurations directly from your Git repository. You can now version-control your Dust setup, review changes through pull requests, and automatically sync your workspace from CI/CD pipelines.
💡 Why is it useful?
Managing Dust configurations through code gives you the same benefits you already get with your application code: change history, peer review, rollback capabilities, and automation. Instead of manually updating agents and skills in the Dust interface, you can define them in your repository and let your CI pipeline keep everything in sync. This is particularly valuable for teams that want to maintain consistency across workspaces, review configuration changes before deployment, or integrate Dust setup into their existing development workflows.
⚙ How does it work?
The GitHub Action provides methods to "upsert" (create or update) Skills and Agent configurations from your repository into your Dust workspace. When you push changes to your repo or merge a PR, the action automatically applies those configuration changes to your workspace.
✨ Concrete Use Cases
Here's how you could use it:
Development workflow: Define your agents in YAML files in your repo, have teammates review changes in pull requests, then automatically deploy approved configurations to your production Dust workspace when merged to main.
Multi-workspace management: Maintain a single source of truth for your agent configurations and sync them across development, staging, and production Dust workspaces using different GitHub Actions workflows.
Audit & rollback: Track every change to your Dust setup in Git history, see who made what changes and why, and easily roll back to previous configurations if needed.
📈 Benefits for you
Better collaboration: Review agent and skill changes through pull requests before they go live
Version control: Full history of all configuration changes with the ability to roll back
Automation: Reduce manual work by syncing configurations automatically from CI
Consistency: Keep multiple workspaces aligned using the same configuration source
Integration: Fits into your existing development workflows and tooling
🚀 How to access it?
The GitHub Action is available now for all workspace admins and developers using GitHub Actions. Check out the repository and documentation to get started: https://github.com/dust-tt/dust-github-action
The feature is in General Availability (GA) and ready for production use.
You can now choose which email address to send from when using Dust agents with the Gmail tool. If you have aliases configured in your Gmail account (like [email protected] or [email protected]), agents can now send emails from these addresses instead of only your personal email.
💡 Why is it useful?
Many professionals use email aliases to represent teams, departments, or shared inboxes. Until now, when an agent sent an email on your behalf, it could only use your primary Gmail address. This created limitations when you needed to maintain a specific professional identity or represent a team.
⚙️ How does it work?
When you ask an agent with the Gmail tool to send an email, you can now specify which of your configured Gmail aliases to use as the sender address. The agent will send the email from that alias, as long as it's properly set up in your Gmail account.
✨ Concrete Use Cases
Here's how you could use it:
Customer Support: Ask an agent to craft and send responses from your [email protected] alias, maintaining consistency in customer communications while saving time on routine replies.
Team Communications: Have an agent send project updates or meeting summaries from your team's shared email address (like [email protected]), ensuring all correspondence appears to come from the team rather than an individual.
📈 Benefits for you
Professional consistency: Maintain the right email identity for each context
Team representation: Send on behalf of groups or departments
Time savings: Automate email tasks without losing control over sender identity
Better organization: Keep communications aligned with your existing email structure
🚀 How to access it?
This feature is automatically available if you're using the Gmail tool. Simply ensure your aliases are configured in your Gmail account settings, then specify which address you'd like to use when asking an agent to send an email.
