dust-tt · axel-ext-dust · Aug 7, 2026
diff --git a/docs/developer-platform/dust-cli/dust-cli.mdx b/docs/developer-platform/dust-cli/dust-cli.mdx
@@ -155,13 +155,17 @@ dust chat                          # uses env vars automatically
 ### Method 2: Command-line flags
 
 ```bash
-dust chat --wId ws_abc123 --api-key sk_your_api_key_here
+dust chat --workspaceId ws_abc123 --key sk_your_api_key_here
 ```
 
-| Parameter    | Env variable        | CLI flag    | Description                      |
-| ------------ | ------------------- | ----------- | -------------------------------- |
-| API key      | `DUST_API_KEY`      | `--api-key` | Your API key for authentication. |
-| Workspace ID | `DUST_WORKSPACE_ID` | `--wId`     | Your workspace ID.               |
+| Parameter    | Env variable        | CLI flag        | Description                      |
+| ------------ | ------------------- | --------------- | -------------------------------- |
+| API key      | `DUST_API_KEY`      | `--key`         | Your API key for authentication. |
+| Workspace ID | `DUST_WORKSPACE_ID` | `--workspaceId` | Your workspace ID.               |
+
+<Note>
+API key authentication runs with workspace-level identity rather than your personal user session. Commands that require a logged-in user are only available after `dust login`.
+</Note>
 
 <Note>
 Command-line flags take precedence over environment variables.

diff --git a/docs/user-documentation/admins/connections-management/github.mdx b/docs/user-documentation/admins/connections-management/github.mdx
@@ -65,6 +65,10 @@ To modify permissions and which repositories or types of data are synchronized:
 3. Click Add/Remove Data, Manage permissions, re-auth, and follow the steps above.
 4. Adjust your selections for repositories, then save your changes.
 
+<Warning>
+Do not uninstall the Dust GitHub App from GitHub directly. Dust is not notified when the app is removed: the connection will still appear configured but will stop syncing. Manage or remove the integration from the Dust Admin panel instead. If the app was already uninstalled, reinstall it from the connection settings and contact `support@dust.tt` if syncing does not resume.
+</Warning>
+
 ## Data Synchronization
 
 * **Issues**: Titles, descriptions, comments, and tags.

diff --git a/...s/tools-management/salesforce/salesforce-notes-on-api-limit-and-permissions.mdx b/...s/tools-management/salesforce/salesforce-notes-on-api-limit-and-permissions.mdx
@@ -76,6 +76,8 @@ Example configurations:
 * Salesforce data is available through the tool "[Query Tables](/docs/user-documentation/agents/knowledge/table-queries)" in the Agent Builder.
 * Note that not all fields are automatically queryable - they may need to be made accessible in your Salesforce configuration first
 
+The Salesforce tool executes read-only SOQL queries against the standard REST query endpoint. Objects exposed only through the Tooling API (such as `ApexClass`, `ApexTrigger`, or `FlowDefinition`) are not supported and return a `sObject type not supported` error.
+
 ### Agent Understanding of the Data Structure
 
 * Even though the agent is quite smart to discover the data structure, we recommend taking the time to properly explain what data is actually relevant for your use case in your agent instructions, especially if it involves Custom Objects. A relevant Account Summary can be very different from one business to another.

diff --git a/docs/user-documentation/agents/integrations/dust-in-slack/slack-workflows.mdx b/docs/user-documentation/agents/integrations/dust-in-slack/slack-workflows.mdx
@@ -31,6 +31,8 @@ For example:
 
    The **whitelisting is at the Slack workflow level,** so you can change the name of the agent called inside anytime once validated.
 
+   However, whitelisting matches the exact Slack workflow name. If you rename the workflow in Slack, the Dust agent will stop responding until the new name is whitelisted. Email `support@dust.tt` with the updated name before renaming.
+
    Bear in mind that **Slack workflow can be restricted**, Dust can only interact with Slack workflows it has permission to access. Either select "Everyone internal in..." or add Dust to the specific channels where the workflow will run. Note: Dust cannot access workflows set to "Managers only."
 </Info>
 3. **Invoke @dust and the Dust Agent of your choice in the Slack workflow message.** Specify which Dust agent to use in a workflow by including the agent's name following this message format: `@dust +agentName`. This will ensure that the correct Dust agent responds to the workflow-triggered messages.
diff --git a/docs/user-documentation/agents/tools/gong.mdx b/docs/user-documentation/agents/tools/gong.mdx
@@ -84,3 +84,5 @@ After adding Gong to a Space and including it in an agent:
 ## Notes and Limitations
 
 - Transcript availability: Newly completed calls may not have transcripts immediately. If you see "No transcript found," wait until Gong finishes processing and try again.
+- No search: the Gong tools cannot search calls by keyword, account, or participant. They only list calls by date range and retrieve calls by ID. For search workflows ("find all calls mentioning X"), use the [Gong connection](/docs/user-documentation/admins/connections-management/gong) to sync transcripts into Dust and query them from an agent.
+- Transcripts are organized by speaker and do not include timestamps.