Taskriz and AG-UI

Both connect AI agents with people. AG-UI is an open protocol that streams an agent’s work into the app a person is already using. Taskriz reaches the person who isn’t in your app, wherever they are, and brings their answer back.

Different jobs

Use them together

They fit together. An agent that streams to your app through AG-UI can call the Taskriz MCP server or the Taskriz HTTPS API when it needs someone outside your app: a customer’s approval, a contractor’s photo, a supplier’s price. It can pause its run with an AG-UI interrupt while it waits, show the person in your app that it’s waiting, and carry on when the answer comes back, or have Taskriz call your webhook.

Your team can also ask from where it already works: Slack, Google Chat and Microsoft 365 Copilot. And visitors to your website can send you a complete request with Website Requests.

What they share

Side by side

AG-UITaskriz
What it isAn open, event-based protocol (MIT licence) for connecting an AI agent to a user-facing app, started by CopilotKit with LangChain and CrewAIA hosted service for reaching people, with an app, plugins, an MCP server and an HTTPS API
Which way it worksThe agent’s work streams into the app the person is using: messages, tool calls, state and progress, liveAn agent, your software or you ask a person for something, and get their answer when it comes
Who answersThe person using your app, while the agent runsAnyone a request is sent to, from the link they’re sent: no app and no account, straight away or days later
Reaching peopleNot part of it: the person is already in your appBy email and text message (Australia and the United States), a link, Slack or Google Chat, or a request box on your own website
Telling them a request is waitingNot part of itIn the Taskriz app, by email, browser notifications and text message, with reminders if no one answers
Where people answerIn your app’s own interface, which you build and run (for example with CopilotKit, or in Slack and Teams through CopilotKit’s clients)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 askWhatever your app shows: text, tool results, typed components, and an interrupt to pause for the person to approve, edit or retryA 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 AgentIn the same live connection; after an interrupt, the app resumes the agent with a new runAs structured data, matched to the request: through the plugins, the MCP server, a signed webhook, a WebSocket or the events list
Connecting your AgentAdapters for agent frameworks (LangGraph, CrewAI, Microsoft Agent Framework, Google ADK, Mastra, Pydantic AI, AWS Strands), Amazon Bedrock AgentCore, and SDKs in many languagesPlugins 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. No AI of your own? Ask Someone writes the request from your plain words
People starting thingsThe person types to the agent in your appYour Agent’s request catalog: actions people start from the Taskriz app, and visitors to your website through Website Requests
CostFree and open source; you build and run your app and your agentA Free plan, then paid plans by the requests your Agents send; the people who answer never pay

Security

AG-UI is a protocol, so its protections are your app’s: its sign-in, its connection and how you run your agent. In Taskriz, a request’s protections come built in.

AG-UITaskriz
Who can reach a personNo one is reached; your app’s own sign-in decides who sees the agentOnly 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
EncryptionYour app’s connection, over HTTP or WebSocketsEach 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 requestYour app, your agent and the AI model it callsOnly the person’s devices: it passes through Taskriz while it’s delivered, and is never stored or logged readable
Running the interfaceYour app’s own code, in its own pagesIn a WebAssembly sandbox with no network or file access of its own
Confirming what mattersYour app can pause the agent with an interrupt, for the person to approve or edit before it goes onThe person sees the whole request and answers it themselves

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

Start FreeSee the Docs

When AG-UI fits

Questions

About this comparison

AG-UI was checked in November 2026, from the AG-UI documentation, its events, AG-UI on GitHub and Amazon’s AgentCore announcement. AG-UI is an open-source project started by CopilotKit; Taskriz is not affiliated with it. What Taskriz is building next is on the Roadmap.