Dust vs Taskade: Context or Configured Steps?
Compare Dust and Taskade on agent-selected skills, defined automations, approvals and pricing allowances for recurring team work.
Founder, Task Machine
Should Dust and Taskade run your process from context or from steps your team has defined? Dust lets an agent select reusable skills. Taskade automations define triggers and actions with branches, loops and filters, making process structure the first distinction to examine.
Both products assign tasks to people and agents, retain context and offer approvals. A team choosing between them should start with a real repeated job, such as reviewing an incoming request before updating a project. The question is which parts of that job should be selected during execution and which should be configured beforehand.
Company knowledge in Dust
Dust brings company knowledge, shared Pods and connected tools into agent work. Its task documentation describes Pod tasks with assignees and Open, In progress and Done states. An agent can pick up a task and mark it done, with a linked conversation where a person can redirect the work.
That gives a team a concrete way to follow delegated work without abandoning its shared context. Dust's initiative-management example also puts goals and success criteria in a Pod and schedules progress summaries. Its docs do not establish a named goal owner tracking a measurable target and acting on changes to it.
Dust's Agent Memory guide describes user-specific memories across conversations. Each agent has separate memories for each user, which you can inspect and delete. For a team evaluating continuity, distinguish those personal memories from the shared knowledge and conversations in a Pod.
Projects and apps in Taskade
Taskade combines projects, AI Teams, automations and an app builder. Its assignment guide lets you assign a task to a teammate, agent or AI Team. Assigning an agent starts its work immediately, so assignment is also an execution boundary.
Its AI Teams documentation describes Orchestrate mode, where a lead plans work, assigns steps to agents and checks results through a review step. AI Teams require Pro or higher. A team can therefore evaluate a coordinated group of agents alongside individual assignment.
Taskade also fits work that needs a prompt-built CRM, dashboard or client portal backed by workspace data. Its agent knowledge comes from projects, files, links and notes. Connected projects update when their content changes, giving app-connected work a different context model from Dust's user-specific Agent Memory.
Define the process before scheduling it
Dust's skills guide packages instructions, knowledge and tools for reuse. Skills can reference other skills, but the agent decides when to activate them. Its docs do not describe a native fixed-step workflow with defined branches that follows the same execution path every time.
Taskade's automation guide describes triggers, action steps, branches, loops and filters. Agents can run inside those steps, and the Runs tab records inputs, outputs and errors. If your request-triage process always needs a classification followed by a branch, those configured elements are relevant evidence.
The limit is not whether either product can start automatically. Dust publishes scheduled and webhook triggers, while Taskade publishes schedule triggers and HTTP Webhook triggers on Pro or higher. Check what happens after the start and what the operator can inspect when a run needs correction.
Taskade's schedule documentation says hourly, daily, weekly and monthly automations can start up to 30 minutes after the set time. It advises against chaining automations by scheduling them a minute apart. Put dependent steps in the process you test, and do not infer an exact start-time guarantee from the availability of a schedule.
Approving an action and checking a result
Dust documents MCP tool approval levels in its changelog, including always asking and never asking. Agents pause for decisions in conversations. Its GitHub tools also support pull-request reviewers that apply internal coding rules, so code review is a published use case with defined criteria.
Taskade's approval-step guide describes approval notifications in Taskade and by email. Selected teammates can use a Review link or the Runs tab to decide. Taskade's agent-tool guide also lets you set Automatic or Manual approval on individual agent tools.
For output checking, Taskade's Bash Sandbox guide documents lint, test and validation scripts, including checking a CSV for missing email addresses and duplicate member IDs. Dust's published correctness example concerns pull-request review. Compare the check that fits your artifact, because a code-review example and a data-validation script do different jobs.
A human approval also serves a different purpose from a script that checks a file. During evaluation, identify whether your approver is authorizing a write, accepting an output, or both. Inspect the run evidence for each decision before enabling the recurring job.
Understand the allowance you will consume
Dust's pricing page lists Pro at €30 per seat monthly or €24 per month billed yearly, with 8,000 monthly credits, excluding VAT. Credits cover model processing and tool actions. Its monthly seat credits do not roll over.
Taskade's pricing page lists Starter at $6 a month billed $72 yearly, with 10,000 monthly AI credits and 350 automation runs. Pro is $10 a month billed $120 yearly, with 50,000 credits and 1,000 runs. These are annual-plan equivalents, and credits and runs are separate allowances.
Neither set of figures establishes how many of your completed jobs the allowance will cover. Use a representative request with its real checks and inspect the usage records. If provider keys matter, Taskade accepts them on Pro and higher, but TSK-Auto automation steps still use Taskade credits and your provider bills other covered model usage separately.
Dust and Taskade, point by point
Below are both products' answers to the same questions, including the source and check date for each answer. Read the justification alongside the label to distinguish a published example from a broader execution contract.
Both columns answer the same questions from each company's public pages. Yes means the company publishes the capability the question asks about, Partly means something narrower, No means it says it does not offer it, and Not published means its public pages do not describe it. Every answer links to its source and shows when we last checked it. The oldest check on this page was November 13, 2026.
| What you compare | Dust | Taskade |
|---|---|---|
| Goals |
Dust
Partly
A Pod can hold an initiative's goal and success criteria, with scheduled progress summaries. Its docs do not describe a named goal owner tracking a measurable target and acting on its changes. |
Taskade
Partly
Plan & Execute agents take objectives, set sub-goals and iterate until the job is done. Its docs do not establish an accountable goal owner tracking a measurable target over time. |
| Leads |
Dust
Partly
Agents can coordinate project updates and delegate work to specialist agents. Its docs do not describe an assigned project, goal or team lead role responsible for reviewing and coordinating the work. |
Taskade
Yes
In an AI Team's Orchestrate mode, a lead plans the work, assigns each step to an agent and checks the result with a review step. AI Teams require Pro or higher. |
| Tasks |
Dust
Yes
Pod tasks have assignees and Open, In progress and Done states. People can complete them, agents can pick them up and mark them done, and agent execution opens a linked conversation where you can intervene. |
Taskade
Yes
Tasks can be assigned to teammates, AI agents or AI Teams. Each task can hold threaded comments, and assigning an agent starts its work immediately. |
| Recurring work |
Dust
Yes
Schedule triggers run agents at times you describe, and webhook triggers respond to outside events. Each run creates a conversation, optionally in a shared Pod. |
Taskade
Yes
Schedule triggers run automations hourly, daily, weekly, monthly or on a custom schedule. External systems can start automations by posting to an HTTP Webhook trigger on Pro or higher. |
| Workflows |
Dust
Partly
Skills package reusable instructions and can reference other skills, while agents delegate through Run agent. The agent decides which skills to activate. Its docs do not describe a native fixed-step workflow with defined branches that repeats the same execution path. |
Taskade
Yes
Automations combine triggers and action steps with branches, loops and filters. Agents can run as steps, and the Runs tab records each run's inputs, outputs and errors. |
| Autonomy |
Dust
Yes
Admins configure MCP tool approval levels, including always asking and never asking. Agents pause for approval in conversations, and actions requiring confirmation from an emailed request send private Accept and Reject links to the sender. |
Taskade
Yes
You set Automatic or Manual approval for each agent tool. Automation approval steps notify selected teammates in Taskade and by email, and collect their decision through a Review link or the Runs tab. |
| Learned autonomy |
Dust
Partly
Medium-stake tools retain per-agent approval history, and self-improving skills propose instruction and tool changes from conversation feedback. Its docs do not describe proposals to change action permissions based on approval history. |
Taskade
Not published
Its public docs describe manually selected approval gates and persistent knowledge, but do not describe proposals to change an agent's permissions from your approval history. |
| Memory |
Dust
Yes
Agent Memory keeps user-specific information across conversations. You can inspect and delete saved memories in the agent's Memory tab. Each agent has separate memories for each user. |
Taskade
Yes
Agents keep persistent knowledge from connected projects, files, links and notes across chats. You can review and edit sources in the Knowledge tab, and connected projects update when their content changes. |
| Planning |
Dust
Yes
For complex questions, @deep-dive creates a research plan and consults a planning agent to review and improve it before delegating to specialist agents. You can follow the research reasoning as it runs. |
Taskade
Yes
Taskade EVE writes a numbered plan before editing files and keeps it in the conversation with step statuses. Start with /plan to agree on the plan before generation. |
| Intake |
Dust
Yes
Webhook sources receive events such as new tickets and route them to an agent's configured trigger. Workspace members can also forward email to [email protected]. Email from non-members is not processed. |
Taskade
Yes
AI Forms start automations from submissions and pass requests through agents and branches. Assign Task can automatically hand an emailed request to a team member based on its subject. |
| Connectors |
Dust
Yes
Dust offers built-in MCP tools, remote MCP servers and custom servers at a public URL. Built-in and custom webhook sources can start agents from events in connected services. |
Taskade
Yes
Taskade lists 100+ integrations and MCP connections, plus HTTP requests to custom endpoints and incoming webhooks. Automations can call remote MCP tools for an agent. |
| Models |
Dust
Partly
You choose a specific model or Basic, Standard or Premium. Auto uses a maintained ordered list with availability fallback. Dust explicitly says it does not select a different model based on each task. |
Taskade
Yes
TSK-Auto picks a model for each task and is available on every plan. You can instead choose a model tier for an agent. |
| Cloud or your own computer |
Dust
Partly
Computer gives agents a temporary workspace for code and files. A preview supports tools executing in custom client applications. Its docs do not establish an option to run the agent runtime itself on your computer or infrastructure. |
Taskade
Partly
Taskade hosts apps and runs agent commands in an isolated sandbox, not on your host machine. Its docs describe no user-operated local agent runtime or self-hosted workspace option. |
| Your own subscription |
Dust
Yes
Dust's Gemini 4 Argon announcement explicitly includes workspaces that bring their own API key. That announcement does not specify eligible plans or the full set of supported providers. |
Taskade
Partly
Pro and higher accept your OpenAI, Anthropic and Google provider keys. Coverage depends on the selected model, and TSK-Auto automation steps still use Taskade credits. Your provider bills model usage separately. |
| Pricing |
Dust
Yes
Business offers Free seats with 500 lifetime credits, Pro at €30 per seat monthly or €24 per month billed yearly with 8,000 monthly credits, and Max at €150 monthly or €120 per month billed yearly with 40,000 monthly credits. Prices exclude VAT. Enterprise is custom. |
Taskade
Yes
Starter is $6 a month billed $72 yearly, with 10,000 monthly AI credits and 350 automation runs. Pro is $10 a month billed $120 yearly, with 50,000 credits and 1,000 runs. Additional credit packs are available. |
| Correctness |
Dust
Yes
Dust documents PR reviewer agents that review pull requests against internal coding rules. This is a defined-criteria check for code reviews, rather than a published acceptance check on every Pod task. |
Taskade
Yes
Agents can run lint, test and validation scripts in the Bash Sandbox. Taskade documents checking a CSV for missing email addresses and duplicate member IDs before importing it. |
For software work
| What you compare | Dust | Taskade |
|---|---|---|
| Code review rules |
Dust
Yes
GitHub tools let you build PR reviewer agents that review pull requests based on your internal coding rules. |
Taskade
Yes
The Pull Request Reviewer agent template accepts your coding standards, linting rules and architecture guidelines, with configurable feedback severity and file types. Its published review checks style violations and bugs. |
| Adversarial review |
Dust
Not published
Its public docs describe no independent second review of risky code changes. GitHub reviewer agents and sub-agent delegation do not establish that review process. |
Taskade
Partly
An AI Team can give an agent the verifier role and reserve review steps for it. Its docs do not establish an independent second code review triggered by a risky change. |
| Risk rating |
Dust
Not published
Its public docs describe no pre-merge risk rating for a code change. Published GitHub review tools and engineering use cases do not establish a risk score. |
Taskade
Partly
The Pull Request Triage agent template flags changes involving authentication, payments, migrations and security boundaries. Its page describes risk flags rather than an overall rating of a change before merge. |
| Pull requests |
Dust
Partly
GitHub tools can search, update, comment on and create pull requests, and agents can review them. Its docs do not establish agents revising a code branch in response to pull-request review feedback. |
Taskade
Partly
Exporting an app to an existing GitHub repository opens a pull request on a new branch. Each export opens a new request. Its docs do not establish an agent revising the same pull request from review feedback. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Dust and Taskade are named only to identify them, and there is no relationship between the companies. Has something changed? Tell us.
Who each one suits
Pick Dust if your team wants shared company context, Pod tasks and conversations where people can steer an agent's chosen method. Its limit for a rigid process is that skill activation stays with the agent, and its public docs do not establish the native fixed-step workflow described above.
Pick Taskade if you want app-connected projects, agent teams and automations with configured branches. Its scheduling guide permits the start-time drift described above, so validate timing-sensitive work before relying on a scheduled trigger.
Where Task Machine fits
Task Machine combines owned Tasks with reviewed plans and acceptance requirements. Its Workflow builder defines ordered steps, branches, human questions and approvals, with verifier checks that can return weak work with feedback. That addresses the process-definition question while keeping the checks attached to the work.
Task Machine is the wrong pick if your main requirement is Taskade's app builder or Dust's shared Pod conversations and those already fit your team. Consult the Dust comparison and Taskade comparison to separate those requirements from reviewed execution. Take one request-triage job and mark its required branches and acceptance checks against the Workflow documentation.