Good ideas.
Meet your tools.
Your next idea starts at the command line. Give your agent the SwayByte Preview #957 toolkit and create without breaking your flow.
Choose your agent
Select an app to get connected Swipe for more apps
Set up Claude Code
Give Claude Code your creative toolkit.
How to connect
Copy the setup prompt into Claude Code. Use a macOS, Linux, or WSL terminal with curl and Node.js 20 or newer.
Review the installation command. Your agent will install the CLI and read the supplied skill.
Open the approval URL your agent shows you, sign in to SwayByte Preview #957, and confirm the displayed code.
Let the agent check your available models and credit balance. Setup does not need a paid generation.
Set up the SwayByte Preview #957 CLI for this agent.
1. Check that this is a macOS, Linux, or WSL terminal with curl and Node.js 20 or newer. These shell commands do not target native Windows PowerShell. Download and inspect the installer at https://pr-957.swaybyte.com/cli/install.mjs, then run:
curl -fsSL https://pr-957.swaybyte.com/cli/install.mjs -o /tmp/swaybyte-install.mjs && node /tmp/swaybyte-install.mjs --source-origin https://pr-957.swaybyte.com --api-url https://api-pr-957.swaybyte.com
2. Read the agent skill at https://pr-957.swaybyte.com/cli/skills/swaybyte/SKILL.md. If this agent supports persistent skills, use its documented skill installation mechanism and the correct local skill folder. Do not overwrite existing configuration. Otherwise load the skill as guidance for this session.
3. Run ~/.local/bin/swaybyte auth status --json and confirm its issuer is https://api-pr-957.swaybyte.com. Stop and report any mismatch; do not switch to another API origin. Then start account authorization:
~/.local/bin/swaybyte auth login --no-browser
Show me the exact approval URL and code printed by the CLI, then wait for me to approve in my browser. Never ask me to paste passwords, API keys, or tokens.
4. After authorization succeeds, run ~/.local/bin/swaybyte auth status, ~/.local/bin/swaybyte models, and ~/.local/bin/swaybyte credits. Report whether the connection works. Do not generate any paid media during setup.Install manually
Use macOS, Linux, or WSL with curl and Node.js 20 or newer. These commands use a Unix shell. The installer adds the CLI to ~/.local/bin.
Connects to https://api-pr-957.swaybyte.com.
curl -fsSL https://pr-957.swaybyte.com/cli/install.mjs -o /tmp/swaybyte-install.mjs && node /tmp/swaybyte-install.mjs --source-origin https://pr-957.swaybyte.com --api-url https://api-pr-957.swaybyte.com~/.local/bin/swaybyte auth login --no-browserAfter approval, check your connection with swaybyte auth status. Use models and credits to check availability before creating media.
Sign in to SwayByte Preview #957, review permissions, and approve. You can disconnect any app below.
Availability & setup notes
Use a Claude Code session with terminal access. Your agent can read the skill and run the CLI in your project.
“Find video models on SwayByte Preview #957, show me their input fields and credit estimates, then retrieve my recent videos.”
Complete video workflows
Ask your agent to show available video workflows and their limits first. Supported workflows assemble your narration and stock-footage scene plan, or caption one to three clips from timestamps you choose. Shorts run 5–90 seconds each, up to 180 seconds combined.
Each submission saves a job ID. Check that job for progress, finished outputs and recorded credits, or recover it from your video history after reconnecting. Finished outputs stay available if another output fails. Your SwayByte plan, credits and queue rules apply to each output; review availability and billing notes before starting.
Stay in control.
Disconnect an app to revoke its access.
You can connect it again any time.
Loading your account…