Unified Codex + Claude tutorial · infra

How to sync a Medux task with Medux MCP

Learn to sync a Medux task with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/tasks/{task_id}/sync

Sync the task with the upstream provider and return the latest local state.

Open the Sync Task API reference →
Choose your AI client

Follow the Codex or Claude workflow

The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.

Codex-specific workflow

Run Sync a Medux Task as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the exact task ID, select medux_sync_task, and keep the Medux task ID and returned output with the rest of the project. Naming the input roles and the expected result prevents an agent from guessing which file should be used where.

Codex prompt pattern

In this workspace, use medux_sync_task through Medux MCP to sync a Medux task.
First inspect and identify the exact task ID.
Show me the exact tool arguments before execution.
After the task completes, return the refreshed Medux task record and verify that the response belongs to the requested task and reflects the latest provider state.

Approval gate

Before approving the call, compare the selected tool, file or asset IDs, ordering, timing, and output settings with the request. If a local filename was mapped to an uploaded Medux file ID, keep that mapping visible so it can be audited later.

Result verification

Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the refreshed Medux task record. The final check is explicit: confirm that the response belongs to the requested task and reflects the latest provider state.

What this tutorial does

Medux operation

Sync the task with the upstream provider and return the latest local state.

Agent workflow

Codex selects medux_sync_task, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires a task id created by a clone, generate, or process request.
  • Use this when you want to refresh task state outside the default polling loop.

Prompt Codex

Start with a clear instruction that names the Medux operation and the intended inputs.

Use Medux to run Sync Task. Review the required inputs, call medux_sync_task, wait for the result if a task is returned, and report the output clearly.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
task_idstringRequiredProvide the value described in the API reference.

Step-by-step workflow

01

Connect Medux MCP to Codex

Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_sync_task tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Codex to run Sync Task

Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_sync_task and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Codex selects medux_sync_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Sync Task
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Sync Task API through MCP?

Codex can call the medux_sync_task Medux MCP tool to sync the task with the upstream provider and return the latest local state. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_sync_task. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Sync a Medux Task as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the exact task ID before proposing medux_sync_task. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.

Claude prompt pattern

Using the assets and requirements in this conversation, help me sync a Medux task with Medux MCP.
Restate which input fulfills each role: the exact task ID.
Propose the medux_sync_task call and summarize its arguments before asking for approval.
When it finishes, return the refreshed Medux task record with a checklist confirming that the response belongs to the requested task and reflects the latest provider state.

Context checkpoint

Have Claude summarize the intended transformation, identify every source asset by role, and list the important constraints. Review that summary together with the proposed tool arguments; correct the conversation first if a file, order, time range, or setting is ambiguous.

Result verification

Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the refreshed Medux task record plus a concise validation checklist confirming that the response belongs to the requested task and reflects the latest provider state.

What this tutorial does

Medux operation

Sync the task with the upstream provider and return the latest local state.

Agent workflow

Claude selects medux_sync_task, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires a task id created by a clone, generate, or process request.
  • Use this when you want to refresh task state outside the default polling loop.

Prompt Claude

Start with a clear instruction that names the Medux operation and the intended inputs.

Use Medux to run Sync Task. Review the required inputs, call medux_sync_task, wait for the result if a task is returned, and report the output clearly.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
task_idstringRequiredProvide the value described in the API reference.

Step-by-step workflow

01

Connect Medux MCP to Claude

Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_sync_task tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Claude to run Sync Task

Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_sync_task and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Claude selects medux_sync_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Sync Task
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Sync Task API through MCP?

Claude can call the medux_sync_task Medux MCP tool to sync the task with the upstream provider and return the latest local state. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_sync_task. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I sync a Medux task with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_sync_task call, and verify the returned result. The tabs above keep client-specific prompting on one canonical page.

Can I use the same Medux tool in Codex and Claude?

Yes. The client interaction differs, but both use the same Medux MCP tool and API request contract shown in this tutorial.

Related developer intent

Use AI agents to sync a Medux task

This tutorial addresses developer workflows for sync AI media task API and refresh asynchronous job status by making the task repeatable through the Medux API. Codex or Claude can prepare inputs, show the MCP tool arguments for approval, monitor processing, and return an output that can be checked against the original request.

This infrastructure step supports long-running image-to-video, AI lip sync, and video watermark-removal jobs by keeping uploads, task IDs, status checks, and returned media auditable.

Run an asynchronous image-to-video jobRun an AI lip sync taskRun video watermark removal
Can Codex or Claude sync a Medux task through Medux MCP?

Yes. Use the client-specific tab above to prepare the inputs, review the Medux tool call, run the operation, and verify the returned result. The linked API reference remains the source of truth for supported fields and limits.

Production, trust, and developer intent

Build a privacy-conscious, auditable workflow to sync a Medux task

This infrastructure step belongs to a unified, multi-model AI media API workflow for Codex MCP, Claude MCP, and other agents. Use one authorized API context, keep task and asset IDs in the calling system, poll asynchronous work, and return only the media result required by the application.

Privacy-conscious operation means keeping credentials outside prompts, uploading only necessary files, limiting access, and defining retention and deletion rules in your own application. Do not infer undocumented encryption, retention, webhook, or compliance guarantees from this tutorial.

How does task polling support production AI media workflows?

Store the Medux task ID, poll until a terminal state, handle failure without duplicate submissions, and attach the accepted result to the originating application record.

Build with the API

API reference and official examples