Updating pod

One word — update — keeps your studio current, and every update is cryptographically checked so only the real thing ever installs.

pod improves constantly. New camera moves land in the vocabulary, generation engines get retuned, rough edges get sanded down — and fixes ship frequently, often within the same week someone reports a problem. Staying up to date is not a chore you schedule; it is one word you type whenever you feel like it.

The update command

If you are already inside the studio (you typed pod and you can see the bordered input box with the ❯ prompt), just type:

❯ update
checking for a new version…
verifying the release signature… ok
installing…
  (pod confirms the update really came from its makers before touching anything)

If you are not inside the studio, the same thing works from a plain Terminal window — the app where you first installed pod. Type pod update and press Enter (Enter is the key that says "go"). Both routes do exactly the same thing: pod fetches the latest version, verifies it, and installs it. Your films, your series canon, your saved keys and your habits are untouched — everything under your episodes folder stays exactly where it is.

There is nothing to download from a website, no installer to hunt for, no version numbers to compare. pod handles all of it.

Why you can trust an update — signed releases

Every pod release is cryptographically signed by its makers. Think of it like the seal on an app from an app store: before installing anything, pod checks the seal. The mathematics behind it means the seal cannot be forged — only pod's makers can produce it.

Concretely, before an update installs, pod verifies three things:

• It came from the makers. If the signature does not check out, pod refuses to install — no exceptions, no override.
• It was not tampered with. If even one byte of the download was altered anywhere along the way, the check fails and pod refuses it.
• It is not older than what you have. pod will never "update" you backwards to an earlier version. A downgrade attempt — accidental or malicious — is rejected the same way a forgery is.

You do not have to do anything to get this protection. It runs on every single update, silently, before anything changes on your machine. If a check ever fails, pod simply stops and tells you — your current, working version stays put.

Windows: one extra move

On Mac and Linux the update installs itself completely. On Windows, a running program cannot overwrite its own file, so the update finishes with one extra step: pod downloads and verifies the new version, then shows you a single move command to run. Copy the exact line pod prints, paste it, press Enter — done. pod tells you precisely what to type; there is nothing to figure out yourself.

❯ update
new version downloaded and verified.
one last step — run this to finish:
    (pod shows the exact move command here — copy, paste, Enter)

How often fixes ship

Often. pod is actively made, and small releases go out frequently rather than big ones rarely. When someone reports a bug — a Telugu voice coming out with the wrong accent, a title card rendering oddly, a gate that asked a confusing question — the fix commonly ships the same week. That is the whole reason the update command is one word: the makers want the distance between "you mention it" and "it's fixed on your machine" to be as short as possible.

A good habit: type update before starting a new production. It costs a few seconds and means every film benefits from the latest crew.

Feedback and bug reports — feedback and report

Your feedback is where most of those weekly fixes come from. There are two commands, both typed right inside the studio:

• feedback — for anything: a suggestion, a wish ("I want a preset for wedding teasers"), something that felt clumsy, something you loved. Plain words, sent straight to the makers.
• report — for when something actually broke. It sends a bug report with context, so the makers can see what went wrong without you having to describe technical details you never asked to learn. If a shoot dies mid-scene or the studio behaves strangely, report is the fastest path to a fix.

❯ feedback the coverage interview is great but I'd love a "match episode 1" shortcut
sent — thank you. feedback like this often ships within the week.

You do not need to file anything formal, know version numbers, or attach files. Say it the way you would say it to a person. Then keep an eye out: type update a few days later and there is a decent chance your suggestion is already in the studio.

If something looks off after an update

Run doctor. It re-checks the whole setup — the video engine, the graphics renderer, your keys — and renders two free local test clips to prove everything works. It self-heals most toolchain problems on its own. For anything it cannot fix, report sends the details to the makers, and the troubleshooting page covers the common cases.