DGC v0.51.0 is out
Navigate
Install DGC
DGC v0.51.0Edit on GitHub ↗
Features/Plugin cards

a plugin's own card in the chat (MCP Apps), in Work, ChatDGC, Pips and the terminal

Plugin cards

#

Some plugins come with a card: their own small app, such as Cardboard's project list or a map, that shows up in the chat right under the step that asked for it. DGC shows it automatically whenever the plugin offers one. Cards use the open MCP Apps standard, so a plugin built for Claude, ChatGPT or VS Code's chat shows the same card here.

Where you see them

#
  • Work. Under the tool's row in the chat, with the plugin's name and the step above it.
  • ChatDGC. Above the words of the reply that used the plugin.
  • A Pip's chat. Under the Pip's reply. A Pip that opens a card while you're away keeps it in its chat for when you look.
  • The terminal. A card can't be drawn there, so one line says Cardboard opened a card · Open it. Click Open it, or type /cards, and the card opens in your browser on a page DGC serves on this computer for that chat alone. The tool's own text still shows as before.

A card comes back when you reopen the chat or reload the window. The model is told in one line that a card was shown; it never reads the card's page. Use Collapse beside its name to make room for the conversation; Expand brings the same live card back. A failed plugin call leaves its error in the tool result and opens no empty card.

What a card can do

#

A card is the plugin's own page, and it looks the way the plugin designed it. DGC gives it your editor's light or dark theme and its colours, and the room to grow up to a comfortable height.

  • Ask its plugin for something. A read runs: a tool its plugin marks read-only, or one on DGC's reviewed list of reads that its plugin doesn't mark otherwise (a tool marked destructive is never a read). A change shows DGC's own Allow card above the card first: Allow, Always allow or Don't. A plugin that can move money asks every time and never offers Always allow, and neither does a call one of your own ask rules asks about. In Work your permission mode and rules decide as they do for the model's own calls (a deny rule refuses it, an ask rule asks, auto mode lets other changes through, plan mode refuses them); in ChatDGC and Pips the plugin's own setting in Settings ▸ Plugins does. Always allow is the same rule Settings ▸ Permissions lists, so you can remove it there. Your answer is checked again before the call runs: a question that expired, a plugin turned off or a deny rule added since runs nothing.
  • Send a message for you. It arrives as your message, starting From Cardboard's card:.
  • Tell the model what you did in it. The next reply in that chat sees it once, marked as the plugin's content, never as instructions.
  • Open a link. It opens in your browser. A site the card didn't say it would use asks you first.
  • Save a file. You choose where, in a save dialog.
  • Use the whole window. The card opens in an editor tab of its own. The button at the right of the card's name does the same.

How it is kept safe

#

The card runs in a sandboxed frame at an address of its own on this computer: one address per plugin, so two plugins' cards can't reach each other, and nothing in DGC's chat, your editor or your other chats is visible to it. It can reach only the sites its plugin declared for it; a card that declared none can reach nothing. Everything it asks goes through DGC, only to its own plugin, and a tool its plugin keeps for the model alone is refused. DGC listens to a card only at its own address, so another page loaded into its frame can't speak for it.

In the SDK

#

An SDK app opts in with session.cards.watch() and gets each card as an mcp_app_card event: draw it yourself, and pass what it asks to session.cards.call(...). See the SDK guide.

Documentation