Skip to main content

​
When confirmation is required

Overlap requires explicit written consent in the current MCP conversation for:
  • publishing immediately
  • cancelling authorized social work
  • running a workflow with supported social external effects
The tool first prepares an immutable preview. The assistant shows that preview and asks you to approve or decline it in chat. It does not open a browser. If you approve in writing, the assistant passes your response verbatim to the MCP write tool, and Overlap records that consent before performing the action. Confirmations are bound to the signed-in user, organization, OAuth client, action, target version, content, account, and time. They expire after ten minutes and can be used once. When an action targets an organization other than the OAuth default, its organization ID remains a selector rather than a credential. Overlap rechecks that the signed-in user is still a member before preparing the preview, recording consent, and performing the action. You do not need to reconnect or change the portal’s active organization. If a post or workflow changes after preparation, the confirmation is rejected and a new preview is required.
Future scheduled publishing is fail-closed during the beta. You can create and edit a future calendar draft, but it cannot be authorized for publication yet. To publish it now, first update scheduledAt to null, review the immediate-publish preview, and provide new written consent.

​
Long-running operations

Workflow runs, renders, and publishing may return before work finishes. The result includes an operation or workflow-run ID and a suggested polling interval. Use:
  • overlap.runs.get for workflow execution
  • overlap.operations.get for renders and social operations
Common operation states include:
reconciliation_required means the external provider may have accepted an action but did not return a definitive response. Overlap will not blindly retry because doing so could publish twice.

​
Safe retry behavior

Each mutation has a durable idempotency receipt. Retrying the same accepted request returns its original operation. Reusing the same idempotency key for different input is rejected.

​
Example

Publish this YouTube draft now. Show me the exact title, description, account, and media, then wait for my confirmation.
The assistant may prepare the action, but publishing cannot proceed until you explicitly approve the exact preview in writing in the conversation.