Dust Release Notes
Last updated: Apr 7, 2026
- Apr 6, 2026
- Date parsed from source:Apr 6, 2026
- First seen by Releasebot:Apr 7, 2026
Send Emails from Your Gmail Aliases
Dust now supports sending Gmail agent emails from configured aliases, letting users choose addresses like [email protected] or [email protected] instead of only a primary personal account. It helps teams keep the right sender identity for support, updates, and other communications.
🎯 What is it?
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.
Original source Report a problem - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
API Keys Can Now Be Scoped to Multiple Spaces
Dust adds multi-space API key support, letting workspace admins scope one key to multiple spaces for tighter least-privilege access and simpler integration management. The feature is live now, and existing keys have been automatically migrated.
What is it?
You can now configure a single API key to work across multiple spaces in your workspace, instead of being limited to one space at a time. This gives you more granular control over how integrations access your Dust environment.
Why is it useful?
Previously, if you wanted an integration to access multiple spaces, you had two options: either give it workspace-wide access (too permissive) or create separate API keys for each space (too complex). This new capability follows the principle of least privilege—you can grant access to exactly the spaces an integration needs, nothing more and nothing less.
How does it work?
When creating or editing an API key in the admin UI, you can now select multiple spaces that the key should have access to. The permission resolution has been updated to handle this multi-space access smoothly.
Concrete Use Cases
Here's how you could use it:
Export shared agents: You have an agent shared across 3 different team spaces (Sales, Marketing, Customer Success). You can now create one API key scoped to these 3 spaces to export or sync that agent's data, instead of managing 3 separate keys.
Controlled cross-team integration: Your data pipeline needs to access specific spaces (Finance and Legal) but not others. You can create a single API key with access to only those two spaces, maintaining security while simplifying key management.
Benefits for you
- Better security: Apply least-privilege principles without operational complexity
- Simpler management: One key for multiple spaces instead of juggling multiple keys
- Unlock new workflows: Run integrations across controlled sets of spaces that weren't practical before
How to access it?
This feature is already live for all workspace admins. When you create or manage API keys in your workspace admin panel, you'll see the option to select multiple spaces. All existing API keys have been automatically migrated, so nothing changes unless you want to adjust the configuration.
Original source Report a problem All of your release notes in one feed
Join Releasebot and get updates from Dust and hundreds of other software products.
- Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
Create Triggers on Any Agent You Can Talk To
Dust adds triggers for every agent you can access, including default agents like dust and deep-dive. Users can automate agent interactions from the Agent Details side panel and manage all triggers centrally from their profile page.
🎯 What is it?
You can now create your own triggers on every agent you have access to, including default agents like
dustanddeep-dive. Triggers allow you to automate agent interactions based on specific events or conditions, extending automation beyond just the agents you've built yourself.💡 Why is it useful?
Previously, trigger creation might have been limited to agents you owned or edited. We believe that if you can talk to an agent, you should be able to automate it. This opens up powerful automation possibilities across your entire workspace, letting you leverage any agent in your automated workflows.
⚙ How does it work?
Create triggers directly from the Agent Details side panel of any agent you want to automate. Once created, all your triggers are centralized in your profile page where you can easily manage and monitor them.
✨ Concrete Use Cases
Here's how you could use it:
Automated research digest: Create a trigger on the
deep-diveagent to automatically compile weekly competitive intelligence reports every Monday morning, even though you don't own that agent.Team notification workflows: Set up triggers on shared team agents to automatically notify specific channels when certain conditions are met, without needing editor permissions on those agents.
Cross-agent automation: Build workflows that chain together multiple shared agents via triggers, creating sophisticated automation pipelines using agents created by different people across your organization.
📈 Benefits for you
- Democratized automation: Automate any agent you use, not just the ones you built
- Centralized management: Find and control all your triggers in one place on your profile page
- Better collaboration: Leverage agents built by colleagues in your automated workflows
- Transparency: Agent editors can see and audit all triggers on their agents; admins maintain full oversight
🚀 How to access it?
- Navigate to any agent you have access to
- Open the Agent Details side panel
- Create your trigger with your desired configuration
- Manage all your triggers from your profile page
Agent editors can view and audit all triggers created on their agents directly in the builder. Workspace admins can delete any trigger if needed.
Original source Report a problem - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:Apr 7, 2026
Discover Skills - Find and leverage workspace capabilities directly in your agents
Dust adds Discover Skills, letting agents automatically find and use discoverable workspace skills. Builders can mark skills as discoverable so global agents like @dust and @deep-dive tap into them without manual setup, improving responses across the workspace.
What is it?
Dust now includes a "Discover Skills" feature that allows agents to automatically find and use relevant skills from your workspace. Builders can flag specific skills as "discoverable," making them available to global agents like @dust and @deep-dive without manual configuration.
Why is it useful?
Previously, if you wanted an agent to use a specific skill, you had to manually configure it for each agent. This created friction and meant many useful workspace skills went underutilized. With discoverable skills, your agents can now intelligently tap into your organization's collective capabilities, improving the baseline experience for everyone in your workspace.
How does it work?
Builders can mark their skills as "discoverable" when creating or editing them. Once flagged, these skills become available to global agents, which can automatically detect when a skill is relevant to a user's request and activate it on the fly.
Concrete Use Cases
Here's how you could use it:
Sales team collaboration: A sales ops builder creates a "CRM Integration" skill and marks it discoverable. Now when anyone asks @dust about customer data, the agent automatically uses that skill without individual setup.
Knowledge sharing: Your engineering team builds a "Code Review Helper" skill. Mark it as discoverable, and @deep-dive can leverage it whenever someone asks technical questions, instantly improving responses across the workspace.
Benefits for you
- Zero configuration: End users get access to powerful skills without any setup
- Better agent responses: Global agents like @dust deliver more accurate, context-aware answers by tapping into workspace expertise
- Increased skill adoption: Your team's best skills get used more widely, maximizing ROI on skill development
- Improved baseline experience: Everyone in the workspace benefits from collective knowledge automatically
How to access it?
For Builders: When creating or editing a skill, look for the new "Make discoverable" option and enable it for skills you want to share workspace-wide.
For Users: Simply use @dust or @deep-dive as usual - they'll automatically discover and leverage relevant skills when needed.
Original source Report a problem - Mar 31, 2026
- Date parsed from source:Mar 31, 2026
- First seen by Releasebot:Apr 7, 2026
Changelog Update
Dust adds Salesforce MCP write support, letting agents create and update Salesforce records with approval. The tool now goes beyond read-only access to help teams manage companies, contacts, opportunities, notes, and more while keeping CRM updates safer and faster.
Salesforce MCP tool can now create and update objects
🎯 What is it?
The Salesforce MCP tool has evolved beyond read-only access. Your Dust agents can now create and update records directly in Salesforce—including companies, contacts, opportunities, notes, and other objects. This means agents can take actions on your behalf, not just retrieve information.
💡 Why is it useful?
This was one of our most frequently requested features. Until now, agents could read data from Salesforce but couldn't modify it, requiring you to manually update records after getting insights. With the introduction of medium stakes for agent actions, we've made it safe for agents to perform write operations with appropriate guardrails in place.
🚀 How to access it?
If you're already using the Salesforce MCP tool with your agents, the write capabilities are available after an admin checks the "Create Object" tool on, from the Admin>Tools>Salesforce menu
Simply ask your agent to create or update a Salesforce record—you'll be prompted to approve the action before it's executed.
If you haven't set up the Salesforce MCP tool yet, check our documentation or reach out to your Customer Success Manager to get started.
✨ Concrete Use Cases
Here's how you could use it:
Automated opportunity updates: After a sales call, an agent can analyze the conversation transcript and create follow-up tasks or update the opportunity stage in Salesforce directly.
Contact enrichment: When you share new information about a prospect, an agent can automatically create or update the contact record with relevant details like job title, company, or notes from your conversation.
Activity logging: Agents can create notes or log activities in Salesforce after customer interactions, ensuring your CRM stays up-to-date without manual data entry.
📈 Benefits for you
- Save time by eliminating manual data entry between Dust and Salesforce
- Maintain data accuracy with real-time updates to your CRM
- Enable end-to-end workflows where agents can both analyze and act on Salesforce data
- Stay in control with medium stakes approval for all write operations
- Mar 30, 2026
- Date parsed from source:Mar 30, 2026
- First seen by Releasebot:Apr 7, 2026
Email your agents directly at [email protected]
Dust adds email support for agents, letting users send or forward messages to [email protected] and get replies back in their inbox. The new opt-in capability brings Dust workflows to email while keeping conversations accessible in the web app.
🎯 What is it?
You can now interact with your Dust agents directly via email. Simply send or forward an email to [email protected] and your agent will process it and reply back to you. This works just like talking to an agent in Slack or the web app, but right from your inbox.
💡 Why is it useful?
Many teams work primarily in email—customer support threads, vendor communications, contracts, bug reports. Until now, you had to switch to Dust's web app or Slack to get help from your agents. With email integration, agents meet you where you already work, making it faster to get answers, draft replies, or process information without context-switching.
⚙ How does it work?
Once enabled in your workspace settings, you can send or forward emails to any agent using the format [email protected]. The agent processes your request and replies only to you (the sender). All conversations triggered by email are accessible in the Dust web app, just like agent conversations from Slack or Teams. If an agent needs authorization to use a specific tool, you'll receive a validation email with secure allow/decline links.
✨ Concrete Use Cases
Here's how you could use it:
- Customer Support: Forward a customer complaint to your support agent and ask it to summarize the issue and suggest a reply draft.
- Contract Review: Send a vendor agreement to a specialized legal/compliance agent and get a quick analysis without leaving your email thread.
- Internal Workflows: CC an agent on an internal discussion thread and ask it to extract action items, create tickets, or draft follow-up communications.
- Bug Triage: Forward a bug report from a client to your technical agent for initial analysis and categorization.
📈 Benefits for you
- Faster workflows: No need to copy-paste email content into Dust—just forward and ask
- Stay in context: Get agent help without leaving your inbox
- Flexible collaboration: Use agents as you would a colleague—forward, CC, or send directly
- Consistent experience: Same agent capabilities as Slack or web, accessible from email conversations in Dust
🚀 How to access it?
This feature is opt-in. To enable it:
- Go to Workspace Settings → Capabilities → Email agents
- Turn on the feature
- Start emailing your agents at [email protected]
📖 Full documentation available here: https://docs.dust.tt/docs/email-agents
🔒 Security note:
Just as you wouldn't click suspicious links in emails, avoid forwarding suspicious or untrusted emails to agents to minimize prompt injection risks.
Original source Report a problem - Mar 20, 2026
- Date parsed from source:Mar 20, 2026
- First seen by Releasebot:Apr 7, 2026
Dust Extension — Agents Now Understand Your Browser
Dust adds full browser awareness to its Chrome Extension, letting agents read current tabs, work across multiple pages, click and type on websites, and use existing MCP tools like Notion and Gmail inside the extension for faster, more seamless browser workflows.
What is it?
The Dust Chrome Extension now gives agents full browser awareness. Agents can automatically detect when they need content from your current page, work across multiple tabs simultaneously, and even interact with web pages directly through clicks and keystrokes. Plus, all your existing MCP tools (like Notion and Gmail) now work seamlessly within the extension.
Why is it useful?
Until now, working with browser content required manual steps—copying text, taking screenshots, or switching back to the web app. This update removes that friction entirely. Your agents can now understand and act on what you're looking at in real-time, making browser-based workflows dramatically faster and more intuitive.
How does it work?
When an agent needs information from your browser, it automatically requests permission to access the relevant tab content or screenshots. Once granted, agents can read pages, navigate between tabs, and even perform actions like filling forms or clicking buttons—all while respecting your privacy with explicit permission prompts.
Concrete Use Cases
Here's how you could use it:
Research synthesis: Ask an agent to "summarize the key points from these three open articles" and it will analyze all tabs at once, creating a unified summary without you switching windows.
Form automation: Tell an agent to "fill out this application form with information from my resume" and it can read your resume from one tab while interacting with the form in another.
Competitive analysis: With multiple competitor websites open, ask "compare pricing structures across these pages" and the agent will extract and analyze the information across all tabs.
Email drafting with context: While reading a LinkedIn profile or company website, ask an agent to "draft an outreach email based on this page" using your Gmail MCP tool, all without leaving your browser.
Benefits for you
- Zero context switching: Work directly where you are without copying content or moving to the web app
- Faster workflows: Agents access what they need automatically with your permission
- New possibilities: Browser interaction and multi-tab awareness unlock entirely new use cases
- Unified experience: All your existing MCP tools now work in the extension just like in the web app
How to access it?
Update your Chrome extension to the latest version. The new capabilities are available immediately—just start a conversation with an agent and it will automatically request browser access when needed.
Original source Report a problem - Mar 20, 2026
- Date parsed from source:Mar 20, 2026
- First seen by Releasebot:Apr 7, 2026
Browser Extension Now Available on Arc & Edge
Dust expands its browser extension to Arc, Microsoft Edge, and other Chromium-based browsers, bringing the same Dust experience beyond Chrome for a more flexible workflow wherever users browse.
What is it?
The Dust browser extension is now compatible with Arc and Microsoft Edge browsers (and all Chromium-based browsers), in addition to Chrome. You can now use Dust's browser extension on the browser that fits your workflow best.
Why is it useful?
Many teams use Arc for its innovative interface and productivity features, while Microsoft Edge is the standard browser in many enterprise environments. Until now, Dust extension users were limited to Chrome. This update ensures you can access Dust's capabilities directly in your browser of choice, wherever you work.
How does it work?
The same Dust extension you know from Chrome now installs seamlessly on Arc and Edge. All features work identically across browsers.
Concrete Use Cases
Here's how you could use it:
- Arc users: Integrate Dust into your split-view workflow and command bar for faster access to your agents while browsing research, documentation, or competitive analysis.
- Edge users in enterprise environments: Access Dust agents directly within your company's standard browser without needing to switch to Chrome for extension functionality.
Benefits for you
Work with Dust where you're already working—no need to switch browsers or compromise on your preferred tools. This means faster access to your agents and a more integrated workflow.
How to access it?
If you use Arc or Edge: Simply visit the Chrome Web Store and install the Dust extension as you would for Chrome. The extension works natively on all Chromium-based browsers.
Original source Report a problem - Mar 20, 2026
- Date parsed from source:Mar 20, 2026
- First seen by Releasebot:Apr 7, 2026
Google Drive Tool: Create Files in a Folder and Share Them Directly from Dust
Dust now supports creating Google Docs, Sheets, and Slides directly in specific Drive folders and automatically setting sharing permissions, helping agents complete shared document workflows from creation to collaboration without extra manual steps.
What is it?
Dust agents can now create Google Docs, Sheets, and Slides directly in specific folders, and automatically manage file sharing permissions. Previously, agents could only create private Google Drive files in your root directory—now they can share files on your behalf.
Why is it useful?
This addresses a common workflow gap: agents could analyze data, draft content, compile reports and create the Google file, but you still had to manually place it in the right folder and share it with your team. Now, agents can complete the entire workflow autonomously, saving you several manual steps every time you need to create a shared document.
How does it work?
When an agent creates a Google file, you can specify both the destination folder and who should have access. The agent handles file creation, placement, and permission settings in a single action.
Concrete Use Cases
Here's how you could use it:
- Weekly Team Reports: Ask an agent to compile your team's weekly metrics into a Google Sheet, place it in your "Weekly Reports" folder, and share it with your manager and teammates automatically.
- Client Presentation Decks: Have an agent draft a Google Slides presentation with project updates, save it to your "Client Materials" folder, and grant view access to specific client stakeholders.
- Meeting Notes Distribution: Create an agent that generates meeting summaries in Google Docs, stores them in your team's shared folder, and gives edit access to all attendees.
- Collaborative Project Documents: Ask an agent to create a project planning doc in Google Docs within your team's project folder and automatically share edit rights with all project members.
Benefits for you
- Time savings: Eliminate 2-3 manual steps every time you create a shared document
- Fewer errors: No more forgetting to share files or placing them in the wrong folder
- Complete workflows: Agents can now fully automate document creation from start to finish
- Better collaboration: Files are immediately accessible to the right people without follow-up
How to access it?
If you already have Google Drive connected to Dust, this capability is available immediately. When configuring an agent or using the Google Drive tool, simply specify the destination folder path and the sharing permissions you need. Your agent will handle the rest!
Original source Report a problem
This is the end. You've seen all the release notes in this feed!