Taskriz
Taskriz and A2UI
Both let an AI Agent show a person an interface instead of a wall of text, and get their answer back. They solve different parts of the problem, so the right choice depends on who your Agent needs to reach.
Different jobs
A2UI
An open-source protocol from Google and its community. Your Agent describes an interface in JSON; your own app draws it with its own components. You build and run the app, the connection to your Agent, and everything around them.
Taskriz
A service. Your Agent sends a request; Taskriz takes it to the right person — on their phone or computer, now or hours later — and brings their answer back to your Agent as structured data. There’s no app for you to build.
What they share
- Data, not code from the web. The Agent describes the interface; it doesn’t send a web page or script to run unchecked.
- A fixed set of building blocks. An Agent can use only the components the client offers — A2UI’s catalog, Taskriz’s iOS-style building blocks — which keeps what people see safe and consistent.
- The answer goes back to the Agent. What the person chooses or types returns to the Agent, so the work carries on.
Side by side
| A2UI | Taskriz | |
|---|---|---|
| What it is | An open protocol and renderer libraries, open source under Apache 2.0 | A hosted service, with plugins and an API |
| Who answers | Someone using your app, in a session with your Agent | Anyone paired with your Agent, wherever they are — straight away or hours later |
| Reaching people | Up to you | An email invitation, your Agent’s QR code or its pairing code — every new pairing confirmed by email |
| Telling them a request is waiting | Up to you | In the Taskriz app, by an email notice, and by text message in Australia (the United States soon) |
| Where people answer | In the app you build — renderers for web (Lit, Angular, React), Flutter and SwiftUI; Jetpack Compose is planned, and community renderers cover more | The Taskriz app, in the browser on any phone or computer — nothing to install |
| The interface | JSON components from your app’s catalog — rows, columns, text, images, buttons, text fields, check boxes, sliders, date inputs, choice pickers, cards, tabs — and components you add | A short Smalltalk program built from iOS-style building blocks — screens, lists, text fields, switches, pickers, date pickers, photo and document pickers, buttons — following world-leading human interface guidelines |
| Answers back to the Agent | Over the connection you choose and run — A2A, AG-UI and others | As structured data, matched to the request: through the plugins, a signed webhook, a WebSocket or the events list |
| Connecting your Agent | Agent SDKs for Python, TypeScript, Dart and Swift, and frameworks that speak A2A or AG-UI | Plugins for Claude Code and ChatGPT, the Taskriz MCP server for any MCP client, and an HTTPS API for any Agent or workflow |
| People starting things | Up to your app | Your Agent’s request catalog — actions people start from the Taskriz app |
| Cost | Free to use; you pay to build, host and run your app and its connections | A Free plan, then paid plans by the requests your Agents send; the people who answer never pay |
Security
Both keep an Agent to a fixed set of building blocks, so it can’t slip its own code into what people see. A2UI is a format, so the rest of its security — who can send what to whom, encryption, storage — is designed by whoever builds the app around it, to suit that app. In Taskriz, it comes built in.
| A2UI | Taskriz | |
|---|---|---|
| Who can reach a person | Set by the app and connection you build | Only people who paired with your Agent — by accepting an invitation, scanning a QR code or entering a pairing code — and every new pairing is confirmed by email |
| Encryption | Set by the connection you choose | 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 app, your servers and the connection you choose | Only the person’s devices — it passes through Taskriz while it’s delivered, and is never stored or logged readable |
| Running the interface | Drawn by your app, inside your app | In a WebAssembly sandbox with no network or file access of its own |
| Pictures | Loaded from the addresses the Agent gives | Fetched through Taskriz, so a picture’s server never learns who opened a request, or when |
| Agents and their answers | Set by the connection you build | The plugins sign in with OAuth, API Agents with their own credentials, and answers sent to a webhook are signed so your Agent can check they came from Taskriz |
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
- Your Agent needs someone who isn’t in front of it — an approval, a choice, a date, a photo from the field — and must reach them where they are.
- You’d rather not build and run an app, notifications, sign-in and delivery to get an answer back.
- Your Agent runs in Claude Code or ChatGPT, or anywhere that can call an HTTPS API.
When A2UI fits
- You’re building your own app or chat, and want your Agent’s interface drawn inside it, in your own design.
- The people answering are already using that app, while they talk to your Agent.
- You want an open-source format and to run every part yourself.
Questions
What’s the difference between A2UI and Taskriz?
A2UI is an open format for drawing an AI Agent’s interface inside an app you build and run. Taskriz is a service: your Agent sends a request, Taskriz takes it to the right person on their phone or computer — now or hours later — and brings their answer back as structured data.
Is there an alternative to A2UI?
It depends on what you need. If you want your Agent’s interface drawn inside your own app, in your own design, A2UI is made for that. If your Agent needs to reach people wherever they are and get their answers back, without building an app, Taskriz does that as a service.
Does A2UI have an iPhone or Android app?
A2UI isn’t an app people install; it gives developers renderers to build their own — an official SwiftUI renderer for Apple devices and Flutter for iPhone and Android, with Jetpack Compose planned and community renderers for more. Taskriz is one app that every Agent’s requests arrive in, in the browser on any phone or computer — nothing to install.
How secure is A2UI?
A2UI keeps an Agent to the components your app’s catalog allows, so it sends data rather than code. Sign-in, encryption and storage are designed by whoever builds the app around it. In Taskriz they come built in: requests are sealed to the person’s own devices, and interfaces run in a sandbox — see Security, above.
About this comparison
A2UI was checked in October 2026, at version 0.9.1, with version 1.0 a release candidate — from a2ui.org and the A2UI project on GitHub. A2UI is a project of Google and its contributors; Taskriz is not affiliated with it. What Taskriz is building next is on the Roadmap.