Droid vs Tasklet
Tasklet runs the workflow. A droid also runs the call.
Tasklet is a seriously good cloud agent. Describe a job in plain English and it connects to your tools, writes code in a sandbox, and runs 24/7 on triggers. A droid does that too, and adds the things that don't fit in a chat box: a phone number, live voice and video, and a home in every channel your team uses.
- Voice, phone & video calls
- Lives in your channels
- Onboard on a call
- Customer-facing comms
The honest short version.
Tasklet (from the team behind Shortwave, backed by YC) is a cloud agent OS, meaning a single chat interface over a 24/7 runtime, thousands of integrations, MCP, a code sandbox, and triggers on schedules, emails and webhooks. It's genuinely strong, and on autonomous app-work a droid and Tasklet are close cousins. Where they part company is on where the work happens. A droid lives in Slack, Teams, email, SMS and on a real phone, so it joins calls, talks to customers, and you onboard it by briefing it like a hire. Tasklet is a chat-and-triggers product, whereas a droid is resident in your channels.
Droid and Tasklet, line by line.
The same job, two tools. Here's how they differ where it actually counts.
| Capability | Droid | Tasklet |
|---|---|---|
| What it is | An AI worker you hire for a role, across chat, voice and the phone. | A cloud agent OS you drive from a single chat interface. |
| Where it lives | Slack, Teams, email, SMS, voice and a real phone number. | Its own web chat, plus Slack / email / webhook triggers. |
| Voice, phone & video | Phone number, live voice calls, and joins Zoom / Meet / Teams with screen-share. | No telephony or meetings. |
| Takes action across apps | ~3,000 governed apps with read / write / destructive actions and per-tool policies. | Thousands of integrations + any HTTP API + MCP + a cloud browser. Comparable breadth. |
| Runs unattended | Durable scheduled and event-triggered runs. | 24/7 triggers on schedules, emails, Slack messages and webhooks. Comparable. |
| Code & compute | Writes and runs code to finish jobs end-to-end. | Writes and runs code in a per-agent cloud sandbox. Comparable. |
| Generates UIs | Builds artefacts and dashboards as a job needs them. | Generates dashboards, forms and trackers on the fly, which is a real Tasklet strength. |
| Team & governance | Shared workspace, memory, approvals and a credential vault. | Shared workspaces, locked-down keys, granular access controls. Comparable. |
| Onboarding | Brief it on a call like a hire. | Describe tasks in plain English in the chat. |
| Who it talks to | Teammates and customers, across chat, phone, SMS and email. | Primarily the operator, in a chat UI. |
Some of these rows go the other way, and they stay in. A comparison page where the competitor never wins is an advert, and readers can tell.
What a droid adds.
Tasklet covers autonomous app-work beautifully. These are the surfaces a chat-and-triggers agent doesn't reach.
Picks up the phone
Own number, live voice and video, and it joins meetings with screen-share, rather than working from a chat box and webhooks.
Lives in your channels
Slack, Teams, email, SMS and phone, so your whole team @mentions the same worker where they already are.
Talks to people as well as tools
Runs real conversations with teammates and customers, as well as making API calls behind a chat interface.
Onboards on a call
Brief it out loud like a hire instead of writing the spec into a chat.
Real-world comms
SMS and email follow-ups, voicemail and call summaries, which are the human glue around the automation.
One worker, every surface
The same droid in chat, on the phone, and in your inbox, with shared memory across all of it.
Where Tasklet shines.
Tasklet is excellent, and honest comparison means saying so.
- Plain-English setup, so you describe the outcome and it figures out the tools and steps.
- A true 24/7 cloud runtime with triggers on schedules, emails, Slack and webhooks.
- Connects to thousands of apps, any HTTP API, MCP servers, and a cloud browser for the rest.
- Generates dashboards and internal UIs on the fly, wired to your real data.
- Per-agent cloud sandboxes, shared team workspaces, and locked-down credentials.
The questions that come up most.
On autonomous app-work, yes. Both are cloud agents that connect to your tools, write code, and run on triggers, and Tasklet does it very well. What differs is surface: a droid is resident in your channels (Slack, Teams, email, SMS, voice, phone), joins real calls, and is onboarded by talking to it, whereas Tasklet is a chat-interface-plus-triggers product. Different shape, overlapping core.
If you want a powerful agent you drive from a chat UI and wire to triggers, Tasklet is a great fit. If you want a worker that lives in your team's channels and on the phone, and that customers can reach, pick a droid.
Yes. Both route across frontier models (Anthropic, OpenAI, Google) per task and build on MCP. What a droid layers on top is the channels, voice and governance wrapped around it.
No. Your conversations, files, and integration data aren't used to train shared models. Droid's providers operate under no-training, zero-retention terms for Droid traffic. See /security for the full posture.
Start free with starter credits, no card. The quickest way to get going is to hop on a call and walk a droid through the job.
Take the agent off the screen.
Starter credits, no card. Brief a droid on a call and watch it work your apps, pick up the phone and follow up, all in the one run.