Skip to main content
Questions or issues? Contact us at api-support@manus.ai. This page lists every waiting event type that you answer with task.confirmAction. Use it when you render your own confirmation UI for one event type or for all of them. For the end-to-end flow, read Confirm an action first.

How to read an entry

Each entry is named after status_detail.waiting_for_event_type and contains: The examples use sample data in production formats. Task IDs and event IDs are 22-character IDs. action_id is a 22-character ID for connector tools, or the model’s tool-call ID for built-in tools such as the terminal. Treat every ID as an opaque string.
confirmed: false means the event did not consume the input and the task is still waiting. A target’s tool_used.status describes the preparation step, not the pending action: many targets report success while the action still waits. Each entry documents only the inputs that it lists. { "accept": false } cancels only where an entry lists it; do not send it for other event types, because its effect there is not documented. To skip without a schema-specific input, resume without a decision.

Index

Manus agent events

These events come from tools that the current Manus agent runs in the main task loop.

Email

Context: tool_used.params.messages[]: recipients, subject and body. Array positions are the values for indices.Waiting status:
Inputs:Optional indices applies the decision only to the listed positions in params.messages[].Target event:
Context: tool_used.params.messages[]: recipients, subject and body. Array positions are the values for indices.Waiting status:
Inputs:Optional indices applies the decision only to the listed positions in params.messages[].Target event:

Calendar

Google and Outlook calendar types share one input schema. event_id is the provider event ID: a Google Calendar event ID, or a Microsoft Graph event ID for Outlook.
Context: tool_used.params.events[]: title, time, location, attendees and reminders.Waiting status:
Inputs:Target event:
Context: tool_used.params.events[]: the event ID and only the fields that change. The current title and time are not exposed; read them from the calendar with event_id if you need a before-and-after view.Waiting status:
Inputs:Target event:
Context: tool_used.params.events[]: the calendar ID and event ID. The title and time of the event are not exposed; read them from the calendar with event_id if you need to show them.Waiting status:
Inputs:Target event:
While the deletion waits, this target reports status: "success" and a past-tense description. Decide from the waiting status, not from the target status.
Context: tool_used.params.events[]: title, time, location and attendees.Waiting status:
Inputs:Target event:
Context: tool_used.params.events[]: the event ID and only the fields that change. The current title and time are not exposed.Waiting status:
Inputs:Target event:
Context: tool_used.params.events[]: the event ID only. The title and time of the event are not exposed.Waiting status:
Inputs:Target event:

Terminal and data APIs

Context: tool_used.params: the command and its working directory (cwd).Waiting status:
Inputs:always_allow is optional. { "accept": true } runs only this command.Target event:
Context: tool_used.params: the data API command that the notice stopped. The credit amount and per-API breakdown are not exposed, and the waiting status has no waiting_description.Waiting status:
Inputs:Target event:

Web projects

Context: waiting_description: the request text. The requested key names are not exposed as structured data; read them from the text or ask the user.Waiting status:
Inputs:Send key and value for each requested secret. Never log the values.Target event:

Social and commerce

Context: tool_used.params: the product ID (id, a Shopify GID) and name (display_name). Only delete operations wait for confirmation.Waiting status:
Inputs:Target event:
Context: tool_used.result.media: the prepared draft (caption, author and media). params is the original input. The waiting status has no waiting_description.Waiting status:
Inputs:There is no decline input. To leave the draft unpublished, resume without a decision.Target event:
Context: tool_used.result.adAccounts[]: the accounts to choose from. Use their id values.Waiting status:
Inputs:An empty selectedAccountIds returns confirmed: false.Target event:

Browser, media, and configuration

These types have no target event. start_event_id returns no event, so decide from waiting_for_event_type and confirm_input_schema.
Context: None. Get the browser list from browser.onlineList. See also Using My Browser.Waiting status:
Inputs:Target event: None. start_event_id returns no event.
Context: None. The model, duration and credit estimate are not exposed. Ask the person who owns the task, or resume without a decision.Waiting status:
Inputs:Target event: None. start_event_id returns no event.For this type, waiting_for_event_id is vga- followed by 12 hexadecimal characters, not a 22-character ID.
Context: None. Applying the suggestion needs connectors[].uid, which the API does not expose.Waiting status:
Inputs:Target event: None. start_event_id returns no event.
Context: None. The connector name is not exposed. Ask the person who owns the task, or resume without a decision.Waiting status:
Inputs:{ "accept": false } returns confirmed: false.Target event: None. start_event_id returns no event.

Earlier agent loop events

The current Manus agent loop does not create these types. They can appear in tasks that ran on an earlier agent loop, so handle them if your integration reads those tasks.
Context: waiting_description: the path of the service to deploy. start_event_id returns the same text as an assistant_message.Waiting status:
Inputs:global_allow is optional. { "accept": true } deploys only this time.Target event:
Context: tool_used.params: project name, title, description and scaffold (features).Waiting status:
Inputs:mode is quality, speed (default), or max.Target event:
Context: None in practice. The target is a tool_used event with empty params; the event asks which analysis mode to use.Waiting status:
Inputs:mode is optional: speed, quality, or max.Target event:
Context: tool_used.params: the title, the input list (iterableInput), the prompt template and the output fields.Waiting status:
Inputs:Target event:

Addon events

These events come from Addons, starting with the Webdev Addon. Only tasks created with client_capabilities get Addon cards. Addon Interaction Cards describes how to render each card.
Context: The addon_interaction message in task.listMessages whose addon_interaction.event_id equals waiting_for_event_id. Show its title, elicitation.message, and a form built from elicitation.requestedSchema. card_type names the card, for example webdev.blueprint. See Read the card.Waiting status:
Inputs:confirm_input_schema.properties.content is the card’s requestedSchema. The request returns after the Addon replies, within about 20 seconds. Never confirm info cards, or cards whose kind or elicitation.mode you do not handle. See Answer the card for errors and retries.Target event: The addon_interaction message described in Context. Its id can differ from addon_interaction.event_id, so match on addon_interaction.event_id instead of using start_event_id.