Zymcos Docs
How to use Zymcos, the AI creative operations platform: making takes with CODA, running a production, and reviewing and delivering the work.
Where to start
Make your first shot
From opening Zymcos to a finished take, in five steps.
Run a production
A script, a bible that keeps characters consistent, and autopilot.
Review and deliver
Check the work, compare versions, and keep what you choose.
For studios
Sign-in, spending and storage limits, how your files and data are handled, and team features as they ship.
What’s new
Version 0.16.0: Compare, the one-row chrome, the Sequence on the Viewport, and music built dark
- Compare one cut with another (customers and operators): a cut's Export Room now has *Compare with another cut*. Cuts, picture lock and the Export Room
- Download your circled takes as one zip (customers and operators): the Export Room of a cut now has *Your circled takes*: every take you circled with ★, from anywhere in the production, as one zip named for scene, shot and take, with the count and size said before you click. Cuts, picture lock and the Export Room
- More ? cards on the public pages (customers and operators): fourteen more pages now end a sentence that tells a reader to find or press something in a ?: Create in Files, Decisions in Files, the tabs above the work area (Home, Script, Bible, Viewport, Files), Settings and Sign out in the top bar, and the Book's chapters, besides the right column, Requests, the versions list, the message box and the phone's bottom bar. Create an image or a clip from words and pictures
All documentation
Start here
- Welcome to ZymcosZymcos is an AI creative operations platform: one workspace where creative work is generated, reviewed and delivered. You tell CODA, the built-in assistant, what you want, and nothing is generated or paid for without your approval.
- Your first shotThe shortest path from opening Zymcos to a first finished take: five steps, one of which spends money. You ask CODA for a single image, and you need no script, bible or files first.
- PlaybooksA playbook is a ready-made way of making one kind of piece, such as a 30-second ad or a music video. It gives CODA the questions to ask and the order to work in, with a typical cost before you spend anything, and it never spends or approves for you.
Make
- Asking CODA to do something to a takeAnything the controls under the picture can do, you can ask CODA to do in the chat. "This" means the take on the stage; CODA does some things straight away and puts others on a card for you to click.
- Running a brief on autopilotOn autopilot, CODA plans the work, you approve the plan and its spending cap once, and the run makes the takes, stopping for review where the plan says. It never spends more than the cap. Autopilot runs come with the Studio and Enterprise plans.
- Cancelling a takeCancel stops the waiting: the take is marked Cancelled at once and nothing more is asked of the provider. It cannot always stop the bill. If the provider had already started, the take may still arrive and is charged.
- When a take failsWhen a generation produces nothing, the card in CODA says so in plain words, and you are not charged for a take that failed, with two rare exceptions where the card's own sentence says what it cost. It also says whether trying again can help.
- The Sequence: approving a storyboard and working with its framesHow to put a saved storyboard version up for approval, what Studio does until it is approved, how to change the order of a locked script's frames by asking for the change, how the Preview plays the sequence, and how the footer's menus, zoom, voice and height work.
- Sound, loudness and the checks on a finished videoHow loudness is set for each destination, the checks a finished video goes through before it can be delivered, and what music and sound effects will do when they arrive in the next release.
- The Book: where your production stands, its plan and its lessonsThe Book tab shows what CODA knows about your production: where it stands, a plan you and CODA keep, lessons CODA follows, and an activity feed of everything that happened. CODA reads the same pages you do, and a long conversation no longer loses what was settled early.
- Activity: everything that happened in your productionThe Activity chapter of the Book lists every action in a production, newest first, as one sentence each, with who did it and how it ended. You can search it, narrow it, take it away as a file, and CODA reads the same list.
- CODA points at the screen: links, approvals and what is wrongWhen CODA wants you to look somewhere she gives you a link that opens the exact place. She approves scenes and circles takes when you ask in your own words, and she can check your production for what is wrong or missing.
- Create an image or a clip from words and picturesCreate makes an image or a clip from a description and pictures you choose, each marked as a character, a style, a composition or an object, with no script or shot needed. It makes a card; the price is on the card and nothing is spent until you click it. A character is held, or no card is made.
- The Advanced panel: choose the model, set the details and see the priceThe Advanced panel in Create shows as much of a take as you choose: Simple (CODA chooses), Controls (the model and common settings) or Expert (every setting and the seed). It prices the take as you change it and spends nothing; a card is the only way to spend.
Run a production
- Writing a scriptThe Production Book holds a production's scripts as structured data: scenes, typed beats and links to the entities in your production bible, so later stages such as the board and the continuity check can read a script instead of parsing one.
- The production bibleThe production bible records what "the same" means for each recurring character, place, prop or look, with the reference images that define it, and whether you have the right to use each. The Bible tab is where you build it; CODA can add to it and draft its rights, and only you affirm them.
- Spending limitsA take spends only inside two limits: the daily limit of the production you are working in and, for an autopilot take, the run's own cap you approved with its plan. A card shows its price before you click, and the price is the clip's length times the model's rate.
- Live updatesThe production you have open keeps itself current: when anyone changes something in it, every open screen shows the change within a few seconds, without a reload. There is nothing to switch on.
Review and deliver
- The continuity gateEvery generated shot is measured against the locked references it committed to, and the measurement is stored with the shot, so "this shot held" is evidence rather than an opinion. Today the gate measures and reports; it does not yet reject a drifting shot.
- Finals and requestsA final is the take a person accepts as a shot's answer. You propose a take, the production checks it, and someone who can approve accepts it; in Solo one click does all three. This page explains the Requests tab, the eight checks, "Not measured", and what you can accept past.
- Decisions and the charterA decision is something the production settled that should hold for every take, written down so people, the checks and CODA all work to it. The charter is the production's goal, audience and tone in a few sentences. This page explains how to write, propose, accept, amend and withdraw a decision.
- Cuts, picture lock and the Export RoomHow to lock the picture, make a numbered cut for the destinations you need, see how many render minutes an export will use before you click, check the cut in plain words and deliver it, and what CODA can do for you on the way. A cut never changes after it is made.
- Sharing a storyboard for reviewA review link lets a client open one saved storyboard version without an account, leave a note on any frame and say Approve or Ask for changes. This page explains how to make, extend, revoke and clear a link, what the reviewer sees, and what a verdict does and does not do.
Files and history
- Your filesEvery production has a Files tab holding everything it has made and everything you brought in. Nine fixed folders say where each file is stored, you make your own folders to organise them, and views, boards and search help you find them. You can name, star and rate takes, download originals and put a file on the stage.
- Every version of a takeThe History tab lists every version of the take on the stage: what it was made from, who made it, when, and what it cost. Versions are numbered v1, v2, v3 in the order they were made, and a number never changes.
- Content Credentials on your filesZymcos copies every generated file into your storage byte for byte, so any C2PA record (Content Credentials) the provider embedded stays intact, and it reads the copy to note what it carries. Nothing is added, altered or refused because of what it finds.
Account and access
- Signing in and outZymcos does not keep your password: you sign in on a page run by Zynth Auth, and Zymcos then starts a session. This page says how a session starts, how long it lasts, what ends it and what you see when something goes wrong.
- Storage and the storage quotaA workspace's stored files are counted in bytes and can have a storage quota. A quota only stops you starting a new take: it never refuses the copy of a take already paid for, never charges for what it refuses, and never deletes anything.
- SettingsThe gear in the top bar opens Settings, where you can lower your spending limits for a production or for yourself, see why each limit is what it is, and see what changed it. You can only set a limit lower than the one the team running your workspace allows, and raising one asks you to confirm.
- Who handles your dataThe companies that process your content on Zymcos's behalf, what each one sees, and what each has committed to. Nothing you make is used to train anyone's models.
Help
- Asking the docs a questionEvery page has a question box that answers from this documentation only, using AI, and lists the pages it used. If no page covers your question, it says so and links to support instead of guessing.
- Support requestsA support request is one conversation between your workspace and Zynth about one problem. The record is built, but there is no form to open one yet. This page says what a request holds and how it moves from open to closed.
- Too many requestsIf requests arrive faster than a speed limit allows, Zymcos refuses the request and asks you to wait. A refused request did nothing: nothing was saved, started or charged, so trying again is safe.
- GlossaryThe words Zymcos uses for its own parts, in alphabetical order, each with a short meaning and the page that explains it fully.