Taskriz and OpenBot
Both put a person in the loop of an AI agent’s work. OpenBot is a workspace where your own team runs and supervises agents. Taskriz reaches the person the work is waiting on, often someone outside your company, and brings their answer back.
Different jobs
OpenBot
An open-source workspace from CopilotKit, the company behind the AG-UI protocol. Your team brings its own agents, models and tools, hosts it in your own cloud, and works with agents in a conversation: they browse, search, draft and act, and ask a person before anything sensitive. Desktop apps for Mac and Windows now; mobile, Slack and Teams in early access.
Taskriz
A service for getting things from people. Your software, your Agent or you send a request; Taskriz takes it to the right person, by email, text message, a link, Slack, Google Chat or a request box on your website, and brings their answer back as structured data. The people who answer need no app and no account.
Where they overlap
Both have a person approve or decide before work goes on. The difference is who that person is.
- OpenBot’s approvals are for your own people. Someone in your workspace approves or denies what an agent wants to do, in OpenBot, or in Slack, Teams or on mobile in early access.
- Taskriz reaches anyone. Your customers, contractors and suppliers outside your company, as well as colleagues: they answer from a link with no app and no account, and Taskriz follows up with reminders and text messages if they don’t.
- Where your team already works. Taskriz works in Slack, Google Chat and Microsoft 365 Copilot, and on your own website with Website Requests, so the people asked can be in your team or not.
Use them together
You could call Taskriz from OpenBot. OpenBot connects tools through MCP, and Taskriz has an MCP server, so an agent working in OpenBot could send a request through Taskriz to a customer, contractor or supplier outside your company, and carry on with their answer when it comes back. Your own agents in OpenBot can also call the Taskriz HTTPS API directly.
Answers from people can take minutes or days: the agent checks back for them, or Taskriz calls your webhook when they arrive. We haven’t tested Taskriz inside OpenBot yet; the Docs show how to connect.
What they share
- A human in the loop. Both keep a person in charge of the decisions that matter.
- Bring your own AI. OpenBot runs the agents and models you choose; Taskriz works with any Agent or software, through plugins, MCP or its API, and with none at all through Ask Someone.
- MCP. OpenBot connects tools through MCP; Taskriz offers its own through the Taskriz MCP server.
Side by side
| OpenBot | Taskriz | |
|---|---|---|
| What it is | An open-source (MIT) workspace for AI agents from CopilotKit: “AI coworkers that each get a computer of their own”, with a browser, files and tools | A hosted service for reaching people, with an app, plugins, an MCP server and an HTTPS API |
| Who it’s for | Teams that run and supervise their own AI agents inside the company, with company controls | Businesses, their software and their AI agents, when the work needs something from a person: a customer, contractor, supplier or colleague |
| Who answers | People in your OpenBot workspace: they approve, deny or review what an agent wants to do | Anyone a request is sent to, from the link they’re sent: no app and no account, straight away or days later |
| Reaching people | Your people open OpenBot; agents can email or post to others through the tools you connect, such as Gmail or Slack | By email and text message (Australia and the United States), a link, Slack or Google Chat, or a request box on your own website |
| Where people answer | The OpenBot desktop app for Mac and Windows now; iOS, Android, Slack and Teams in early access; web coming soon | The Taskriz app in the browser on any phone or computer, nothing to install; in Slack and Google Chat; or on your website |
| What a request can ask | Approve, deny or review an action, in the conversation, with results shown as lists and charts | A whole screen built for the answer: choices, dates, a photo or document, a map or a short note, from iOS-style building blocks |
| Answers back to the Agent | The decision lets the agent carry on, in OpenBot | As structured data, matched to the request: through the plugins, the MCP server, a signed webhook, a WebSocket or the events list |
| Connecting your Agent | Your agents through AG-UI (Claude Agent SDK, OpenAI Agents SDK, LangChain, Google ADK, Mastra, AWS Strands, Microsoft Agent Framework, CrewAI), tools through MCP, models through your own keys | Plugins for Claude and ChatGPT, the Taskriz MCP server for any MCP client (Copilot Studio included), and an HTTPS API for any software, Agent or workflow, wherever it runs. No AI of your own? Ask Someone writes the request from your plain words |
| The next step | The agent continues its task once approved | The answer arrives on the same conversation as the request, ready for the next one; reminders follow up if no one answers |
| People starting things | Your people give an agent a task in a conversation | Your Agent’s request catalog: actions people start from the Taskriz app, and visitors to your website through Website Requests |
| Running it | You host it: on a laptop with Docker, or in your own cloud with one Helm chart for Kubernetes (EKS, AKS, GKE); hosted by OpenBot in early access | Hosted by Taskriz on Amazon Web Services; nothing to run |
| Cost | OpenBot is free for personal use on your own laptop; Pay as you go is up to US$29 per user a month, billed monthly, the rate falling as the team grows; Annual: custom, through sales. Both add 5% of monthly model spend above US$5,000 per organisation; your models and infrastructure are paid separately. Bots, agents and guests aren’t counted as users | Free to start: 500 requests a month, no card; then Builder at US$29 a month paid monthly, or US$25 a month paid annually (US$290 a year); Business at US$99 paid monthly, or US$83 paid annually (US$990 a year). No seats, and the people who answer never pay |
Security
OpenBot is built to run inside your own network, with your company’s sign-in, roles and audit trail; how requests and data are protected follows from how you deploy it. In Taskriz, a request’s protections come built in.
| OpenBot | Taskriz | |
|---|---|---|
| Who can reach a person | People signed in to your workspace, with single sign-on, SCIM and roles; per-tool rules say what needs a person’s approval | Only people your Agent sends a request to, or who paired with it. Someone without an account opens a request with one tap on their first device (a one-time code elsewhere), and anyone can decline, or stop an Agent reaching them |
| Encryption | Your own deployment: OpenBot runs in your cloud or data centre; its pages don’t describe requests sealed to people’s devices | Each request is sealed to the person’s own devices and stored that way, and travels over TLS 1.2 or later |
| Who can read a request | Your deployment and its admins (with a full audit trail), the agents and the AI models they call | Only the person’s devices: it passes through Taskriz while it’s delivered, and is never stored or logged readable |
| Company controls | Single sign-on, SCIM, roles, cost limits and an audit trail you can send to your SIEM; CopilotKit states it is SOC 2 Type II compliant | Sign-in with email and password, and a list of your signed-in browsers you can sign out of; two-step sign-in is on the Roadmap |
| Running the interface | In OpenBot’s own apps | In a WebAssembly sandbox with no network or file access of its own |
To be plain about Taskriz too: files sent with a request or reply are encrypted on our servers but not sealed to devices, and two-step sign-in is on the Roadmap. Security has the details.
When Taskriz fits
- The work is waiting on someone outside your company, such as a customer’s approval, a contractor’s photo or a supplier’s price, and they shouldn’t have to install or sign up for anything.
- You want answers back as structured data, in your software or your Agent, wherever it runs.
- Your team asks from Slack, Google Chat or Microsoft 365 Copilot, or you have no AI of your own and want to ask in plain words.
- Visitors to your website should send you a complete request, not a note to chase.
- You’d rather not host anything.
When OpenBot fits
- You want a workspace where your own people run, supervise and approve AI agents, hosted in your own cloud.
- Your engineers already build agents in frameworks AG-UI supports, and you want them in one place with your models and tools.
- You need company controls for agents: single sign-on, roles, cost limits and an audit trail.
Questions
What’s the difference between OpenBot and Taskriz?
OpenBot is a workspace your team uses to run and supervise AI agents, with your own agents, models and tools, hosted in your own cloud. Taskriz is a service for reaching people: your software, your Agent or you send a request, Taskriz takes it to the right person by email, text message, a link, Slack, Google Chat or your website, and brings their answer back as structured data.
Can OpenBot reach customers or contractors outside my company?
OpenBot’s agents can send email or post messages through the tools you connect, and its approvals go to people in your workspace. Its pages don’t describe a way for someone outside your company to receive a request and answer it. That is what Taskriz does: they answer from a link, with no app and no account.
Can an agent in OpenBot use Taskriz?
OpenBot connects tools through MCP, and Taskriz has an MCP server, so an agent in OpenBot should be able to send requests through Taskriz and read the answers. We haven’t tested it inside OpenBot yet; the Taskriz MCP server works with any MCP client that supports sign-in with OAuth.
Does Taskriz use AG-UI?
No. AG-UI, created by CopilotKit, connects an agent to the interface of the app the person is already using, as a live stream. Taskriz reaches a person who isn’t in that app, through the Taskriz MCP server, plugins or its HTTPS API, and returns their answer when it comes, minutes or days later.
About this comparison
OpenBot was checked in November 2026, from open.bot, its pricing and business pages, OpenBot on GitHub and the AG-UI documentation; its prices were checked on 14 November 2026. OpenBot is a product of CopilotKit; Taskriz is not affiliated with it. What Taskriz is building next is on the Roadmap.