What’s new

What changed in each Zymcos release, with a link to the page that explains it.

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
  • A ? beside a sentence shows where to find the thing (customers and operators): on four public pages, thirteen sentences that tell a reader to find or press something now end in a ?: the Sequence strip and its resize bar, the four views, the versions list, a frame's menu and Requests; Files, then Cuts, the four lists of Files and the + beside Folders; the production name, the message box, the right column's tabs and the bar at the foot of a phone. The Sequence: approving a storyboard and working with its frames
  • CODA says what each export measured (customers): asked whether a cut is ready, she now reads each destination's stored technical-check result and tells every failing or unmeasured check with its figures and the way out; an export with no stored result is told as not measured, never as passed. Cuts, picture lock and the Export Room
  • The production chrome is one row that folds, with no phase headings and no double rule: the PRE-PRODUCTION, PRODUCTION and POST-PRODUCTION headings are gone from the tab bar and the Sequence bar (the order of the tabs is the order of the work). Writing a script
  • The Sequence plays on the Viewport: choosing Preview in the Sequence strip, pressing the new Play button on the strip's top line (the strip can stay shut), or choosing Play from here on a frame's menu puts the playback on the Viewport, the one place a picture is looked at, in place of the take and its buttons. The Sequence: approving a storyboard and working with its frames

Version 0.15.0: Assembly, Cuts and the render service

  • Make a card carries the model and settings you chose (v0.15.0; customers and operators): in Create, the Advanced panel's Make a card is no longer switched off when you pick a model or change a setting: the card is that take, with the model, the settings and the seed, and its price is the price in the box. The Advanced panel: choose the model, set the details and see the price
  • Music and effects on the cut, ducked by data (v0.15.0 F1; customers and operators): the music and effect lanes take layers: an audio file with a level that can change along its length, fades, and for music a duck ("12 dB under the voice, 200 ms to fall, 600 ms to rise") that the preview and the export play the same; a cut without sound is unchanged to the digit. Sound, loudness and the checks on a finished video
  • Loudness set for each destination, with stems (v0.15.0 F2; customers and operators): an export for a destination mixes its sound, measures the mix and sets its level to the destination's target and peak ceiling (EBU R 128 and ATSC A/85 for TV, the platforms' reference levels for the internet; each figure names its source and is unreviewed until the owner reads it), and delivers the dialogue, music and effects stems where the destination asks for them. Sound, loudness and the checks on a finished video
  • A music track needs a licence on record before an export (v0.15.0 F3; customers and operators): a person records the kind, licensor, reference and last day of a track's licence (PUT/GET on the asset); an export with a track that has none, a withdrawn one or one that has run out stops before anything is made, with nothing charged, and says so. Sound, loudness and the checks on a finished video
  • Technical checks on a finished export (v0.15.0 F4, F5, F6; customers and operators): an export is measured for loudness, levels, picture, format and flashing (framing and captions when the Cut supplies their facts), each required, advisory or not asked for by the destination; the result is kept with the render and read at GET /api/v1/projects/{id}/renders/{job}/qc. Sound, loudness and the checks on a finished video
  • A cut is ready when its last render finishes, and its evidence carries what was measured (v0.15.0 E with F; customers and operators): the render worker's process now tells the cut that asked for an export, so a cut becomes ready by itself and nobody has to press Check again (which still does the same thing); the evidence pack holds each destination's technical checks as measured and names any destination with none, which is never shown as passed. Cuts, picture lock and the Export Room
  • A failing technical check holds a delivery back (v0.15.0 E with F, ADR-0227 §6; customers and operators): the cut's checks gain a tenth, Technical checks: it reads what the render worker measured on each finished destination, fails when a required check failed (naming the destination and the check) and may be gone past with a reason that the evidence pack records; a required check that could not be measured, and a destination nobody measured, show as not measured and are never a pass. Sound, loudness and the checks on a finished video
  • A music track with no licence stops a delivery (v0.15.0 E with F; customers and operators): the cut's Rights cleared check now fails for a music or effect track with no valid licence on record, naming it in a sentence, and no reason goes past it, as with the rest of Rights. Sound, loudness and the checks on a finished video
  • Ask CODA to lock the picture, make a cut, check it and export it (v0.15.0 E, ADR-0225; customers and operators): "make a cut for YouTube and TikTok" and "check cut 2 again" are done when you ask in those words and CODA says what she did; when it was her idea, or you did not say where the cut goes, she puts up a card and nothing happens until you click it. Cuts, picture lock and the Export Room
  • Lock the picture, make a numbered cut, see the minutes before you export (v0.15.0 E; customers and operators): in Files, the new Cuts section states whether the picture is locked and what that means, locks it when every picture is its shot's final (and names the shots that are not), and unlocks it with a reason. Cuts, picture lock and the Export Room
  • Deliver a cut: signed, sealed with its evidence, or refused (v0.15.0 E; customers and operators): Deliver (the approve right) re-runs the checks, signs each destination, seals an evidence pack and makes the cut Delivered, or refuses and keeps nothing; each check that may be gone past asks for a reason that is kept, and Rights cleared never can be. Cuts, picture lock and the Export Room
  • Choose the model, set the details and see the price, in Create (v0.15.0 H2; customers): under Quality, the Advanced panel starts on Simple and, one step up, shows the Model list (each with its price for this take and its terms in plain words, and the reason a model cannot be chosen) and the settings that model marks as common; Expert adds every setting, the seed and which model CODA would have chosen instead. The Advanced panel: choose the model, set the details and see the price
  • A setting for how much of a take you see (v0.15.0 H2; customers and operators): How much of a take you see and set (Simple, Controls or Expert) is yours alone: no production or workspace sets it. Settings
  • Ask CODA about what you pointed at (v0.15.0 D2d; customers and operators): on the Preview, Ask CODA about this (beside the name of the layer you pointed at) puts that layer into your next message, opens CODA's column, and CODA is told its name and, for a block, what it holds; pressing it again or letting go of the layer takes it back, and sending uses it once. The Sequence: approving a storyboard and working with its frames
  • CODA places charts, diagrams, code and moving lines, and changes a block you have added (v0.15.0 D2c; customers and operators): "a bar chart at the start with North 120, South 80 and West 45", "a flow diagram of ...", "lines of code ...", "rising lines that say ...", then "change the bar chart's unit to percent". The Sequence: approving a storyboard and working with its frames
  • CODA's take cards carry the settings you ask for (v0.15.0 H, ADR-0214; customers and operators): "make it eight seconds", "four pictures", "use seed 7" go on the card and the price shows them; a setting the model does not offer, or a value outside what it takes, is refused before any card exists and CODA says what the model does take. Asking CODA to do something to a take
  • Point at a block on the Preview to change it (v0.15.0 D2d; customers and operators): click a chart, diagram, lines of code or a line of text on the Preview and it is outlined and named; Edit this block opens that block's form, and Undo reverses the change. The Sequence: approving a storyboard and working with its frames
  • See, change and remove the blocks on the cut (v0.15.0 D2c; customers and operators): the Sequence's Add menu has Blocks on the cut, which lists each block that was added (what it says and where it is) with Edit, the same form on its own fields, and Remove; Undo reverses either. The Sequence: approving a storyboard and working with its frames
  • Add a block to the cut from the Sequence (v0.15.0 D2c; customers and operators): the Sequence's Add menu has Block, a form for a title card, lower third, end card, legal line, caption, a bar, line or donut chart, a big number, a flow diagram, lines of words or lines of code: it is built from the block's own fields, says what is wrong beside each box before sending, and puts the block at the start, the end or at a shot; Undo takes it off. The Sequence: approving a storyboard and working with its frames
  • Shape the cut by asking CODA. Say what you want in your own words and name the frames: "make the change between frames 2 and 3 softer", "add a title card at the start", "slow frame 2 to half speed", "fill the picture with frame 3, keeping the left in view", "fade out at the end". The Sequence: approving a storyboard and working with its frames
  • Preview: play your sequence. The Sequence strip has a new view, Preview, that plays the sequence as it stands: each frame's picture for as long as it lasts, the script's text on screen over it, and your recorded spoken lines with sound. The Sequence: approving a storyboard and working with its frames
  • A playhead on the Timeline. The Timeline shows where the Preview is, follows it while it plays, and clicking the ruler moves it. The Sequence: approving a storyboard and working with its frames
  • Activity: everything that happened in your production, in one list. The Book's Record chapter becomes Activity: every action by you, by CODA for you, by a collaborator, by a reviewer and by the app, newest first, each as one sentence, with how it ended (a refused action repeats the sentence you were shown). Activity: everything that happened in your production
  • CODA reads what happened. Before every reply she is shown what happened since her last one, and she answers "what did I do yesterday" or "who cast Mara" from the record, saying who did it, and says so when nothing is on record. Activity: everything that happened in your production
  • "Checked against the record". When something CODA said about a scene stops being true, the app writes a line in the chat saying what she said and what the production shows, in its own words, and CODA acknowledges it first. Activity: everything that happened in your production
  • A second check of CODA's replies, on for everyone. A cheap model (claude-haiku-5-5 unless the operator names another) reads each reply against the record and can point at one sentence the record contradicts; it cannot write anything itself, never acts, and is limited per day by plan. Activity: everything that happened in your production
  • Settings: how many recent actions CODA reads. *Recent actions CODA is shown in every turn* sets how many of the latest actions in the production CODA reads each turn (your plan sets the most; a workspace or a production can lower it). Settings
  • CODA no longer writes "I did not run that action" under a story shift or an explanation of a lock, counts every shot, and says a standing soft change in the person's words (v0.15.0; customers and operators): from the fourth live golden run. Asking CODA to do something to a take
  • CODA circles the takes, not the Bible's reference pictures, and no longer writes "I did not run that action" under a scene's mood (v0.15.0; customers and operators): from the fifth live golden run. Asking CODA to do something to a take
  • A cut's request offers no Accept in Requests (v0.15.0 E with F; customers): the button was refused by the server for a cut; the request now says a cut is delivered, from Files under Cuts. Cuts, picture lock and the Export Room

Version 0.14.2: Caddy from source, the cards in CODA's context, and the 0.14.1 findings

  • A "yes" answers what CODA last asked, not a card that happens to be waiting. When CODA asked "shall I put up scene 3's card?" and you said yes, she used to answer "your yes is noted; the click is what spends" about an older waiting card, and again on the next yes. Asking CODA to do something to a take
  • CODA no longer agrees with something the record contradicts. Told "we have the clip for this already" when the production shows no clip, she says what the record shows, kindly, in the same reply, and asks which is right, instead of agreeing and correcting herself a turn later. Asking CODA to do something to a take
  • A card says which scene it serves. The card line, CODA's record of cards and her "Done" lines now read "shot 5 (scene 2)", not "shot 5". Asking CODA to do something to a take
  • A clip in the Viewport's strip shows its first frame and says what it is. A clip used to show the word "video" in an empty box, with the same name as the still it came from; it now shows its first frame and a line under the name ("Clip · 3.0s", "Still · 1024×768"). Cancelling a take
  • CODA always knows which cards are waiting, dismissed or refused. The production's cards are now in front of her every turn, from the record and across every conversation, so "what did I leave open?" and "what's on the table?" are answered from the ledger however they are put. Asking CODA to do something to a take

Version 0.14.1: the clip gate, and CODA that tells what went wrong

  • CODA can explain every kind of failure, not only a refused clip. A take or run step that failed, a change the app would not save, a delete, lock or upload that was refused, a dropped connection and a panel that crashed are now on the record CODA reads, each with what it means, the usual causes, what you can do and when to pass it to the person who runs the system. When a take fails
  • The lock check is compact and says where it stands. The box that opens when you lock a script or the Bible is tighter, puts each row's detail beside its label, and takes a quiet colour from the verdict (green, amber or red). The production bible
  • CODA understands what you mean, not a keyword. She finds a scene's or a shot's take by its number ("start the clips with scene 1"), never asks you to say a product word such as "animate", treats dismiss, delete and cancel of a card as the same request, tries again when you ask for something refused earlier, and writes a clip's description in the positive. Asking CODA to do something to a take
  • A clip card that would be refused says so before you click. A waiting clip card now checks, live, whether a click would be refused (the shot's picture not checked yet, a character still being prepared, the production's daily spending cap) and says so on the card in plain words, with what to do first; Generate waits, and the note goes away by itself the moment the cause is gone. The continuity gate
  • The continuity check runs by itself. A new background pass (gate-scoring, every two minutes) checks the newest pictures of shots that have a cast, so a clip is no longer waiting on a command only an operator could run. The continuity gate
  • CODA can tell you what went wrong. The app now keeps a short record of what was refused or failed for you (thirty days, in the words you were shown, with what to do next), and CODA reads it every time you talk to her. When a take fails
  • A shot with no cast is no longer held back, and a refused clip says why. A scene with no character has nothing to check its picture against, so its clips go ahead. The continuity gate

Version 0.14.0: the Production Book, and the polish from the 0.13.1 live test

  • CODA says what became of every card, and remembers it. Dismissing a card, CODA withdrawing one, a take finishing, failing or being cancelled, and a click on a card that was already withdrawn each get one short line in the chat, written by the app and not by the model: *Dismissed the card for a still for Shot 1. Asking CODA to do something to a take
  • The Book: where a production stands, its plan and its lessons. A new Book tab in the right column shows what CODA knows about the production in seven chapters: the Situation (worked out by the app from the production, updated seconds after something changes), the Plan (proposed, next, doing, done, dropped; an item is only done when the production shows it is), Lessons (things to do or not do, which CODA proposes when you correct her and you accept, correct or retire), Decisions, Charter, the Record (what happened, by day and by who did it) and the Playbook. The Book: where your production stands, its plan and its lessons
  • CODA keeps hold of what was settled early in a long conversation. When a conversation outgrows what she reads at once, the app keeps a short record made from your messages, the cards and what she did, in view in place of the older messages, so a name or a colour from forty messages ago is still held and a value you changed is the changed one. The Book: where your production stands, its plan and its lessons
  • CODA gives links that open the exact place, uses the screen's own words, and checks what is wrong. Where CODA would tell you where to click she now gives a link that opens that scene, shot, Bible entry, take, card, setting or tab and pulses it, like Show me. CODA points at the screen: links, approvals and what is wrong
  • Create: make an image or a clip from words and pictures, and a character is held or there is no card. In Files, Create opens a panel beside your work: describe an image or a clip, add up to four pictures from your files or an upload, and say what each is for (Character, Style, Composition or Object); no script or shot is needed. Create an image or a clip from words and pictures
  • Every take says what it is, the storyboard shows the pick, and a frame can leave its scene. A take is a Draft (made, not chosen), Circled (the ★) or Final (accepted under a request), and says so on its thumbnail in the scene panel, the Viewport, History, Files and the storyboard; CODA uses the same three words and the Book's Situation counts them. Finals and requests
  • Locking shows what is still open, and CODA never locks. Lock version N on the Bible and Lock the script now open a check before anything is locked: a row each for what the lock cares about (the Bible's entries, pictures, rights and changes; the script's scenes, shots, approvals and open requests), each marked fine, open or stops it, with a link to what is open, then what the lock means, then one button, Lock anyway when something is open. The production bible
  • Deleting a shot with takes works, and loses nothing. Delete is always on the shot sheet. Writing a script
  • A Scripts page lists every script as a card. Title, format, draft or locked, version, scenes, approved scenes and when it changed, with Open, Duplicate (a new draft copy) and New script; two scripts with the same title are told apart. Writing a script
  • The script PDF has a title page and prints each scene's synopsis. The logline, genre and tone, format and target length, version, date and production; an outline from CODA is no longer a list of bare headings; Export says why it is unavailable. Writing a script
  • An approved scene looks approved in the Script tab, there is one Next, forms share one select, and the shot editor sits beside the chat. The scene list tints an approved scene (*Approved* / *Approved, then edited*); the Script header's Next chip is gone (the right column's stays, and says why it skips an earlier scene); every dropdown is drawn with the product's look; the shot editor is a side panel, so you can keep chatting with CODA while it is open. Writing a script
  • Switching CODA's follow-ups off no longer silences the line that says a card was approved. Before, with follow-ups at zero the approval line ("Making it now; I'll say when it's done.") was not sent either, so a person could be left waiting on a promise. Asking CODA to do something to a take
  • When you have already said yes in your own words, CODA no longer says it cannot approve. "ok this is approve, generate" is met with the card being yours to click (the click is what spends), not with a request to approve again. Asking CODA to do something to a take
  • The Sequence no longer promises music in a release that is out. The Sound tab, the + menu's Music item and the Sequence page said music and sound effects "arrive in v0.14.0"; they now say "in a later release". The Sequence: approving a storyboard and working with its frames

Version 0.13.0: requests and the trail, the Sequence, playbooks and settings, and a backup for CODA

  • Approving a card and dismissing it at the same moment can no longer both go through. The approval's record was written just after the take was made, so a Dismiss that landed in between closed a card that had already spent. Asking CODA to do something to a take
  • A locked script keeps its order when you Undo. Undo and Redo of a frame move were not stopped by a locked script (a same-scene one reordered the shots, a cross-scene one failed with a server error); they now say the script is locked and change nothing. Writing a script
  • A request's button says what accepting does. A take's request still says Accept as final; a change to the locked Bible or a script, and a frame move a locked script refused, say Accept this change; a storyboard version says Approve the storyboard, and once approved the line says clips are now made for the frames it covers instead of "the change was written". Finals and requests
  • Get a storyboard version approved, and ask for a change a locked script refused. Beside a saved version, Ask approval opens a request that a person with the approve right accepts; CODA can ask but never approves. The Sequence: approving a storyboard and working with its frames
  • The Sequence strip has its own height, menus, zoom, Sound tab and voice. Drag its top edge to resize it (it remembers), zoom the timeline, open a frame's menu (move to a scene, another take, add text in the script, ask CODA, remove an empty frame), and Add → Voice for a priced card per spoken line that is ready in the selected frame's scene. The Sequence: approving a storyboard and working with its frames
  • Choose how far CODA goes before it stops for you, and what it may do. Settings gains Autonomy (Ask every time, Plan first, Autopilot within the cap, and whether a run pauses after each stage) and What CODA may do: for every tool and every act, Never / Ask me / Without asking (only for free, undoable acts; anything that costs money, and locking, deleting or erasing, always wait for your click), and for every model, Allowed or Never. Settings
  • Type / for commands, and a new production opens on "What are you making?". /take (a quick take), /plan (a plan card, Studio and Enterprise), /final (propose the take on the stage as its final) and / with a playbook's name are listed in the message box's menu for your plan; a command is saved as you typed it and skips no rule. Welcome to Zymcos
  • The workspace works on a phone. Instead of "Desktop only for now", a phone (upright or turned sideways) shows one panel at a time with a bar of three: CODA, Workspace (Home, Script, Bible, Viewport and Files) and Details (the scene, History, Requests, Run). Welcome to Zymcos
  • Playbooks: a ready-made way of making a 30-second ad, a music video and five more. Ask CODA to start one by name ("start the 30-second ad playbook") and it asks the playbook's first questions one at a time, writes the answers toward the production's charter, and knows which stage you are at and what comes next. Playbooks
  • If CODA's usual model cannot answer, a backup model does. CODA's chat, script drafts and the documentation's question box each name a second model (Command A in production). Welcome to Zymcos
  • The documentation's question box is answered by Claude Haiku 5.5. The answer is still written only from the documentation sections found for the question and still lists the pages it used; one that cites none of them is still refused. Who handles your data
  • Share a saved storyboard version with a client for review. In the Sequence footer, Review beside a saved version makes a link a client can open without an account: they see that version's frames only, can leave a note on any frame or overall, and say Approve or Ask for changes (and change their mind). Sharing a storyboard for review
  • A Studio production changes the locked Bible and locked scripts through requests. In Studio, editing the pictures, rights or voice of an entry the current Bible lock names, taking the next lock, and unlocking a script are no longer direct: saving such an edit sends it as a request (the Requests tab and the stage show what would change, before and after), and someone who can approve accepts it, which writes the change (and takes the next Bible lock if asked) or re-locks and re-exports the script. Finals and requests
  • Write down what the production decided, and CODA works to it. Files gains a Decisions section under the nine folders: the production's charter (goal, audience, tone, deliverables, brand) and its decisions, each a short document (context, decision, alternatives, consequences) that can carry rules the checks read, such as an aspect ratio, a minimum resolution, the models allowed or never allowed, or a most a take may cost. Decisions and the charter
  • Runs propose finals; the Witness and the Requests tab watch them. When an autopilot run finishes making takes for a shot it opens a request for the best one (★, then 👍) and lists the others, so Use this take instead is one click; a run never accepts. Finals and requests
  • Ask CODA to propose a final, explain a check or write a request's summary. Say "propose this take as the final", "why did Continuity fail on request 3?" or "is this ready to accept?" and CODA opens the request on the Viewport, reads the checks aloud with the usual fix, or writes the summary. Finals and requests
  • Propose a take as a shot's final, see it beside the current one, and accept it. A new Requests tab in the right column lists the production's requests, each with how its eight checks came out; choosing one opens it on the Viewport with the current final and the proposed take side by side, the checks beneath, and Accept as final. Finals and requests
  • ★ is *circled*; a *final* is the take a person accepted for a shot. Circling a take is your keeper mark and no longer makes it the shot's final. Your files
  • A take can be proposed as a shot's final, checked, and accepted by a person. Behind the scenes only so far (the screens come in the next slices): a request for a take, its checks, an Accept that needs the *approve* right and a written reason for every check it is accepted past, Solo's one-click *Make final*, and the production's rules (Solo advises, Studio requires). Finals and requests
  • Eight checks judge a proposed final. Continuity, Matches the shot, Defects, Provenance, Rights, Model terms, Cost and Production decisions each read what the platform already knows about a take and answer pass, fail, pending, or *not measured* with the reason; not measured is never counted as a pass. Finals and requests
  • The record for requests, checks, rules and finals exists. A production can now keep a numbered request for a take or a change, the checks run on it, who accepted it and why, the rules it was judged under, and a shot's finals as a timeline; a person is named on it by a private reference, so erasing them later never rewrites it. Finals and requests
  • The tabs name the phases. Along the top, quiet labels sit over the tabs when the window is wide enough: Pre-production over Script and Bible, Production over the Viewport, with Home first and Files set apart after a thin rule; the Sequence's header says Post-production. Writing a script
  • The path's colours are the stage colours. In the Progress bar, in the Progress list and in the four small marks on each scene row, every stage (Script, Bible, Shots, Cast, Stills, Clips) is drawn in its own colour, the same everywhere, and how far it is shows in the shape: filled is done, half is under way, a ring has not begun, a dash is not yet applicable (it replaces the single family of green). Writing a script
  • The Bible's reference pictures use the same card and the same drag. A picture of an entry's reference pack is the card tile with its place, what shots do with it and Remove; dragging one now puts it *before* the picture you drop it on (it took that picture's place before), a *Last in the pack* box appears while you drag, and Move earlier / Move later still tell you when a picture is already at the end without losing your place. The production bible
  • Files rows and boards use the same card and the same drag. A file in the Files list is the row of the one card (a picture or an icon for its kind, its name, facts and the chosen outline), and a board's files are tiles. Your files
  • The History rail's versions are the same card. A version is the row: a thumbnail, then its number, name, ★ and marks, with who made it, when, the cost and "moved from" under it; the version on the stage has the brand outline instead of a tinted box, and an erased or withdrawn version is a plain row you cannot press. Every version of a take
  • Takes in the shot strips and the Viewport's history use the same card. A take in a shot's strip is the thumb, a row in the Viewport's history is the row: the picture, a *Still* or *Clip* tag, a ★ when it is circled, a warm outline when it is the shot's chosen take of its kind, and the brand outline for the one you are looking at (the chosen outline was green before). Writing a script
  • The navigator, the gallery and the Sequence follow the one grammar. Scenes in the navigator, tiles in the Gallery and frames in the Storyboard are the same card: a picture, a *Still* or *Clip* tag, a label, and a ★ with a warm outline when it is a chosen one, kept apart from the brand outline of the thing you are looking at. Writing a script
  • Download the storyboard as a PDF. PDF (top right of the Sequence) gives you a landscape A4 sheet, six frames a page, each with its picture, number, length and scene, and a footer with the production, the version and the date; each saved version has its own PDF, drawn as that version kept it. Writing a script
  • The timeline shows your script's text and spoken lines. Under the pictures, a Text lane shows the script's on-screen text, supers and lower thirds over their scene, and a Voice lane shows its spoken lines from the scene's start: solid when spoken, dashed while waiting for speech, outlined when it cannot be spoken yet (point at it for why). Writing a script
  • Ask CODA to swap two frames, remove one, save the storyboard as a version, or present it. "Remove frame 3" deletes the frame's shot when it holds no takes (takes are never deleted, so a frame with one stays and CODA says why). Writing a script
  • Ask CODA to delete an empty bible entry or folder and it does. "Delete the prop Mug" deletes the entry when it holds no pictures, rights or voice, and "delete the folder Picks" deletes a folder with nothing in it; CODA says so once, and the Bible selection clears. The production bible
  • Present the storyboard. Present shows the sequence full screen as an animatic, each frame's picture held for its length with its scene underneath; Space plays and pauses, arrows step, Escape leaves. Writing a script
  • Save the storyboard as a version. Save version keeps the sequence as it stands, with every frame's scene, length and picture and the Bible version it was made on, under a name or a number (*Storyboard v2*). Writing a script
  • Ask CODA to move a frame or set its length. "Move frame 3 before frame 1", "move frame 1 into scene 2", "make frame 2 five seconds long" and "undo that" are done when you ask and name the frame, and CODA says what it did to the order. Writing a script
  • Move frames and set their lengths from the Sequence, with Undo. Drag a storyboard card, or select it and use Alt+Left and Alt+Right (or Earlier and Later), to move it; moving across a scene's edge puts its shot in the other scene, so the script and the sequence never disagree. Writing a script
  • The bottom strip is now the Sequence. It shows your shots as frames in the order your script reads: collapsed, one line (frames, length, how many have a still); expanded, a Storyboard of cards grouped by scene with their pictures and lengths, and a Timeline with the frames along a ruler. Writing a script
  • Ask CODA to delete an empty shot and it does. "Delete shot 3" deletes it when it has no takes, and CODA says so once. Writing a script
  • A step CODA got right on the second try shows no warning. When CODA named a shot that was not there, was told so and tried again correctly, the transcript used to show "CODA corrected a step." over the good card. Writing a script
  • You choose how you work. Settings → How you work sets the order Progress and CODA recommend in: every scene's still before any clip (the default), a scene's still and clip before the next scene, or clips straight from the script. Settings
  • A waiting card can be dismissed. Dismiss on a generation card or a run plan closes it: it spends nothing, reads *Withdrawn · nothing was spent* and cannot be approved afterwards, even from an old tab. Asking CODA to do something to a take
  • Progress follows the scene you are on, and counts every scene. The path is now six stages (Script, Bible, Shots, Cast, Stills, Clips; the old Takes stage is split), each counted over scenes: *A still in 1 of 3 scenes*. Writing a script
  • Every scene shows its picture, and the Script page has a Gallery. The scene list carries a small picture of each scene (its chosen still, else the first take it has, else an empty frame), and a Gallery button shows every scene as one tile with its chosen still and chosen clip, its counts and the takes that are in no shot. Writing a script
  • Ask CODA to lock the Bible and it does. "ok go ahead and lock version 1" used to get a card and "I can't press it for you". The production bible
  • The screen follows what CODA does. When CODA makes or changes something, the app goes there: the Bible on the entry, the Script on the scene or shot, Files on the folder, the way "Show me" does. Welcome to Zymcos
  • Ask CODA to change a reference pack and it does. "add that picture to Mara's references", "take out the second picture" and "make the side view her main reference" are done at once, with the note that the rights need affirming again and (for a rearrangement) an Undo. The production bible
  • A sentence about earlier work no longer earns "I did not run that action". CODA's note that something it said was not done was added under a scene that really had been added, because the reply also mentioned "the outline I queued earlier". Asking CODA to do something to a take
  • A price reads the same everywhere. The approval card printed $0.025000 where History said $0.03 for the same take. Your first shot
  • The card for adding a picture to references says what it does. A picture on no shot was quoted as "Add 'Unassigned take' to Podcast Gues…" over a button that said "Make this change". The production bible
  • Script details labels sit beside the first line of their value, the progress line always counts of five, and the narrow Scene picker stops looking disabled. A long logline had its label at its foot; "0 of 4 done" became "of 5" when Cast became applicable (a stage that is not applicable yet is now greyed and says "not yet"); the Scene picker wore the placeholder's colour once a scene was chosen. Writing a script
  • One click, one acknowledgement. Approving a take used to get two replies that each named the next step, one at the click and one when the take finished. Welcome to Zymcos

Version 0.12.0: the Script page, CODA on Sonnet, and the 0.11.2 findings

  • One clip is a card on every plan. On a plan without autopilot runs, asking CODA for a single clip with "just do the whole thing" got "autopilot runs come with Studio and Enterprise", or a question about how to make it. Running a brief on autopilot
  • Asking CODA to write a script from nothing now starts the draft. CODA would create the script and then stop before starting the draft you asked for, saying it had already made that request. Writing a script
  • CODA reads what your scenes say. When CODA read your script it saw each scene's heading and how many elements it had, never the words, so asked for a shot for a scene it had to ask you what happens in it. Writing a script
  • CODA no longer tells you what a picture shows when it hasn't seen it. It says what it asked for instead, and if it does describe a picture's contents the reply adds that it hasn't seen the picture. Welcome to Zymcos
  • A shot CODA makes is in the scene it is for, and says so. CODA could make a shot in no scene and still tell you it was in one. Writing a script
  • CODA's next step matches the one on the Script tab, or it says it is suggesting another. It could name a different next step from the strip's without saying so; such a reply is now corrected with the strip's step. Writing a script
  • A step CODA gets wrong no longer uses up its turn. When CODA makes a mistake it can correct itself, such as naming a script kind that doesn't exist, the correction no longer counts as one of the three actions a reply can take, so asking it to start a script and write its scenes gets that done. Writing a script
  • A clip made from a still no longer fails because of how the still was named. CODA can now name one of your pictures as the start of a clip by the picture itself, and a value that is not a web address is refused before a card is shown, so it can never reach the generation service. When a take fails
  • The Script page gives the scenes the room. A two-row header says what the script is (title, status, format, length) and what to do (the next step, Outline with CODA, Co-write, Board and More: the brief, adding pages, the breakdown, the table read, revisions, lock and unlock, export); what a script with no scenes cannot do yet appears with its first scene. Writing a script
  • CODA's activity lines speak plainly. A line now says what CODA did in your words (*Added scene 1, EXT. Welcome to Zymcos
  • CODA asks before it changes a Bible entry's references. Adding a picture to an entry, or taking pictures out or reordering them, is now a card you press, showing the references before and after and what happens to the entry's rights. Asking CODA to do something to a take

Version 0.11.0: CODA that talks, the whole script chapter, folders and settings

  • CODA answers when you act on its cards. When you press a button on one of CODA's cards (lock the Bible, affirm rights, change a Bible entry's references, approve a take or a plan, approve or reject a draft), CODA replies by itself with what happened and the next step, after any reply it was still writing. Welcome to Zymcos
  • Who handles your data. A page naming the companies that process your content on Zymcos's behalf (Anthropic for CODA's conversation from this release, Cohere for drafting and the documentation's answers, fal for takes, DigitalOcean for storage), what each sees and what each has committed to. Who handles your data
  • Stills are priced, and CODA can make a clip from words alone. An image take now shows a real price (fal bills $0.025 for each megapixel, rounded up; a default still is one megapixel), so a plan that makes stills can start. Running a brief on autopilot
  • CODA talks to you, not just takes orders. Ask in your own words — "something for my coffee brand", "make it better" — and CODA says how it read you, asks one short question when it cannot tell what would change the cost, and otherwise picks something sensible and tells you what it picked. Welcome to Zymcos
  • Ask CODA how something works. "How do I cancel a take that is still generating?" — CODA looks it up in the published documentation, answers in its own words and names the page it used. Asking the docs a question
  • Settings. The gear in the top bar opens Settings: your spending limits and defaults, each with the value in force, why it is that value, and where you can change it. Settings
  • Your own folders in Files. Under the nine storage folders (which still say where each file is stored, and never change) there is now Folders: make them, nest them five levels deep, rename and move them, and drag files into them, or use Move to… on a file (or on several you tick) with the keyboard. Your files
  • Ask CODA to organise your files. "Make a folder called Client picks", "put this in the Client folder", "rename Internal to Behind the scenes", "what is in Client?": CODA does these at once, as the same controls would, and says so. Your files
  • Views and search in Files. Views — Unfiled, Recent, Circled ★ and Withdrawn — sit under Folders, and a search box above the list finds files by title or by the prompt that made them, inside whatever you have open (a folder, a view, or everything). Your files
  • Download a folder as a zip. Download as zip gives you a folder and everything under it with the same structure. Your files
  • Upload into a folder, and have a run file its results. With one of your folders open, Upload files what you add straight into it; with anything else open it arrives Unfiled, as before. Your files
  • CODA only casts who you named. Asking CODA to "put her in shot 3" now gets a question, "which entry do you mean?", instead of a guess. Writing a script
  • Live co-writing (off by default). Where a deployment enables it, a person who may curate a script can turn on Co-write for it, invite members of their workspace as editors, commenters or viewers, and type in the same scenes at the same time, each seeing the others' words as they are typed and which scenes others have open. Writing a script
  • Hear the script: a table read. Under the title, Table read lists every dialogue and voice-over line by scene against the speech made for it, with the ★ take standing for each, a player that reads them in order, and a Speak button on a line with none (a priced card in CODA that your click approves; nothing is spent by pressing Speak). Writing a script
  • Review: comments and scene approvals. Each scene has a Comments button (notes on the scene or one of its elements, answers, and resolving a thread) and an Approve button that records you looked at the scene as it reads now. Writing a script
  • An estimate of what it would cost to make the script. The scene board gives each scene's generation cost for one pass (a still and the video of each shot, at draft or final), worked out the way the ledger prices a generation, and compares the total with the cap CODA proposes for a run. Writing a script
  • A locked screenplay is a production script. Locking a screenplay freezes its scene numbers and tracks every later change instead of refusing it: the first change starts the blue revision, Revisions shows the sets and what each changed, and Start the next revision begins pink, yellow and on through the industry's colours. Writing a script
  • Final Draft and PDF. Import a Final Draft .fdx file (previewed first, like Fountain) and export the script as .fdx or as a PDF in the industry's page layout, with scene numbers in both margins and revised pages on their colour for a script in production. Writing a script
  • The script says when what was made from it is out of date. When you change a scene's elements or heading, its shots and takes made for the earlier words are marked "Script changed since this was made" on the shot, in the scene board and to CODA. Writing a script
  • A scene board. Under the script's title, Scene board shows every scene against what it has (what is written, the entries it names and whether they are locked, its shots and who is cast, its takes, video and starred ones) and what it is missing, in words. Writing a script
  • A script feeds the Bible and the shots, as cards you commit from. Under the title, Breakdown shows the characters and places the script names (matched to your Bible, with the ones to add ticked) and the shots each scene might be broken into, with lengths inside what a video model takes. Writing a script
  • Start a script from an idea. A production with no script opens on three ways in: write it yourself, develop it with CODA (your idea and as much of a brief as you have, and CODA drafts an outline for you to approve), or bring one you already have. Writing a script
  • CODA drafts, you decide. Ask CODA for an outline, or for one scene, from the Script tab or in chat. Writing a script
  • A script now has a format. A screenplay, commercial, live selling session, music video, brand film, social short, event or immersive script each offers the elements it uses (parentheticals and sections for a screenplay; voice-over, supers, music, shots and a call to action for a commercial) and reads the way it should: one page column, or picture beside sound. Writing a script
  • Bring a script in, take it out. Paste or upload a script as Fountain (the format Final Draft, Highland, Fade In, Celtx and WriterDuet share) or plain text, see what was found before anything is written, and add it to the script as one edit. Writing a script
  • A take you generate yourself now goes on the stage. Before, once you had clicked a take (or a card's "Show on the stage") the Viewport stayed on it and a new image landed only in the strip. Live updates
  • The Script tab says where your production is and what to do next. A strip at its head reads, for example, "Next: Lock Maya. Writing a script
  • You can see how each take matches the locked pictures. A take in a shot with a cast shows its marks under the picture in the Viewport and under the take on the stage in the History tab: for each cast entry, the check where it did worst ("Looks like 0.81 · Strongest of 3 takes"), with the other checks one click away. The continuity gate
  • You can cast a character into a shot, and CODA can. The shot editor has a Cast section: one row for each entry of the Bible, each saying where it stands for this shot (in it, in it at an older version, castable, not locked yet, no rights, or rights withdrawn), with Cast, Update (a swap in one step, never automatic) and Take out, an Undo after each, and a line saying how many pictures the shot will be held to and why any did not travel. The production bible
  • Shots have an editor, and CODA can use it. Each shot in the Script tab has an Edit button that opens a sheet for its length, framing, camera move (with its amount in its own unit), light, aspect ratio, resolution, whether anyone speaks and whether a character must look the same. Writing a script
  • Fewer "the text model is unavailable" replies, and no false "I did not run that action" under an edit that ran. When the text model answers that it produced no response, CODA asks it once more before giving up. Welcome to Zymcos
  • CODA never shows a half-written tool call, and says why the model refused a request. A reply that begins as a JSON object missing its tool field is corrected or replaced, never shown; a refusal from the text model (a 4xx) is logged with the provider's own reason instead of only its status. Welcome to Zymcos
  • CODA no longer says it will generate things, and a limit set to your operator's figure reads as yours. After a card, CODA's own words are refused if they promise to make or start the thing itself ("I'll proceed with generating…"): only your click does. Settings
  • A documentation lookup no longer floods the chat. When CODA looks up how something works, the conversation shows one line ("Looked up in the documentation: Cancelling a take.") and keeps the passages in the row's expansion; a one-line result, such as a refusal's reason, is still shown whole. Asking the docs a question
  • CODA no longer shows a tool call, or promises something it did not do. A how-do-I question could come back as a made-up {"tool": "cancel"…} line; a request to lower a limit could come back as "I'll lower it" with no card. Welcome to Zymcos
  • CODA now says correctly what an unpriced image can and cannot do. A single image card with no recorded price can still be approved (it counts at a cautious guess against your daily cap); a plan that contains one cannot start. Spending limits
  • A take the provider refused no longer spins forever. When the provider accepts a take and then cannot run it (for example, it cannot fetch a picture it was given), the take now fails once, with the usual plain sentence, and its reserved cost is released. When a take fails
  • A plan to animate a picture no longer fails after you approve it. CODA's plan now says which role the picture plays (the one a clip starts from), and a plan whose pictures its model could never accept is refused when it is proposed, with the fix, instead of failing every step once approved. Running a brief on autopilot
  • CODA tidies a plan it wrote slightly wrong instead of failing. A steer written inside a step, a clip length in the wrong place, or a field a plan has no use for are put right and said ("I tidied the plan as written: …"), and the plan card is made. Running a brief on autopilot
  • A plan CODA wrote wrongly says how to fix it. When a plan fails its check because a steer was put inside a step's request (it belongs beside it, and only after a review), CODA is now told that, so its next call can be right instead of giving up with "please try again". Running a brief on autopilot
  • A folder CODA makes shows up in Files at once. Asked to "make a folder called Client picks", CODA made it, but the Folders list only caught up when the background relay got to it (or on a reload). Your files
  • CODA no longer says a card is up when it has not put one up, and settings talk is plainer. Asked to raise a limit above what your operator allows, CODA once answered that a card was above when no card existed. Settings
  • The "Reading this as: …" line now appears with a plan card, as it already did with a single take. It was written for the first and silently dropped for the second, so a plan card arrived without CODA's reading of the request. Running a brief on autopilot
  • CODA no longer leaves a picture request hanging after it asked a question. After "help me create a lighthouse", CODA's question, and "recommend", the model wrote its proposal as a code block, said it was waiting for approval and quoted a price it had never been given; nothing ran, three times out of three. Asking CODA to do something to a take
  • CODA's "how I'm reading this" line now arrives with the card, not instead of it. Asked to build something on autopilot, CODA was told both to say how it read the request and that nothing may come before or after a plan card, so it wrote the reading, then the plan as text, and no card appeared. Running a brief on autopilot
  • CODA no longer shows you raw JSON when its own tool call is malformed. A reply that began as a call but was not valid JSON was shown as text, and nothing ran. Welcome to Zymcos
  • CODA's claims are checked against what it did. A message that says an action was done ("I've renamed her", "I've created Sarah") when no such action ran now ends with Nothing was changed: I did not run that action.; a request CODA wrote behind other words, so that nothing ran, is asked for once more and otherwise answered with I could not carry that out, so nothing was changed. Asking CODA to do something to a take

Version 0.9.5: safe to leave running: one CODA, autopilot runs, and a docs site that can be found

  • The Bible can be locked from its tab, in two steps. A strip across the top says Version 3 locked 2 October (or Not locked yet) with a Lock version 4 button and History, a list of every lock with its date and how many entries it took. The production bible
  • The Bible tab edits an entry's reference pack: an ordered row of pictures, the first four marked as the ones shots use, reordered by drag or by Move earlier and Move later, saved as one draft. Each picture says Used in shots (the first four usable ones) or Kept, not used; a withdrawn, an erased or a missing reference is drawn as it is (Withdrawn: not used in shots, Erased, Not found) with its Remove, never dropped. The production bible
  • References come from the production's files or an upload, in one dialog. Add references opens From your files (images only, withdrawn and erased left out, many at a time, a filter over the pictures loaded so far, stopping at the room the pack has) and Upload (each file in turn, its own state, and a plain sentence for a HEIC photo, a file that is too large, a full workspace or too many uploads). The production bible
  • A consent can cite its evidence file. The rights form's Evidence (optional) opens the same dialog for one file, shows its name with a Clear, and records it with the consent; a file already on a consent is still kept when the person affirms again. The production bible
  • CODA's arrange_references leaves a line in the transcript with an Undo. It says whether pictures were taken out, a different one was made the main reference or the order changed, says the rights were cleared only when they were, and Undo puts the earlier pictures back on a revision read just then (and says it clears the rights again). The production bible
  • Add to Bible says the pack's own refusals and does not offer a full pack. Not an image, withdrawn, erased and too many now read in the Bible's sentences instead of a generic "fault on our side", and an entry holding twelve pictures is marked full in the dialog. The production bible
  • A reference pack now refuses what cannot condition a generation, for every caller: a file that is not a still, a withdrawn or erased file being added, and a thirteenth picture. The API answers 422 with a stable reason (reference_not_image, reference_withdrawn, reference_erased, pack_too_large) and the offending asset_ids; the same rules bind CODA's Add to Bible and the new arrange tool. The production bible
  • CODA can take pictures out of a reference pack and put them in a new order (manage_entity arrange_references), and can never add one or keep the rights. Free and reversible, so it is done at once; it calls the pack editor's own service call with the pack revision it has just read, clears the entity's rights as any pack edit does (and says so, and that the person affirms them again in the Bible), refuses a picture that is not already in the pack, and records the previous order for Undo. The production bible
  • The Bible tab: characters, places, props and looks, and the right to use them. A new tab between Script and Viewport lists the production's characters, places, props and looks, each with two small labels read from the record (where its lock is: "Not locked yet", "Locked as version 2", "Edited since version 2"; and where its rights are: "Rights not set", one of four plain choices, or "Rights withdrawn"). The production bible
  • CODA's Bible rows: Undo, a delete card and a rights draft. Asking CODA to make or rename a character is one line with an Undo (a made entry is deleted again, a rename is put back); deleting is a confirmation card that deletes nothing until you click it; and "she signed a release" becomes a rights draft in your words whose one button, Open in the Bible, selects the entry and fills the form. The production bible
  • Add to Bible points at the Bible tab. With nothing in the Bible the dialog sends you to the tab to make something first, and after adding a still the note offers Open in the Bible on that entry; the dialog and CODA no longer say entities are made in the Book. Your files
  • A take can be made for several shots at once from a card. A proposal now names the shots it is a take of as a list (up to 32), and the card says which shots before you spend ("Will be a take of shots 2, 3."). Every version of a take
  • Cancel a take. The take being made in the Viewport has a Cancel button. Cancelling a take
  • Phones show "Desktop only for now" (I1-1). Upright or sideways, a phone gets one page saying the workspace needs a computer and nothing is lost, instead of a squeezed workspace under a tab bar that did nothing. Welcome to Zymcos
  • The review grid's own read. GET /api/v1/projects/{id}/assets?checkpoint=<id> lists exactly the takes a run's checkpoint shows for review, with the list's usual filters, count and paging. Running a brief on autopilot
  • Video is priced before you click. A video card says what its price is for, such as "about $1.70 for 15 s", and the seconds on the card are the seconds the model is asked for and the seconds you are charged for. Spending limits
  • History says where a take has been. A take moved between shots shows "moved from Shot 4". Your files
  • The docs can be found by search engines and by AI answers. Every page of docs.zymcos.com now has its own title, description and canonical address, opens with an "In short" answer, shows the release it applies to and when it was last reviewed, and carries structured data describing it. Asking the docs a question
  • The docs catch-up, part one: pages for what a customer meets every day New pages on signing in and out (sessions, the 12-hour cap, an ended session, and "Zymcos is temporarily unavailable" read as an outage, never a sign-out), on live updates (what refreshes by itself, who sees a take land, and the limits), and on "Too many requests" (a refused request did nothing, and whose limit it was). Signing in and out
  • Storage and the quota, documented. What is counted, that identical files are counted once, and that a quota refuses a new take before any money is spent and never the copy of one already paid for. Storage and the storage quota
  • Support requests, documented as they are. What a request holds and how it moves from open to closed. Support requests
  • C2PA on copied files, documented. Every copy is checked for a manifest; the check only reads, never blocks or alters the copy, and its verdict is recorded but not shown in the app. Content Credentials on your files
  • A public glossary and "Your first shot". The glossary defines the words a filmmaker meets in the workspace, each pointing at its page. Glossary
  • Support pages for autopilot runs, tiers and entitlements, and how CODA reads a request. How a run works, its statuses, the kill switch and the journal; where a tier lives (on the membership, not the workspace) and how an operator changes it; and which parts of CODA's reading are steering and which are enforced. Running a brief on autopilot
  • Press / on any docs page to jump to the question box, with a switch to turn it off. The shortcut does nothing while you are typing in a field or holding Ctrl, Meta or Alt. Asking the docs a question
  • Screenshots in the docs come from Storybook, and cannot go stale quietly. A page shows a screenshot by naming a story (::figure{story="…" alt="…"}); make docs-figures captures the stories tagged docs-figure in the pinned container, in both colour schemes, and records the baseline each was captured from. Your first shot
  • A take made for several shots is named by all of them, and pictures made together say which they are. Files, the Viewport, History, the manifests and CODA now agree: Shot 4 · take 2, Shots 2–3 · take 1 for a take made across shots (it was "Unassigned take", and sat in the Unassigned strip of the Script tab), and Shot 2 · take 2 · 3 of 4 when one request made four pictures (they all had the same name). Your files
  • Editing a pack without saying which version you read is a 428, and If-Match is accepted. PATCH /entities/{id} used to answer 422 when a pack, voice or rights edit omitted expected_pack_revision; it now answers 428 Precondition Required with a body that names the field and says where the current revision is read, and counts the refusal. The production bible
  • The app says one name. The Home tab's heading reads "Welcome to Zymcos", the timeline bar's logo and its link label read "Zymcos", and the message shown when your organisation's installation does not permit everything Zymcos needs names the product by its name. Welcome to Zymcos
  • Stopping an autopilot run cancels the takes in flight instead of waiting for them, so a stop takes effect in seconds. Running a brief on autopilot
  • A take a stop cancelled reads Cancelled in the Run tab, not Failed. Its step says what it may still cost once, in the platform's own sentence, instead of a red "Failed" with the error code repeated in front of it. Cancelling a take
  • Approving a review with nothing marked means "none". Until now an empty choice let the server pick whatever was marked ★ or 👍 when the approval arrived, so a take marked a moment later could change what the next checkpoint built on. Running a brief on autopilot
  • The review grid shows exactly what the approval accepts. The Viewport's review now reads the checkpoint's takes from the server, every page of them, instead of filtering the takes the Viewport had loaded; it says so while it reads, and offers no "Load more" under a review. Running a brief on autopilot
  • A run's step refused before spending says why, as a take would. A step whose model can no longer take it, whose prompt is missing or not accepted, or whose reference the model cannot use now records the same code as the generation route, with a sentence, instead of a generic code and a raw record. Running a brief on autopilot
  • One CODA, no modes. The Forge / Flow / Relax switch is gone from the top bar. Welcome to Zymcos
  • Relax is now "autopilot runs". The Run tab, the plan card and the docs say so, and the run's recorded actor is agent:autopilot. Running a brief on autopilot
  • The session's name sits under the message box, not in CODA's header. Beside the wordmark it read as part of the product's name. Welcome to Zymcos
  • The proposal card's foot is one status line and at most one button. It reads "Generated · $0.42" or "running — 40% · unpriced" in place of separate badges and rows; in a narrow CODA "Unpriced" is one word (the sentence stays on hover) and the button stays on one line. Your files
  • Existing docs pages now match what shipped The customer pages say Viewport where they said Gallery, stop promising a search link and a support form, list History instead of promising it, and say that a take can be dragged onto a shot. Welcome to Zymcos
  • Editing an entity's reference pack, voice or rights now says which version you read, and a stale edit is refused instead of overwriting. Each entity carries a pack_revision; an edit of reference_asset_ids, voice or a rights field must send expected_pack_revision, and if someone else changed the pack first the answer is a 409 stale_pack showing the pack as it now stands (a request without the revision is a 422). The production bible
  • The Bible's "Rights not set" chip is neutral, and Affirm rights waits for a change. A missing rights basis is not a fault (a draft can wait for its paperwork), so the chip is plain grey with an unfilled shield and the warning colour is kept for "Rights withdrawn" and "Edited since version N". The production bible
  • Branch from here and Edit no longer drop a take's other shots. A branch of a take made across two shots proposed only the first, so the new take was filed under one shot; Variations and Animate proposed none, so the card could neither price the shots' length nor condition on their characters. Every version of a take
  • A token the API refuses a minute early no longer shows as an error. The server that sits between the browser and the API planned each sign-in token's life by the provider's stated 900 seconds, but the API enforces the token's own expiry, so for the last 30 to 60 seconds of every token (about every 14 minutes) requests were refused and the person saw "cannot load" or "That did not go through". Signing in and out
  • A failed take never shows our provider's name or billing page (audit 0004 I1-4). The card says what happened in our own words — *This take did not start* or *This take failed*, one sentence under it, whether trying again can help, and a short code to quote to support. When a take fails
  • The bible copy says where the bible is today (I1-3, I1-13). Add to Bible no longer sends you to the Book to make an entity or re-affirm its rights — the Book has no screen for either yet; the dialog, its note and CODA's reply say it is done through the API for now. The production bible
  • Sending works after switching CODA session mid-reply (B2-1), and a dropped reply says so (B2-4): a notice under the conversation says the connection dropped and whether CODA had your message. Welcome to Zymcos
  • Use as reference names the still's role so a clip can be proposed from the button: the still becomes the clip's first frame, said in the dialog and on the card. Your files
  • Each production has a daily spending limit on clicked takes Clicks spend at most $25 per production in any rolling 24 hours, unless your workspace sets another figure. Spending limits
  • Moving a take keeps its continuity scores Dragging a take to another shot, or asking CODA to, used to delete the scores the gate had measured for it. The continuity gate
  • Two people committing a character to one shot at once can no longer bind two versions of it. One commitment lands and the other is refused with what the shot now holds. The continuity gate
  • The docs' ask box cannot be run up by a bot. It refuses crawlers and requests from other sites, limits each address (an IPv6 /64 counts as one), and stops at a daily spend ceiling of 10 USD, counted as 244 asks from the worst-case cost of one ask, with a warning at 80%. Asking the docs a question
  • Autopilot runs are a Studio and Enterprise entitlement, enforced. The tier catalog's relax_mode flag, which nothing read, is now autopilot_runs, checked when a run is created: another plan is refused with a reason the plan card shows, and CODA does not offer it a plan. Running a brief on autopilot
  • A landscape picture fills the stage's width, however narrow the room above it. With CODA open and the right column collapsed the stage is wide and short, and the picture was squeezed to the stage's height and centred with empty bars either side. Your files
  • Redis is a required, bounded, authenticated platform dependency. The backend refuses to boot outside development without REDIS_URL, and no longer falls back to a localhost address. Welcome to Zymcos
  • An outage no longer looks like being signed out. When the session service is down, Zymcos now says it is temporarily unavailable, keeps you on the page you were on, and comes back by itself when the service does. Welcome to Zymcos