components/dust: update wording + add skipToolsvalidation

[spolu]

WHY

This PR attempts to add skipToolsValidation to the create conversation endpoint to allow pipedream workflows to execute Dust agents without having to handle tools validation.

It also proposes a update the wording of the integrations.

It's unclear to me how versioning works in Pipedream and what would happen to existing integrations post this change. Happy to tweak the PR accordingly.

Summary by CodeRabbit

• New Features

  • Added an option to skip tools validation when running an agent.

• Refactor

  • Updated terminology from "assistant" to "agent" throughout the interface for improved clarity.
  • Renamed related properties and actions to reflect the new terminology.

• Chores

  • Incremented the package version to 0.1.1.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
pipedream-docs	⬜️ Ignored (Inspect)			May 14, 2025 2:56pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			May 14, 2025 2:56pm

[coderabbitai]

Walkthrough

The changes rename all references from "assistant" to "agent" across the Dust component and its actions. This includes property names, method names, descriptions, and URLs. A new boolean property, skipToolsValidation, is introduced to the agent action. Version numbers are incremented to reflect these updates.

Changes

File(s)	Change Summary
components/dust/actions/run-agent/run-agent.mjs	Renamed action and all references from assistant to agent; added skipToolsValidation property; updated version and descriptions; changed message sending method and URL path.
components/dust/dust.app.mjs	Refactored all terminology from assistant to agent, including property and method names; updated descriptions; no change to API logic or payloads.
components/dust/package.json	Incremented package version from 0.1.0 to 0.1.1.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RunAgentAction
    participant DustApp

    User->>RunAgentAction: Trigger "Run an Agent" action
    RunAgentAction->>DustApp: sendMessageToAgent({ agentId, message, skipToolsValidation })
    DustApp->>DustApp: Process request, send message to agent
    DustApp-->>RunAgentAction: Return response
    RunAgentAction-->>User: Confirm message sent to agent

Loading

Possibly related PRs

• PipedreamHQ/pipedream#14043: Refactored the original "dust-talk-assistant" action to "dust-run-agent," directly modifying the same action file and related identifiers.

Suggested labels

ai-assisted

Poem

A rabbit hopped in code today,
Swapping "assistant" out the way—
"Agent" now runs, bold and bright,
With skipToolsValidation in sight.
Version numbers gently climb,
While Dust hops forward, in perfect time.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/dust/actions/run-agent/run-agent.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

components/dust/dust.app.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7135567 and 84a89c7.

📒 Files selected for processing (3)

• components/dust/actions/run-agent/run-agent.mjs (3 hunks)
• components/dust/dust.app.mjs (4 hunks)
• components/dust/package.json (1 hunks)

🔇 Additional comments (13)

components/dust/package.json (1)

3-3: Version bump aligned with feature changes.

The version increment from 0.1.0 to 0.1.1 properly reflects the renaming and feature changes across the Dust component.

components/dust/dust.app.mjs (7)

7-12: Property definition updated to use "agent" terminology.

The prop definition has been correctly renamed from assistantId to agentId with appropriate label and description updates.

---

13-19: Method and variable names updated for consistency.

The method call was changed from listAssistants to listAgents and variable renamed from assistantConfigurations to agentConfigurations to maintain consistency with the new terminology.

---

28-31: Variable name formatting improved.

Consistent variable naming in the mapping function.

---

44-50: Improved parameter destructuring in _makeRequest.

The method now properly uses object destructuring for cleaner code.

---

51-56: Method renamed but API endpoint unchanged.

While the method was renamed from listAssistants to listAgents, the API endpoint path still uses "/assistant/agent_configurations". This is likely intentional to maintain compatibility with the backend API.

---

63-69: Method renamed but API endpoint unchanged.

The method was renamed from sendMessageToAssistant to sendMessageToAgent, but the API endpoint path still uses "/assistant/conversations".

---

70-76: Improved parameter destructuring in upsertDocument.

The method now properly uses object destructuring for cleaner code.

components/dust/actions/run-agent/run-agent.mjs (5)

5-9: Action renamed and versioned for "agent" terminology.

The action was properly renamed from "dust-talk-assistant" to "dust-run-agent" with an appropriate version bump from 0.0.1 to 0.0.2 to reflect the changes.

---

13-15: Property definition updated to use "agent" terminology.

The prop definition reference has been correctly updated from assistantId to agentId.

---

19-20: Message description updated to reflect agent terminology.

Description correctly updated to reference "agent" instead of "assistant".

---

37-43: New property added for skipping tools validation.

The new skipToolsValidation boolean property allows bypassing tools validation during agent execution, which was one of the main objectives of this PR.

---

46-69: Method call updated and new parameter added.

The method call was updated from sendMessageToAssistant to sendMessageToAgent and the skipToolsValidation parameter was properly added to the request payload.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vercel]

@spolu is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible