Help centre Start here
Connect Claude Code or Codex
Swiftbird works through the AI agent you install yourself. How it finds it, what the statuses mean, how the talker and the builders split the work, and what stays between you and your provider.
How the connection works
Swiftbird doesn't have an AI model of its own and doesn't sell AI. Its Chat drives the Claude Code or Codex command-line tool installed on your computer. Every request runs in that tool, under your own account, with its own sign-in and permission settings.
That means:
- you need your own Claude or OpenAI plan, billed by the provider, not by Swiftbird;
- Swiftbird never copies or stores your provider credentials;
- whatever your provider account allows, such as which models you can use and how much, still applies.
Swiftbird is not a proxy
Swiftbird isn't a proxy or an intermediary between you and Anthropic or OpenAI:
- Straight to the provider. Claude Code or Codex sends your messages and files directly to Anthropic or OpenAI. Nothing passes through Swiftbird's servers. The app shows the conversation on your screen and sends it nowhere else.
- Your sign-in stays yours. You sign in on the provider's own sign-in page, through Claude Code or Codex. Swiftbird never sees, stores or forwards your password or sign-in tokens.
- Nothing collected. Your chats are Claude Code or Codex chats, and like theirs they live on your own computer. Swiftbird never uploads or collects them, nor your prompts or projects. Its cloud holds only your Swiftbird sign-in and subscription.
- Nothing altered. What you send reaches the provider exactly as you wrote it. Alongside it, Swiftbird briefs the agent on the editor and your film, which is how it knows the studio.
- The official programs, unmodified. Swiftbird runs the Claude Code or Codex you installed, as published by Anthropic or OpenAI.
- Carry on without Swiftbird. Open in terminal reopens a conversation in Claude Code or Codex itself, right where it stands.
The Swiftbird subscription pays for the studio. Your Claude Code or Codex usage remains on your own provider account and is billed separately.
Use your plan or an API account
Claude Code and Codex each let you choose how you're billed when you sign in:
- A plan: your Claude plan, or your ChatGPT plan for Codex.
- An API account: an Anthropic Console account for Claude Code, or an OpenAI API key for Codex.
Either way, Anthropic or OpenAI bill you directly under your own agreement with them.
Install and sign in
- Install Claude Code, Codex, or both, following the provider's own instructions.
- Sign in using the tool's own login in a terminal (for example
codex login, orclaudefollowed by/login). - Open Swiftbird. It looks for installed copies, checks their version and whether they're signed in, and uses the newest working version it finds.
If a tool shows Sign-in needed, the Sign in button starts that tool's own login command. Swiftbird never signs in on your behalf.
What the statuses mean
| Status | Meaning | What to do |
|---|---|---|
| Connected | Installed and signed in | Nothing |
| Sign-in needed | Installed, but signed out | Use Sign in, or log in from a terminal |
| Not found | No installed copy was found | Install the tool, then check again |
| Not checked | Installed, sign-in state unknown | Use Check connection |
The talker and the builders
Each conversation is split in two:
- The talker answers first, in Chat, on the timeline and in the Scene Lab. It's a quick agent on your own subscription (Claude: Sonnet 5.5 at high; Codex: GPT-6.1 Sol at high). Swiftbird's rules are its own system prompt, the first and deepest instructions it reads, so it knows the app, your projects and your tools. It makes small edits itself with the editor's tools, never adds motion, and writes a plan before anything bigger is built.
- Builders do the jobs in the plan: Blender for 3D, Remotion for motion graphics, research, edits, and any new motion. They run on the builder model you choose for the film in the Builder menu: Opus 5.5 or Fable 5.1 on Claude, GPT-6.1 Sol or GPT-6 Astra on Codex, at high effort or above.
Talking and planning don't need your biggest model, so your chosen model's effort goes to the work.
Permissions, questions and stopping
Your agent's normal permission settings still decide what it may do. Its permission requests and questions appear as cards you can answer. Stop cancels the request that Swiftbird started.
Where your conversations go
Your messages, the attachments you add and the project context you select go to your provider through its tool, under its privacy terms. Swiftbird keeps its own copy of each conversation on your computer. See Your data stays on your machine.
Last reviewed 15 October 2026. Describes Swiftbird as planned for launch; details can change before then. Still stuck? Contact support.