You built it.
Now brag.

/brag is an open-source agent skill that turns a project you just built into a short, shareable launch video — music, motion, and share copy included. One command. No video editor.

Who made it

By latent-spaces (Shunit Haviv Hakimi), MIT license. Original repo: github.com/latent-spaces/brag (created 2026-06-16). Docs: latent-spaces.github.io/brag. A hosted version runs at letsbrag.app (paste a site link, get a video). A community fork lives at github.com/mymyanmarland/brag.

How it works

1. The agent reads your project code to understand what the app does.
2. It plans the story — the angle, the hook, the best moments to show.
3. It uses your real UI and branding, not stock filler.
4. It builds the scenes with motion, music, and sound effects.
5. It renders the video with Hyperframes — HeyGen's open-source HTML-to-video framework.

What it's for

Developers, indie hackers, and founders who built an app with a coding agent and want a launch video fast — for X, LinkedIn, Facebook, or Discord. Voiceover is off by default; /brag --voice adds Kokoro narration. /brag-slim is a lean variant for Claude Opus 5.5 (no Hyperframes).

What you get

Everything lands in brag-output/:

• brag.mp4 — the rendered video (15–25 seconds)
• brag.jpg — the poster frame (also baked in as frame 0)
• brag-plan.md — the plan and storyboard
• composition-brief.md — the brief handed to Hyperframes
• share-copy.txt — the caption, ready to post
• composition/ — the Hyperframes project

Example — PocketLab

This 21-second video was made from a real project (PocketLab, a phone science lab with 100 experiments) on a test machine: 1920×1080, 30 fps, 1.5 MB, music + sound effects. Hyperframes check: 0 errors, 33/33 contrast passed. The Burmese hero line renders correctly.

Three steps. Install, check, run.

Step 1 — Install /brag

Codex:

codex plugin marketplace add latent-spaces/brag
codex plugin add brag@brag

Claude Code:

/plugin marketplace add latent-spaces/brag
/plugin install brag@brag

Any other agent (Cursor, Copilot, Gemini CLI, opencode):

npx skills add https://github.com/latent-spaces/brag --skill brag

Add -g to install globally (every project); drop it to scope to one project.

Step 2 — Check the requirements

• An agent that supports Agent Skills (Claude Code, Codex CLI, opencode, Cursor, Copilot, Gemini CLI)
• Node.js 22+
• FFmpeg on PATH
• Hyperframes CLI — check it and fetch its browser:

npx hyperframes doctor
npx hyperframes browser ensure

Step 3 — Run it inside any project

/brag

Steer it if you like: /brag --tone polished, /brag --format vertical, /brag --voice. Your video appears in brag-output/brag.mp4.

Before any real video: get the Muse ready, and prove it with a test render.

Why two phases?

Install problems (missing browser, low disk, blocked CDN) are much cheaper to find on a throwaway example than on your real launch video. Phase 1 finds them once, so Phase 2 is smooth.

Phase 1 steps

1. Open the Muse's own chat and send it the Phase 1 message (Section 5 — one Copy All tap).
2. The Muse installs /brag and Hyperframes on its own machine, downloading them itself from GitHub. Nobody can push files into another Muse's machine — each one installs it itself.
3. It proves it works: it clones the brag repo and runs /brag on one of its bundled examples to render a short test video.
4. It runs npx hyperframes check in the composition and fixes every error.
5. It shows you the test video and the check result. It makes nothing real yet — it waits for your project.

What "ready" looks like

• Plugin installed (Codex) or skill installed (other agents)
• npx hyperframes doctor passes (browser ready)
• Test video exists, 15–25 seconds, with audio
• Hyperframes check: 0 errors
• Frames are readable, and any Burmese text is verified in the frames

The Muse is ready. Now give it a project.

What to send

• App name — e.g. PocketLab, ShwePrompt, KeyScope.
• Repo link — e.g. https://github.com/<you>/<app>, or the project folder if it has no repo yet.
• What to highlight (optional) — the one feature or claim the video must show. One line is enough.
• Tone / format (optional) — default is landscape, polished, 15–25 seconds. Say vertical or square for social feeds.

What happens next

1. The Muse reads the project, plans the video, and renders it.
2. It shows you the video and key frames first. Nothing is published.
3. You review it. Wrong word, wrong scene, wrong tone? Say so — it re-renders.
4. When you approve, download the mp4 and post it yourself.

Two messages. One tap each — Copy All, paste into the Muse's own chat. Replace PocketLab with your app name, and add its repo link.

Phase 1 — Get ready

Get ready to make launch videos with /brag, the open-source skill from https://github.com/latent-spaces/brag. Install it on YOUR OWN VM now, so you are ready when I give you a project. Download everything yourself from GitHub on your machine.
codex plugin marketplace add latent-spaces/brag
codex plugin add brag@brag
npx hyperframes browser ensure
For other agents: npx skills add https://github.com/latent-spaces/brag --skill brag
Then prove it works: clone https://github.com/latent-spaces/brag and run /brag on one of its bundled examples to render a short test video.
Run npx hyperframes check in the composition and fix every error.
Show me the test video and the check result. Do not make any real project video yet. Wait until I give you an app and its repo.
If /tmp is small, set TMPDIR to a workspace folder before rendering.
If the GSAP CDN fails, vendor GSAP locally.

Phase 2 — Make my video

Make a launch video with /brag, the open-source skill from https://github.com/latent-spaces/brag. Install it on YOUR OWN VM and test it there first. Download it yourself from GitHub on your machine.
codex plugin marketplace add latent-spaces/brag
codex plugin add brag@brag
npx hyperframes browser ensure
For other agents: npx skills add https://github.com/latent-spaces/brag --skill brag
Make a 20-second launch video for PocketLab in your VM.
Show me the video and frames first. Do not publish anything.
If /tmp is small, set TMPDIR to a workspace folder before rendering.
If the GSAP CDN fails, vendor GSAP locally.

Two problems came up during the verified test run. Both have fixes.

1. Render refused — low disk space on /tmp

On the test machine, /tmp is a 512 MB tmpfs. The render refused for low disk. Fix: point the temp and frame-cache folders at your workspace on every Hyperframes command:

TMPDIR=~/workspace/brag-test/tmpdir HYPERFRAMES_EXTRACT_CACHE_DIR=~/workspace/brag-test/frames-cache npx hyperframes render --output brag-output/brag.mp4

2. GSAP CDN failed in render workers

The render workers could not load GSAP from cdn.jsdelivr.net (ERR_TUNNEL_CONNECTION_FAILED), so timelines never registered and the render was blocked. Snapshots had worked — only the render path failed. Fix: vendor GSAP locally — copy gsap.min.js from Hyperframes' own node_modules into composition/assets/vendor/gsap.min.js and point index.html at the local file.

What to check before you trust a video

• npx hyperframes check — 0 errors (contrast included)
• Frames are readable — every line holds long enough to read
• Burmese text verified in the frames — never trust the plan alone
• Audio is present — ffprobe shows an audio stream, not silence
• Poster baked as frame 0 — so every platform shows the right thumbnail

Honest limits. These are untested or out of scope — the guide says so rather than pretending otherwise.

Do I need Codex or Claude Code on my own machine?

No. Ask your Muse — it installs /brag and renders on its own machine, then shows you the video. Install it yourself only if you want to run it directly without waiting.

Can one Muse make videos for all my apps?

Yes — one at a time. Give it one app, review the video, then the next.

Can two Muses work on the same video?

No. One video, one Muse. Two agents on one video double the work and split the decisions.

Where does the video file live?

In the Muse's workspace, under brag-output/brag.mp4. Download it from the chat and post it yourself.

Does it cost anything?

/brag and Hyperframes are free and open source. The agent run uses your AI provider's tokens or API plan — the same cost as any other agent task.

Can I use my own fork?

Yes. Replace latent-spaces/brag with mymyanmarland/brag (or your fork) in the install commands. Example fork: github.com/mymyanmarland/brag.

What is /brag-slim?

The same /brag, rebuilt lean for Claude Opus 5.5 — no Hyperframes, same creative rules. On Opus 5.5, /brag switches to /brag-slim automatically.