OpenCode + Text to video
OpenCode runs the work loop and Text to video performs the selected operation. The Composer below preselects OpenCode, GPT-5.6 Sol, and this tool so you can test one real task with the same billing and recovery path as any AgentSky run.
How the combination works
OpenCode decides when to call Text to video.
OpenCode runs the coding-agent loop in the cloud: it explores the repository, edits files, calls tools, and executes validation with the selected compatible model.
Describe one coherent shot: the setting, subject action and camera movement. The current adapter defaults to Seedance 2.0 through BytePlus, submits an asynchronous generation job and returns an MP4 when the job succeeds. The configured default can be overridden by the deployment.
OpenCode
Owns the task loop, context, model calls, tool choice, cloud computer, progress and final result.
Text to video
Performs the operation exposed by the current Text to video capability. Its input limits and output shape come from the live tool guide and adapter.
AgentSky
Keeps the selected agent, model, capability grant, task state and usage record together. Tool charges and model or runtime charges remain itemized separately.
Setup and first task
Start with one bounded text to video task.
The Composer carries OpenCode, GPT-5.6 Sol, and Text to video. Begin with the smallest input that lets you inspect the output before expanding the workflow.
Open the OpenCode Composer
The Composer above preselects OpenCode, GPT-5.6 Sol, and Text to video. Add the target, required inputs and a concrete expected result; the draft stays in place through sign-in.
State the Text to video boundary
Generate a slow camera move through a quiet studio with plants and a laptop on the desk. Use natural morning light and no text.
Run and verify the returned result
Check the output against the source or brief, confirm that the result has the expected format, and inspect the task usage for model, runtime and tool charges.
Inputs, cost and limits
What OpenCode + Text to video establishes
Model-flexible coding work where teams want OpenCode's workflow with a wider choice of compatible model providers.
Configure and verify
- OpenCode and GPT-5.6 Sol are preselected for the browser evaluation.
- Text to video is enabled from the current capability catalog with its live input and output guidance.
- The first task can be checked from the returned artifact, text or provider result before a larger workflow is attempted.
Still depends on the task
- A tool guide does not guarantee a provider result for malformed, blocked or unsupported Text to video inputs.
- A successful tool call does not establish that the result is correct for your business decision; inspect the output at its source boundary.
- Total task cost can include model tokens, active computer time and the selected tool's billable units.
Current Text to video rates
seedance.generate
$0.304 per second.
Tool-specific details
Use the current Text to video contract.
Describe one coherent shot: the setting, subject action and camera movement. The current adapter defaults to Seedance 2.0 through BytePlus, submits an asynchronous generation job and returns an MP4 when the job succeeds. The configured default can be overridden by the deployment.
Catalog controls
prompt is required; duration defaults to 5 seconds, with a catalog range of 1–10. ratio accepts 16:9, 9:16 or 1:1.
Generation flow
A submitted job has a task ID. The waiting path polls for completion and returns an MP4 artifact; the configured timeout is five minutes.
Default model
dreamina-seedance-2-0-260128. The adapter strips user resolution flags, so a request for 1080p is not a supported resolution control.
Common questions
Related resources