# Make and edit video with your coding agent

Atet gives your agent one local project to generate images, video, and voice, edit screen recordings and imported footage, add captions, graphics, and motion, and export finished videos. Your source files never change.

Ask your agent to record your screen while you demo the app, cut the pauses and filler words, add captions and `logo.svg`, and show you a preview before the final export.

Free and open source under the MIT license. Version 3.2.0. Requires Bun 1.3.14 or newer. Recording needs macOS.

## One job in four commands

1. Report the recording, rendering, browser, and media tools on this machine: `atet doctor --json`.
2. Read the inputs, resources, and outputs of the built-in social-variants recipe: `atet workflows show social-variants --json`.
3. Resolve the whole run before anything renders: `atet workflows plan social-variants --input job.json --json`.
4. Stream progress and keep the record of the run: `atet workflows run social-variants --input job.json --jsonl`.

Atet covers four output families (images, diagrams, animated loops, and video) through four peer interfaces: Agent Skill, CLI, TypeScript SDK, and MCP. Delivery covers 16:9, 9:16, 1:1, and 4:5 with clean and captioned cuts from one edit.

- Generate: create images, video shots, voiceovers, and transcripts from text and reference media with the models available through your own Vercel AI Gateway.
- Edit: cut pauses and filler words, reframe speakers, zoom into screen actions, and add captions, overlays, color, and audio treatment. Source media stays unchanged.
- Deliver: preview the edit, then export clean and captioned versions in landscape, vertical, square, and portrait from the same timeline.

## Install

Two installs: the Agent Skill teaches your agent the creative decisions, and the CLI does the work. Atet requires Bun 1.3.14 or newer.

```sh
npx skills add https://github.com/hraness/atet/tree/v3.2.0 --skill atet
# or
bunx skills add https://github.com/hraness/atet/tree/v3.2.0 --skill atet
```

```sh
bun add --global @hraness/atet@3.2.0
atet doctor
```

Run `atet doctor` inside the project you want to work in. Then start a new agent session and describe the finished result, naming the source files and details that must remain unchanged.

The public skills command installs the current repository release guide. When that command is not being used, `atet skill install` installs the guide shipped with your CLI for Codex by default.

- Claude Code: `atet skill install --target claude`
- Other Agent Skill readers: `atet skill install --target agents`
- Only the current repository: run the install there and add `--scope project`

## Ask your agent to …

A useful request names the source, the result, and the details that must stay the same. Your agent plans the commands and shows you a preview before it makes the final files.

### Edit a product demo

Use Atet to record my screen, camera, microphone, and system audio while I demo the app. When I stop, turn the recording into a polished two-minute walkthrough. Remove long pauses and filler words, zoom in when I click or type, keep me framed, add readable captions and `logo.svg`, and show me a preview before exporting the final video.

### Generate an opening sequence

Use Atet to create three opening-shot ideas from `product.png`. Show them to me side by side, then animate the one I choose into a six-second widescreen clip. Keep the product shape, colors, and lettering recognizable.

### Add voice and deliver every format

Use Atet to generate a calm voiceover from `script.txt`, place it over the approved edit, mix the music quietly underneath it, and export clean and captioned versions in 16:9, 9:16, 1:1, and 4:5.

### Explain a system visually

Use Atet to turn the services in this repository into an editable diagram, then build a short animated version that introduces each service in order.

After it runs, your agent should show you the result and report the source, preview, and final output files. You can ask for changes in the same plain language.

## Workflow

Atet brings generation, editing, motion, and export into one project that your agent can inspect and revise. Preview and final renders use the same timeline and composition.

1. Bring in what you have. Record a screen, camera, microphone, and system audio on macOS, or import existing video, audio, images, and graphics.
2. Generate what is missing. Discover current Gateway models and create images, video shots, voiceovers, or transcripts from text and reference media.
3. Shape the edit. Remove pauses and filler words, align sound, reframe speakers, zoom into screen actions, add overlays, captions, color, and audio treatment.
4. Review before final. Render a lower-cost preview from the same timeline and composition that will produce the final video.
5. Deliver every version. Export clean and captioned cuts in landscape, vertical, square, and portrait formats without rebuilding the edit.

Graphics and motion use the same toolkit. Atet also creates editable diagrams, converts raster artwork to SVG locally, and builds deterministic animated layers with HTML, SVG, shaders, and Three.js. Those outputs can stand alone or join a video project.

## Interfaces

The same local system meets four kinds of caller:

- Agent Skill: version-matched guidance for turning a creative brief into the right operations. Install it with `npx skills add https://github.com/hraness/atet/tree/v3.2.0 --skill atet`.
- CLI: human-readable commands and stable JSON for local scripts. Start with `atet workflows list --json`.
- TypeScript SDK: declarative or imperative media work inside your own Bun code. Import `vectorizeImage` from `@hraness/atet`.
- MCP: a fixed set of typed operations confined to one selected root. Run `atet mcp --root /absolute/path/to/workspace`.

## What stays local

Atet keeps source media, editing decisions, previews, and final outputs in storage you control. The agent chooses explicit operations, and the project records what those operations changed.

- Source media stays unchanged. Original recordings and imported media are never rewritten. Cuts, timing, framing, overlays, and effects are recorded as project decisions, and every alternative starts from a named project state.
- Project state stays on your machine. There is no Atet account or hosted project database. Source, project state, previews, and final files stay in storage you control.
- Gateway credentials stay local. Model-backed work uses your Vercel AI Gateway credential from the local process, never stores or prints it, and uploads local media only after explicit acknowledgement.
- Operations leave receipts. Preview and final renders use the same timeline and composition, so the edit you approve is the edit that exports. Important operations keep secret-free receipts that name their inputs and outputs.

The installed Agent Skill and `atet --help` describe the exact tools on the current machine. The repository documents the rest.

- [README and agent guide](https://github.com/hraness/atet#readme)
- [Architecture](https://github.com/hraness/atet/blob/main/docs/architecture.md)
- [Security policy](https://github.com/hraness/atet/blob/main/SECURITY.md)
- [Atet on npm](https://www.npmjs.com/package/@hraness/atet)
- [Source on GitHub](https://github.com/hraness/atet)

## Questions

### Does Atet require an account or subscription?

No Atet account or subscription exists. Atet is free and open source under the MIT license. Model-backed generation uses caller-owned Vercel AI Gateway access.

### What does it cost?

Atet costs nothing. Editing, previews, diagrams, vectorization, and exports run on your machine. Model-backed generation goes through your own Vercel AI Gateway access, so any model usage is billed to that account, not to Atet.

### Where do my Gateway credentials live?

In the environment of the local CLI or SDK process. Atet does not store or print the credential, and this website never receives one. With a linked Vercel project, `vercel env run -- <command>` injects it for one command without writing it into the project.

### Which platforms does Atet run on?

macOS, Linux, and Windows with Bun 1.3.14 or newer. Screen, camera, microphone, and system-audio recording belongs to the macOS host and needs the matching operating-system permissions. `atet doctor` reports which tools the current machine has.

### Does Atet overwrite original media?

No. Original recordings and imported media stay unchanged while edits, alternatives, previews, and deliveries remain attached to explicit project states.

### When can local media leave the machine?

Only model-backed work may upload named media, and only after explicit acknowledgement. Local editing, vectorization, deterministic rendering, previews, and outputs remain local.

### Does the Atet website generate or edit media?

No. The website explains and installs the local system. Media work runs in the caller's CLI, SDK, MCP server, or desktop host.

## Built by Ben Guo

Atet is built by Ben Guo, a musician and builder, formerly a founder and engineering leader at companies including Venmo and Stripe, now building from Puerto Rico.

- [hraness.com](https://hraness.com)
- [@hraness](https://x.com/hraness)
- [GitHub](https://github.com/hraness/atet)

## The name Atet

Agentic creative coding toolkit. At the beginning of time, when there was nothing but chaos, Atum existed alone in the watery mass of Nun. A pyramid mound called Benben emerged. When the lotus flower bloomed, Atum dawned and became Ra. Every night Ra sails in the underworld on the solar barque Atet.

## Sitemap

- [Atet home](https://atet.sh/index.md)
- [Machine-readable site guide](https://atet.sh/llms.txt)
- [Markdown sitemap](https://atet.sh/sitemap.md)
- [XML sitemap](https://atet.sh/sitemap.xml)
