# Welcome to Zymcos

> In short: Zymcos 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.

Applies to: v0.9 · Last reviewed: 2026-11-02 · Canonical: https://docs.zymcos.com/product/getting-started/

Zymcos by Zynth is an AI creative operations platform: one workspace where creative work is
generated, reviewed and delivered, with a professional production process built in rather than
bolted on.

> **Zymcos is in active development and is not yet generally available.** This documentation
> grows alongside the product — pages appear here as the features they describe become real.

**On a phone** — held upright or turned sideways — the workspace shows one panel at a time with
a bar of three at the foot: **CODA** (the conversation), **Workspace** (Home, Script, Bible,
Viewport and Files) and **Details** (the scene, History, Requests and Run). Switching keeps your
place: a half-typed message and a reply still arriving are still there when you come back. The
Sequence at the foot of the desktop workspace is not on a phone; open the same production on a
computer for it.

## One CODA that reads what you ask

There is no mode to pick. You tell CODA — the built-in creative assistant — what you want, and it
works the way the request calls for:

- **A quick take.** "Make me an image of a lighthouse at dusk." CODA proposes that one image,
  with its price, on a card. Nothing is made until you approve it.
- **A production.** "Let's make a 30-second ad for my coffee brand." CODA starts from the
  script — offering to draft it with you — and then the shots, proposing each generation on a
  card as you go.
- **An autopilot run.** "Build the whole thing for me, here's $20." CODA proposes a plan: the
  generations it would make, in order, each priced, under a spending cap. You approve the plan
  and the cap once, and it runs. CODA only ever *offers* a run — it never starts one on its own.
  Autopilot runs come with the Studio and Enterprise plans.
  [Running a brief on autopilot](https://docs.zymcos.com/product/running-a-brief/) walks through it.

You do not have to be precise. Say it the way you would to a colleague — "something for my coffee
brand", "make it better" — and CODA says how it read you. If one thing would change the cost or
the result and it cannot tell which you mean, it asks one short question, usually with a couple of
options; otherwise it picks something sensible, tells you what it picked and gets on with it. Tell
it to decide everything and it will: a first concept of its own, cheap and at draft quality, on a
card you can approve or send back. After
it prepares something, it tells you in its own words what it made and what it assumed, and suggests
what to do next. If you ask for something that cannot be done here, it says so plainly and offers the closest
thing that can. A short clip from words alone is one priced card, and so is a still.

Before anything big, CODA says in a line how it is reading your request, so you can correct it.
Whichever way you work, the rules on spending are the same: nothing is generated or paid for
without your click, and a run needs its plan and cap approved. Everything you make is kept with
its full recipe, so moving from a quick take into a production, or picking a run's results up by
hand, never loses your work.

## Your productions

Everything you make lives inside a **production** — one film, spot or piece, with its own script,
bible and conversations with CODA. The first thing Zymcos asks a new workspace for is a
production's name; there is no default.

The production you are working in is shown at the left of the top bar. Click it (or press **⌘K** / **Ctrl+K**) to switch to another, to rename the current one,
or to start a new one. Every panel — CODA, the script, the Viewport — follows that choice, and the
page address carries it, so a reloaded or shared link opens on the same production.

The address also carries **what you are looking at**. Choose a version in the Viewport, or put a
file on the stage from Files, and the address updates; copy it and the link opens on that very
version. The browser's Back and Forward move through what you looked at. A link to a version
that is no longer in the list (older than the history loaded so far, or withdrawn since) says
so, and offers the latest, rather than quietly showing you a different one.

## The right column: History, Run and Pulse

The column to the right of the stage holds its modules as tabs: **History**, where every
version of the asset on the stage is listed (see [Every version of a take](https://docs.zymcos.com/product/version-history/)), **Book**, where the production stands, with its plan,
decisions, charter and activity (see [The production Book](https://docs.zymcos.com/product/the-production-book/)), **Requests**, where a take
proposed as a final and any change waiting for a person are listed (see [Finals and requests](https://docs.zymcos.com/product/finals-and-requests/)),
**Run**, where your production's autopilot runs are approved, reviewed and
stopped, and **Pulse**, the collaboration product, which reads "not connected" until it is. While the Script tab is
open a first tab, **Scene**, shows the scene you are in. Opening a module from the collapsed rail expands the column; closing it again
collapses the column only if that is how it was opened, so a layout you chose stays yours.

When the column is too narrow for every tab, the names turn into icons first. If the icons still do not fit, the least urgent tabs move into **More**, the three dots at the end of the tabs, which lists them by name. **Requests**, where your own action waits, is the last to move, and **Pulse** never does. Nothing is lost: every tab is still one choice away.

Renaming changes the label only. Nothing that refers to a production — its sessions, its shots,
its assets — is affected by its name.

## Talking to CODA

CODA's replies render as formatted text — headings, lists, dialogue and shot tables read as they
were written. Hover a message for its time and its actions:

- **Copy** any message.
- **Edit and resend** one of yours. This sends a *new* message; the original stays in the
  conversation, marked *Edited*, so the record of what was asked is never rewritten.
- **Regenerate** a reply, or **Try again** after CODA could not answer. The new answer is added
  below; the earlier one folds under *Earlier answer* rather than disappearing.

Type **`/`** in the message box for the commands:

- **`/take`** — a quick take: one picture, clip or line on a card, from what you type next.
- **`/plan`** — a plan card for what you type next, with each take priced and a cap (Studio and Enterprise).
- **`/final`** — propose the take on the stage as its shot's final. Accepting it is yours.
- **`/` and a playbook's name**, for example `/ad-30s` — follow that [playbook](https://docs.zymcos.com/product/playbooks/).

A command is just your message, typed: it is saved as you typed it, it asks for nothing the usual way would not, and a card still needs your click.

A line beginning with a wrench is something CODA *did* to your production, in plain words: *Added
scene 1, EXT. TOKYO STREET – NIGHT (RAIN)*. When CODA tried something that couldn't be done, the
line says so in a sentence meant for you (*Every script here is locked, and a locked script takes no
draft.*); when it corrected a step of its own, the line just says *CODA corrected a step.* Dates and
times everywhere are shown in your own time zone.

If CODA's usual model cannot answer for a moment, a second model answers instead, and a quiet line
under the reply says so: *Answered by our backup model while the main one is unavailable.* It reads
your request the same way and asks you the same things, though it can be a little quicker to act on
a vague request, so check that a card says what you meant. It only takes over before CODA has done
anything in that message: if CODA had already made a change when the problem hit, the message
stops there and you can send it again.

When CODA changes something, the screen goes there: the Bible on the entry it made or changed, the Script on
the scene or shot it worked on, Files on the folder. It never moves while you are typing (it waits until you
stop) and it never moves for something CODA only read or only offered. The switch under the message box,
**Following CODA**, turns it off for you.

When you press a button on one of CODA's cards (lock the Bible, affirm rights, approve a take or a
plan, approve a draft), CODA replies by itself with what happened and the next step, so you don't
have to tell it. When you approve a take, the reply is one short line, *Making it now; I'll say when
it's done*, and the next step comes when the take finishes or fails. The replies that say what happened
and what comes next count toward a daily number you can lower, or set to zero to turn them off, in
**Settings** (*Times a day CODA answers what you do on its cards*); the one-line acknowledgement of an
approval does not use up that number, and turns off with it.

CODA can't see your pictures or clips. It tells you what it asked for ("I asked for a low angle
with no people"), and checking what a picture actually shows is yours: an image model doesn't
always do what it was asked. If a reply does describe a picture's contents, it ends with *I
haven't seen the picture, so check it yourself.* A clip made from a still is asked for movement
only: the still is what it starts from.

CODA's reply appears as it is written. While it is replying the send button becomes **Stop**;
stopping keeps what you have seen — the partial reply stays in the conversation, marked as
stopped.

If the connection drops while CODA is replying, a notice under the conversation says so, and
whether CODA had received your message — if it had not, your message is still in the box to
send again. You can switch to another session while CODA is replying in this one and carry on
there; the reply keeps going and is waiting when you come back.

The box grows as you type, up to four lines, then scrolls. **Enter** sends; **Shift+Enter**
starts a new line. What you have typed is kept if you switch sessions and come back.

Type **`/`** at the start of the box for shortcuts to what CODA can do — *Start a script*, *Add
a scene*, *Generate an image*; each puts a sentence in the box for you to finish and send. Type
**`@`** anywhere to name one of your production's committed bible entries exactly. The box
mentions `@` only once the bible has an entry to name.

Under the box, one quiet line says where your message goes: *Your current chat session is:* and
the session's name. Click the name to open the **Sessions** list. A long name is shortened with
an ellipsis; hover the line to read it whole.

A session takes its name from the first thing you say. Hover it in the **Sessions** list to
rename it.

## Where to go next

- **[Your first shot](https://docs.zymcos.com/product/your-first-shot/)** — the shortest path from signing in to a
  finished take.
- **[Signing in and out](https://docs.zymcos.com/product/signing-in/)** — sessions, and what "temporarily unavailable"
  means.
- **[Glossary](https://docs.zymcos.com/product/glossary/)** — the words this workspace uses.
- **[Writing a script](https://docs.zymcos.com/product/writing-a-script/)** — the Production Book: scenes, beats,
  locking, and what CODA may edit for you.
- **[The production bible](https://docs.zymcos.com/product/production-bible/)** — characters, environments and props as
  records, the references that define them, and what locking a bible means.
- **[The continuity gate](https://docs.zymcos.com/product/continuity-gate/)** — how a generated shot is measured
  against those references, and what that check does and does not enforce today.

## Getting help

- **Ask these docs** — the question box understands questions, not just keywords, and every
  answer links to the page it came from. See [Asking the docs a question](https://docs.zymcos.com/product/ask-the-docs/).
- **Ask for support** — if the docs do not resolve your problem, a support request is how you
  reach Zynth. [Support requests](https://docs.zymcos.com/product/support-requests/) says how one works and what is not built
  yet.

## Troubleshooting

This section is being written. Each troubleshooting guide is added as the corresponding feature
ships, so that every page here describes software you can actually run.

**"Zymcos is temporarily unavailable."** Part of the service is down for a moment. You are still
signed in and nothing you made is lost: stay on the page, and it comes back by itself as soon as
the service does (or choose **Try again**).

**Signed out after an update.** Some maintenance releases restart the service that holds sign-in
sessions, which signs everyone out once. The release notes say so when it happens; signing in
again is all it takes.

- **[When a take fails](https://docs.zymcos.com/product/when-a-take-fails/)** — what the card says, whether trying
  again can help, and the code to quote to support.
