Taskriz
Taskriz and the OpenAI Apps SDK
OpenAI’s Apps SDK puts your product inside ChatGPT conversations, for the ChatGPT user in front of it. Taskriz reaches anyone your Agent needs — no ChatGPT account required — and the Taskriz plugin for ChatGPT brings that to ChatGPT too.
Different jobs
OpenAI Apps SDK
OpenAI’s way to build apps that run inside ChatGPT conversations — now called plugins for ChatGPT and Codex. A plugin is an MCP server with an optional interface, shown in an iframe in the chat, for the ChatGPT user who’s using it.
Taskriz
A service for reaching people, wherever they are. Your Agent sends a request whose interface it designs to anyone paired with it — they need no ChatGPT account — and gets the answer back. The Taskriz plugin for ChatGPT (desktop and Codex) lets an Agent in ChatGPT reach someone else.
What they share
- An interface, not a wall of text. Both let an Agent show a person an interface to answer.
- MCP underneath. Both are built on the Model Context Protocol.
- ChatGPT. Taskriz is itself a plugin for ChatGPT — it works with the Apps SDK’s world, not against it.
Side by side
| OpenAI Apps SDK | Taskriz | |
|---|---|---|
| What it is | OpenAI’s SDK for apps in ChatGPT, now called plugins for ChatGPT and Codex, built on MCP and the MCP Apps standard | A hosted service that gives any Agent a way to reach people — with plugins, an MCP server and an API, and no app for you to build |
| Who answers | The ChatGPT user in the conversation — they need a ChatGPT account, and availability varies by plan and region | Anyone paired with your Agent — your team, your customers, contractors, family — wherever they are, straight away or hours later — no ChatGPT account needed |
| Where people answer | In ChatGPT, on desktop and mobile | The Taskriz app, in the browser on any phone or computer — nothing to install; email notices, and text messages in Australia (the United States soon) |
| What a request can ask | Any interface your app provides, in an iframe — inline cards, fullscreen or picture-in-picture | An interface your Agent designs for each request, from iOS-style building blocks — screens, lists, choices, switches, dates and times, numbers, notes, photos and documents — following world-leading human interface guidelines |
| Answers back to the Agent | Within the conversation: tool calls to your server, and messages into the chat | As structured data, matched to the request: through the plugins, a signed webhook, a WebSocket or the events list — whenever the person answers |
| Connecting your Agent | Your own MCP server, reviewed by OpenAI before it’s listed in its directory | Plugins for Claude Code and ChatGPT (desktop and Codex), the Taskriz MCP server for any MCP client, and an HTTPS API for any Agent or workflow |
| Cost | No fee stated by OpenAI; you build and host your server, and the people using it need ChatGPT | Free to start — 500 requests a month, no card; then Builder at $29 or Business at $99 a month. No seats, and the people who answer never pay |
Security
OpenAI keeps apps in an isolated iframe, reviews them before they’re listed, and limits the data they receive. Reaching someone outside ChatGPT isn’t part of it — and there, Taskriz’s protections come built in.
| OpenAI Apps SDK | Taskriz | |
|---|---|---|
| Who can reach a person | The ChatGPT user who uses your app; OpenAI reviews apps before listing them | 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 your server; accounts connect with OAuth 2.1 | 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 | ChatGPT, the model’s conversation and your server | Only the person’s devices — a request passes through Taskriz while it’s delivered, and is never stored or logged readable |
| Running the interface | An isolated iframe with a strict content security policy | In a WebAssembly sandbox with no network or file access of its own; pictures come through Taskriz, so a picture’s server never learns who opened a request |
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 person your Agent needs isn’t using ChatGPT — or isn’t in the conversation right now.
- They should answer on their phone or computer, later if need be, with no ChatGPT account.
- You’d rather not build, host and get an app reviewed: use the Taskriz plugin for ChatGPT, or the API.
- You want each request sealed to the person’s own devices.
When the OpenAI Apps SDK fits
- You want your product inside ChatGPT conversations, for ChatGPT’s users.
- The person you need is the one chatting, right now.
Questions
What’s the difference between the OpenAI Apps SDK and Taskriz?
The Apps SDK puts your app inside ChatGPT conversations, for the ChatGPT user in front of it. Taskriz takes your Agent’s request to anyone paired with it, on their phone or computer — no ChatGPT account needed — and brings the answer back.
Is the Apps SDK now called plugins?
Yes. OpenAI’s developer documentation now calls them plugins for ChatGPT and Codex: a plugin bundles skills, an MCP server and an optional interface.
Can a ChatGPT app reach someone who doesn’t use ChatGPT?
OpenAI’s documentation describes apps for the ChatGPT user in the conversation, not for reaching anyone else. Taskriz does that: the Taskriz plugin for ChatGPT lets your Agent send a request to anyone paired with it, on their phone or computer.
About this comparison
The OpenAI Apps SDK was checked in October 2026 from OpenAI’s developer documentation — plugins and security and privacy. Taskriz is not affiliated with OpenAI. What Taskriz is building next is on the Roadmap.