What a card is

A card is a small, interactive view that appears in the chat when your AI uses ahel. Instead of a wall of text, you see the result laid out: a list of issues, one customer's details, a draft to review, or a change waiting for your press.

#What cards show

• Results from your apps: a list, one record in detail, or the outcome of an action.
• Confirm cards for changes, with the values filled in and one button. Nothing runs until you press it. See Confirm, receipts and approvals.
• Setup steps, such as an app that still needs your key, with a link to finish it on ahel.ai.
• Approvals waiting for an owner or team lead, on the Team plan.
• Errors, said plainly, with what to do next.

#Where cards appear

Claude shows your apps as cards. ChatGPT works through Developer mode, on plans that allow custom apps; we have not verified cards there yet. Cursor, Claude Code and Codex get complete text.

Cards depend on the AI tool drawing them. ahel sends both the card and its text in every answer, and the tool shows what it can.

#The text version

Every card has a complete text version with the same facts. Your AI reads the text, so it can summarise, compare or continue from a result whether or not you saw a card. In a tool without cards you lose the layout, not the information.

The one thing a tool without cards cannot do is press a confirm button in the chat. For that, ahel gives your AI a link to the same confirm on ahel.ai, and you press it there.

#Cards for your own app

Apps you build in Studio get cards too: you shape how their results look before anyone uses them. See Build and publish in Studio.

#The protocol word

Cards use the MCP Apps extension of the Model Context Protocol. An AI tool that supports MCP Apps can draw them; one that does not shows the text.