What Swiftbird doesn't do, on purpose
No bundled AI, no rendering, no automatic uploads, no cloud copy of your films. Each "no" is a decision, and here's why.
Product pages usually list what something does. This post lists what Swiftbird doesn't, because for a tool that sits between you, your AI agents and your films, the limits matter as much as the features.
It doesn't sell you AI
Swiftbird drives the Claude Code or Codex command-line tool you install and sign in to yourself. It doesn't include a model, resell tokens, or hide an AI bill inside its price.
Why: you already pay for your agent, and you should keep full control of that account, its limits and its data terms. A desk shouldn't take a cut of your AI spend. It also means Swiftbird uses your agent exactly as it is, with your skills, your tools and your settings.
It doesn't render your film
Blender renders the 3D, Remotion renders the graphics, and Premiere finishes the edit. Swiftbird shows stills and existing rendered segments, and its scene editor is a wireframe for direction, not a renderer.
Why: those tools are excellent at rendering, and a final render is a deliberate, often expensive decision. Swiftbird never starts one on its own.
It doesn't change Blender behind your back
The scene editor produces a proposal. Blender stays unchanged until your agent builds the change through your normal workflow, and you can compare the result against exactly what you asked for.
Why: a production scene has one writer at a time. Two things editing the same file is how work gets lost.
It doesn't upload automatically
Publishing prepares everything YouTube needs and shows you exactly what would be sent. Nothing uploads from a chat reply, a saved draft or a planned date. And to be plain about where things stand: no video has been published through Swiftbird yet.
Why: publishing is irreversible in the ways that matter. It should always be a deliberate act.
It doesn't approve anything for you
An agent saying "done", a judge's pass, or a date on the calendar is recorded as exactly that. Script approval, scene acceptance and upload are yours.
Why: long films drift when "finished" and "approved" get blurred. Keeping them separate keeps the film what you meant it to be.
It doesn't keep your films in the cloud
Your films, media, scripts, conversations and keys stay on your computer. Swiftbird's cloud holds your sign-in and, once paid plans launch, a minimal billing history.
Why: documentary work is large, private and often licensed. There's no reason for it to leave your machine, and every reason for it not to.
It doesn't run on a Mac
Swiftbird is a Windows app. We'd rather do one platform properly than two badly.
If that sounds like the right kind of tool, join the Windows waitlist. If you want to know exactly what works today, the changelog keeps a straight record.