Animate Images With Actionway

Create one short video from one still image. Keep the workflow focused: improve the motion prompt, discover the current Actionway capability, quote the call, obtain confirmation, run it once, and deliver the downloaded video.

Workflow

1. Prepare Actionway

Use actionway --agent-host=codex as the prefix for every Actionway command.

1. Run actionway --agent-host=codex update --check once per session.
2. Run actionway --agent-host=codex whoami.
3. If authentication is missing, run actionway --agent-host=codex init, ask the user to approve browser access, and follow the returned skill.source installation instructions. Never request or expose credentials.
4. Run actionway --agent-host=codex --help if a command shape is uncertain. Treat the current CLI and registry as authoritative.

2. Resolve the source image

Accept PNG, JPEG, or WebP input when the selected service supports it.

• Prefer an existing HTTPS image URL from the user's message or attachment metadata.
• If only a local file path is available, do not invent a URL, embed a file:// path, or upload the image to a third party without explicit approval. Explain that the current Actionway video interface requires an accessible HTTPS URL and ask the user for one or for permission to publish the file through a destination they choose.
• Open or inspect the image before writing the motion prompt. Preserve the main subject, identity, product shape, text, logo, and composition unless the user requests a transformation.
• Do not submit sensitive or confidential imagery without warning that Actionway sends the required input to the selected tool provider.

3. Choose sensible defaults

Ask a question only when a missing choice would materially change the result. Otherwise use:

• duration: 5 seconds;
• aspect ratio: match the source image when supported;
• resolution: 720p;
• audio: off;
• generations: one;
• motion: subtle, coherent, and physically plausible.

Use 9:16 only when the user asks for a Reel, Short, TikTok, Story, or vertical social post. Never crop a source aggressively without mentioning it.

4. Write the motion prompt

Translate the user's intent into one concise production prompt containing:

1. the subject action;
2. the camera action;
3. environmental motion;
4. continuity constraints;
5. an explicit instruction to preserve important identity or product details.

Prefer one clear motion direction over a sequence of unrelated events. Avoid asking a five-second clip to contain multiple scenes.

Example:

A slow cinematic push-in toward the perfume bottle. Soft fabric and reflected light move gently in the background. Keep the bottle, label, logo, proportions, colors, and composition unchanged. Smooth realistic motion, no cuts, no new objects, no text distortion.

5. Discover and inspect the capability

1. Run actionway --agent-host=codex tools search "animate one still image into a short video while preserving the subject" --limit 3.
2. Choose only a returned tool_ref that accepts image input and produces video.
3. Run actionway --agent-host=codex tools inspect <tool_ref>.
4. Compare the inspected variants using current price, supported duration, aspect ratio, resolution, reference fidelity, latency, and provider data terms.
5. Prefer the least expensive suitable variant for a first draft. Do not memorize service names or prices.

If the user sets a maximum budget, pass it to capability search when supported and reject any inspected plan that exceeds it.

6. Prepare the paid call

Build arguments from the inspected schema exactly. Prefer the canonical Tool protocol:

actionway --agent-host=codex tools call <tool_ref> \
  --variant <variant_id> \
  --input-json '<schema-compliant JSON>' \
  --idempotency-key <stable-key>

Use a stable idempotency key when retrying the same request. Never resubmit merely because an asynchronous job is still pending.

When the response is confirmation_required:

1. Show the capability and variant.
2. Show the duration, resolution, aspect ratio, and effects.
3. Show Actionway's exact USD quote and maximum charge.
4. Ask for an explicit yes/no confirmation.
5. Do not spend or resume automatically.

After approval, resume only the prepared call:

actionway --agent-host=codex tools call --resume <call_ref>

If the user changes the image, prompt, duration, aspect ratio, resolution, or variant, prepare a new call and request a new quote.

7. Wait and deliver

• If the call returns accepted, immediately run actionway --agent-host=codex wait --job-ref=<job_ref>.
• Continue the same job reference if waiting is interrupted. Never submit a duplicate generation to recover a pending job.
• Download terminal video assets into the current task's outputs/ directory with a descriptive .mp4 filename.
• Present the local video to the user, followed by a compact receipt containing the service, actual charge, duration, resolution, and job reference.
• If the output is technically successful but aesthetically weak, explain the issue and propose one specific prompt adjustment. Do not spend on another generation without a new quote and confirmation.

Guardrails

• Never enable Auto Pay.
• Never exceed a user-provided budget.
• Never run multiple paid variants as an unapproved comparison.
• Never claim that a successful but disappointing generation is free or refundable.
• Never animate a real person deceptively or imply endorsement without permission.
• Refuse unlawful sexual, exploitative, impersonation, or rights-infringing uses.
• Preserve the provider and usage information returned by Actionway rather than inventing licensing claims.

Example requests

• "Animate this product photo with a slow camera push-in."
• "Make the water and clouds move in this landscape while keeping the mountains fixed."
• "Turn this illustration into a five-second vertical loop for Instagram."
• "Bring this character portrait to life with subtle hair and eye movement."