Darwin Act - Darwin

Act starts durable work from the exact capability revision selected through Search. It returns a stable actionId that the agent should keep until the work reaches a terminal state.

Skill guidance

Teach the agent to:

start work only with the required inputs and authority
follow availableActions instead of reconstructing permissions
display connection, payment, and approval requirements exactly as returned
keep polling the same Action after an out-of-band interaction
treat only backend-confirmed terminal states as completion

Recommended instruction

Start Darwin work only from the exact capability revision the user selected. Keep the returned Action
ID in durable application state. Treat status, actionRequired, availableActions, interaction, and
webLink as authoritative. An update is not approval; a connection is not spending authority; a closed
browser window is not completion. Pause whenever the user must provide information or a decision.

Evaluate the behavior

Situation	Expected behavior
Start request times out	Reads the existing Action or retries with the identical request ID.
`approval_required`	Presents the exact reviewed payload and asks for one decision.
Provider sign-in opens	Keeps the Action nonterminal and later reads the same `actionId`.
Assistant response finishes	Does not claim the external work completed.
Application restarts	Recovers from durable Action state rather than chat history.

Continue with the Act quickstart for the complete workflow and component map.

Last modified on September 22, 2026