Skip to main content
Questions or issues? Contact us at api-support@manus.ai. Addons can show cards in the conversation. Some cards need an answer before the agent continues, for example the Webdev project blueprint (features and design direction). Other cards only show information, for example a saved project version with its screenshot. In the Manus app these are interactive cards. Over the API, Manus returns each card as JSON, and your client renders it. Form cards use the MCP elicitation form format. There are two kinds of card. An elicitation card is a form that the user answers. An info card only shows information and has no answer. When a form card makes the agent wait, status_detail.waiting_for_event_type is addonInteraction. Confirmation Events shows its waiting status and the inputs it accepts. For polling and the general confirmation flow, see Task Lifecycle.

Opt in when you create the task

Declare what your client can render in task.create:
  • { "elicitation": {} } also means form support, as in MCP.
  • This release supports only form. URL mode is not available yet.
  • info: {} means your client can show display-only cards (kind: "info"). Without it, you get no info cards.
  • Without client_capabilities, nothing changes: you get no addon_interaction messages. The task can show waiting without confirm_input_schema, and the Addon continues with its defaults when its own deadline passes (the Webdev blueprint waits about 60 seconds). To steer it, use task.sendMessage.
  • With interactive_mode: false, Addons do not wait for an answer. They continue with their defaults.

Read the card

The card arrives in task.listMessages as an addon_interaction message:
requestedSchema is always a flat object with at most 32 properties. Each property is one of:
  • string, optionally with minLength, maxLength, and format (email, uri, date, or date-time).
  • number or integer, optionally with minimum and maximum.
  • boolean.
  • A single choice: oneOf with const and title, or enum.
  • A multiple choice: array with items.anyOf or items.enum, optionally with minItems and maxItems.
Every property can have title, description, and default, and the object can have required. No other keywords appear. A choice has at most 64 options. Its default is one of the options; for a multiple choice it is a subset of the options without duplicates. Check the answer against these rules before you submit it. Manus checks the same rules and returns 400 invalid_argument when the answer breaks one. Option values (const) are non-empty strings that the Addon chooses, for example style_0. Do not depend on their format: show title to the user and send back const. The order of keys in properties is not guaranteed, so do not depend on it. Arrays keep their order: the options in oneOf, anyOf, and enum, the required list, and display.media. To lay out the form, see Render the card. When the card makes the agent wait, the waiting status_update points at it: waiting_for_event_type is addonInteraction, waiting_for_event_id is the card’s event_id, and confirm_input_schema describes the answer. Some cards do not make the agent wait; you can still answer them until the card is closed (see Answer the card).

Render the card

Render a card from its fields. The same rules work for every Addon and every card_type, so your client can show cards that did not exist when you built it. The layout, colors, and fonts are your choice. Show each card in the conversation at its position in task.listMessages. When a newer message has the same card_id, replace the older card with it. For an elicitation card, render one control for each property in requestedSchema.properties:
  • Lay out the controls in a stable order, because the order of keys in properties is not guaranteed. We suggest the properties in required first, in array order, and then the others by name.
  • Use the property’s title as the control label, and description as help text. If there is no title, use the property name.
  • Preselect default. Mark the properties in required as required.
  • display.option_media[<property>][<option value>] is the id of an image in display.media. Show that image with the option.
  • Add a submit button that sends accept with the form values, and a decline button that sends decline. If your UI lets the user dismiss the card, send cancel when they do. Each card_type defines what decline and cancel mean; for example, both mean “Skip all” for webdev.blueprint. See Answer the card.
Manus checks each card before it sends it to you. Use these limits to plan your layout. Lengths count UTF-16 code units, as JavaScript String.length does. Manus removes leading and trailing spaces from title, the messages, alt, and link labels, and never sends them empty.

Info cards

An info card shows information and has no answer. This Webdev card reports a saved project version with its screenshot:
  • Render it as described in Render the card.
  • info.links is optional. Each link has id, label, and an https url. Open it in a browser.
  • info.data is optional structured data. Each Addon documents its fields per card_type; see Webdev Cards. If you do not use them, ignore them.
  • An info card never makes the agent wait, and it has no expires_at. It can arrive at any time while the agent runs, for example right after the agent saves a project version.
  • Do not call task.confirmAction for an info card. Manus rejects it with 400 failed_precondition.

Sensitive cards

When sensitive is true, the answer contains a secret, for example an API key:
  • Render the string properties as password inputs. Do not log the answer, and do not show it again after the user submits it.
  • The card has no default values.
  • Manus does not store the answer: not in the task history, not in task.listMessages, and not in any cache. Manus passes it to the Addon inside the task.confirmAction request. If that request fails, the user must enter the secret again, or your client resends it from memory.

Webdev cards

The Webdev Addon sends these card_type values: webdev.blueprint, webdev.secret, webdev.hosting_confirmation, webdev.publish_confirmation, webdev.visibility_confirmation, webdev.checkpoint, and webdev.unsupported_step. Webdev Cards describes each one: when it appears, its fields and info.data, how to answer it, and how the Manus web app shows the same step.

Answer the card

Call task.confirmAction with an MCP ElicitResult:
  • accept requires content that matches requestedSchema.
  • decline (the user said no) and cancel (the user dismissed the card) take no content.
Manus checks the answer against requestedSchema and passes it to the Addon inside this request. The request returns after the Addon replies, within about 20 seconds. confirmed: true means the Addon accepted the answer. The agent then continues on its own; Manus does not send a status update for the card. Disable the submit button while the request runs. Treat the card as closed when any of these happens:
  • task.confirmAction returns confirmed: true.
  • task.confirmAction returns 400 failed_precondition.
  • The card made the agent wait, and the task no longer waits for it: status is not waiting, or waiting_for_event_id points to another event. This happens, for example, when the Addon’s deadline passes.
  • The user sends a new message, or you stop the task.
task.confirmAction errors for these cards:

Handle what you do not recognize

New card kinds and modes will be added. Your client must not fail on them. If kind or elicitation.mode has a value you do not handle:
  • Show title and, if present, elicitation.message or info.message as plain text.
  • Do not render controls, and do not call task.confirmAction for that card.
  • Let the user reply in the conversation, and send the reply with task.sendMessage.