this+that vs Skydive
Coworkers you assign work to, or work that gets picked up as it lands.
Skydive gives you agents with names and roles, each with its own cloud computer and its own email address, and you email them, forward them a thread, or put them on a schedule. this+that starts from the other end: it reads Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business as one stream of incoming work, pulls the real tasks out, and acts on them as they arrive. The difference is what sets each of them off.
Named coworkers on a schedule, or your messages as the trigger
Skydive is a platform for building AI coworkers. Each agent gets a name, a role, and its own computer with a browser, a file system and a terminal, so it can research, handle files and finish multi-step work on its own. You reach the same agent from web, Slack, email, iMessage, desktop or the command line, and it keeps one memory across all of them. Give it an address on your company domain and you can email it or cc it like any other colleague. It is a well-made product with a clear idea behind it.
The design decision that separates us is what starts the work. In Skydive, a person does: you message an agent, forward it a thread, or set a routine. Their routines run on a clock, and their own documentation is plain about it, describing a routine as work an agent runs on its own schedule, with examples like every weekday at 9am or the first of each month. Even the inbox example is a scheduled summary. this+that has no schedule at its center. A message lands, and that is the trigger. The work someone else sent you becomes a task in your DoBox, and a workflow can run on it the moment it arrives rather than the next time a routine happens to wake up.
The second difference is where knowledge lives. Skydive's memory belongs to the agent, and its templates are per role, so what your support agent learns is your support agent's. In this+that the brain is shared: every teammate and every workflow reads and writes the same layer, and it fills itself from the conversations your team is already having. If you want capacity you can hand jobs to, Skydive is a good answer. If your problem is that things arrive and get missed, that is a different product, and it is this one.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Skydive | this+that |
|---|---|---|
| What starts the work | A person, or a clock. You message an agent, forward it a thread, or set a routine that runs on a schedule. | An arriving message. Workflows fire on what lands in your channels, so nothing waits for the next scheduled run. |
| Automation model | Routines, described in plain English and run on a schedule: every weekday at 9am, the first of each month, or once at a future moment. | Workflows triggered by the message itself, with conditional logic, loops and sub-agents. A schedule is available and is not the point. |
| Shape of the product | A roster of agents. Each has a name, a role, its own computer with browser, files and terminal, and its own chat. | A shared work surface. One universal inbox across every channel, with tasks in DoBox that the whole team can see and assign. |
| Each agent gets its own address on your domain. You email it, forward it a thread, or cc it, and finished work comes back. | We read your mailbox. Nobody has to forward anything for the work inside a thread to be noticed. | |
| Channels | Web, Slack, email, iMessage, desktop, CLI and API. Gmail and Slack can also be connected so an agent reads them. | Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business, read as one stream. |
| Knowledge | Memory belongs to each agent and improves from your corrections to that agent. | The brain is one shared layer with version history. Every teammate and every workflow reads and writes it. |
| Contacts | Not a contact product. CRMs are reachable as tools an agent can act on. | An address book that assembles itself from the channels you connected, with the history attached. |
| Third-party tools | Over 100 integrations across communication, docs, dev tools, CRM and finance, plus 170+ models to choose from. | Open MCP. Built-in servers for GitHub, Notion, HubSpot, Jira, Dropbox and Asana, plus any MCP-compatible tool. |
| Pricing | Starter is $20/month and covers up to five users. Team is $200/month and states no user count of its own. Agents are unlimited on both, and model and compute usage is billed on top at a stated 0% markup. | Free for 30 days. |
| Maturity | Launched publicly on August 20, 2026 after a closed beta with more than 20 companies. Built by Anything, a 15-person team. | Out of beta, with SOC 2 Type I as of July 31, 2026 and Type II underway. |
- Every agent gets its own computer, with a browser, a file system and a terminal, so it can go and do things on the open web rather than only inside connected tools.
- The roster model is easy to reason about. You can hand work to a named agent with one job and hold it to account, which is a clean way to add capacity.
- Reachable from web, Slack, email, iMessage, desktop, CLI and API, with one identity and one memory across all of them.
- Giving an agent an address on your own domain makes it addressable by anyone who can send email, including people outside your company.
- Over 100 integrations and a choice of more than 170 models.
- Pricing is unusually legible for this category: unlimited agents on every tier, and no markup on model cost.
- The trigger is the message. Work is noticed as it arrives, so nothing sits until a scheduled routine next runs.
- Nobody has to forward anything. We read the mailbox you already use, which means the request buried in a long thread still gets caught.
- The brain is shared across the team and writes itself from the conversations you are already having, rather than living inside one agent.
- DoBox is a team surface. Tasks are assignable and visible to everyone, instead of sitting in a private chat with an agent.
- We read Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business, so the channels a small team actually runs on are covered.
- Contacts build themselves from those same channels, with your correspondence attached to each person.
See what's waiting in your inbox
Connect your inbox and this+that starts reading it. The tasks, follow-ups, and open commitments buried in your messages become tracked work, and what your team knows starts collecting in one place.
Free for 30 days · No credit card required