Let your coding agent add sounds to an app with blips
By Flavio
Install the blips command and agent skill from Chip Pops, ask Claude Code, Cursor or Codex for app sounds, listen to its picks, and keep the IDs it exported.
You’re building an app with a coding agent, and it needs a few sounds. A chime when a note is saved, a crunch when it’s deleted, a swoosh when a message goes out. You’d like to say that in one sentence and have the files land in the project, named after what they do.
The catch is that the agent can’t hear anything. Left alone, it will grab a random file from somewhere, or write a synth in code that sounds like a smoke alarm. What you want is an agent that knows where good sounds are, picks a short list, and lets you make the call with your ears.
That’s the workflow Chip Pops was built for. It’s a Mac app with about 6,000 8-bit sound effects, plus a blips command and an agent skill that teaches Claude Code, Cursor and Codex how to use it. By the end, your agent will find candidates, you’ll listen, and the chosen WAV files will sit in your project with their source IDs written down.
If you’d rather pick sounds by hand for a Swift app, Pick UI sounds for clicks, toggles and errors in a Mac or iOS app covers that.
What you need
Chip Pops runs on macOS 14 or later, on Apple silicon and Intel Macs.
After purchasing, download the app ZIP from your Polar receipt, unzip it, and drag Chip Pops.app to Applications. The app is signed and notarized, so confirm Open at the first-launch prompt. The receipt also has the full source code of the same version, and a license key that turns on automatic updates.
The first time you open it, click Generate the Library. Chip Pops makes every sound on your Mac with jsfxr, which the README says takes less than half a minute and about 300 MB. The library lives in ~/Library/Application Support/Blips. The sounds are yours to use in free or commercial projects, with no credit needed.
You also need a coding agent that reads skills from a folder: Claude Code, Cursor or Codex. The skill installer looks for their home folders, ~/.claude, ~/.cursor and ~/.codex, so open each agent at least once before you install the skill.
Last, a project to put the sounds in. In this tutorial it’s a Mac app at /Users/flavio/dev/recipe-box and a web app next to it. Those paths and app names are examples.
Here’s the preflight check. Once the command is installed (next section), this should print the version and the command list:
blips help
blips 1.3.1: 8-bit sound effects made with jsfxr, in categories, for the interfaces of your apps.
Usage: blips <command> [options]
categories List the categories, with how many sounds each has
list List sounds, by category, tag or words in their name
show Show a sound's file, tags and jsfxr parameters, or what a combo or jingle is made of
play Play sounds, one after the other
path Print the library folder, or a sound's WAV file
export Copy sounds into a folder, like an app's resources
generate Generate the library with jsfxr, replacing the one there
capabilities What blips can do, and what changed in each version
Install the command and the skill
An agent works through the terminal, so it needs two things from Chip Pops. The blips command is how it searches and copies sounds. The skill is how it knows that command exists, when to reach for it, and which rules to follow. Without the command, the agent has nothing to run. Without the skill, it has a command it never thinks of, and you’d have to explain the categories, tags and export flags in every chat. Install both once, from the app’s menu, and every new chat in every supported agent picks them up.
In Chip Pops, open the Chip Pops menu:
Chip Pops → Install Command Line Tool…
Chip Pops → Install Agent Skill…
The first item links blips into ~/.local/bin. If your shell can’t find it afterwards, add that folder to your PATH.
The second copies the skill to ~/.agents/skills/blips. Then, for each agent whose home folder exists, it creates a link named blips in that agent’s skills folder, pointing at the shared copy. So ~/.claude/skills/blips and ~/.codex/skills/blips are the same file, not two copies that drift apart. If you already made a link there yourself, the installer leaves it as it is.
When it works, you get an alert:
The agent skill is installed
Claude Code, Cursor and Codex now know how to add sounds to your apps with the blips command. Install the command too, from the same menu.
Check that the agent folders point where you expect:
ls -l ~/.claude/skills/blips ~/.codex/skills/blips
lrwxr-xr-x@ 1 flavio staff 34 Oct 5 10:32 /Users/flavio/.claude/skills/blips -> /Users/flavio/.agents/skills/blips
lrwxr-xr-x@ 1 flavio staff 34 Oct 5 10:32 /Users/flavio/.codex/skills/blips -> /Users/flavio/.agents/skills/blips
Both are links to the same folder. If an agent isn’t listed, it didn’t have a home folder when you clicked. Open it once, then run Install Agent Skill… again. A second install replaces SKILL.md with the copy bundled in the app, which is also how you refresh it. The app copies it again on launch when an update changed it.
For the agent’s own discovery, there’s a manifest it can read too:
blips capabilities --json
{
"capabilities" : [
{
"command" : "blips categories --json",
"description" : "List the sound categories: interface sounds, game sounds, combos and jingles"
},
{
"command" : "blips list --category sent --json",
"description" : "Find combos of two sounds for app events, like a swoosh into a pop for a sent message"
},
Ask for sounds by event, not by ID
The best prompt describes what happens in your app, not which file you want. The skill gives the agent a table that maps events to categories: done or saved goes to success, deleting goes to trash, a message sent goes to sent, switches go to toggle, alarms go to alarm. If you ask for “a nice ding”, the agent has to guess what the ding is for. If you say “when a recipe is saved”, it lands in the right category, and it names the file after the event. That name is what your code will refer to for years.
So write the request the way the README does, by event:
Add a sound when a recipe is saved, and one when it's deleted.
Keep them calm, this is a cooking app.
The agent starts by looking at what’s there:
blips categories
Interface
click 158 Short clicks and taps for buttons and keys
blip 188 Menu blips for hover, select and navigation
pop 152 Bubbly pops for new messages and items
toggle 400 Two-note flicks for switches and checkboxes
success 111 Rising chimes for done, saved and correct
error 400 Low buzzes for failures and wrong input
notification 172 Chimes that ask for attention, for alerts and reminders
swoosh 400 Whooshes for transitions, sending and sliding panels
The full output goes on with the Game, Combos and Jingles groups, and ends with 5957 sounds in 26 categories, from seed 1. Categories have different sizes because Chip Pops only keeps a sound that’s clearly different from every other one in its category. That’s why there are 111 success chimes and 400 errors.
“Calm” matters too. The skill tells the agent that soft means a sine wave, the calmest sound, while retro is square and chiptune. It also says sounds for frequent actions should be short, and jingles are for moments that happen once.
Let the agent shortlist, then listen yourself
This is the step that makes the whole thing work. The agent can read names, tags and lengths, but it can’t judge whether a chime is pleasant or grating. The skill tells it to pick two or three candidates per event and ask you to listen. If you skip this and let it export the first match, you’ll ship a sound nobody chose. Sometimes that’s fine. Often it’s a 0.6 second chime on an action you do forty times a day.
Here’s what the agent runs for the saved sound:
blips list --category success --tag soft --limit 5
success-009 0.47s Soft rising success [sine, repeating]
success-011 0.26s Soft rising success [sine, vibrato]
success-014 0.62s Soft rising success [sine, long]
success-015 0.46s Soft rising success [sine]
success-017 0.55s Soft rising success [sine]
The agent reads the lengths and tags. success-014 is tagged long, so it drops it for a frequent action. Then it asks you to play the rest:
blips play success-011 success-015 success-009
success-011 0.26s Soft rising success
success-015 0.46s Soft rising success
success-009 0.47s Soft rising success
blips play plays them one after the other, with macOS’s built-in afplay command, and prints each line as its sound starts. Tell the agent which one you liked by its ID. You can also open them in the app, which is faster if you want to go back and forth: the arrow keys move to the next sound and play it, and Space plays or stops.
open -a "Chip Pops" --args -select success-011
That opens Chip Pops on that exact sound, with its waveform and pitch in the inspector.
Combos work the same way. For deleting, the agent looks at trash, which is a falling swoosh into a crunch:
blips show trash-003
trash-003: Falling swoosh into retro hit
Category Trash: A falling swoosh into a crunch, for deleting and throwing away
Library seed 1
Tags sequence, swoosh, hit, low, noisy, falling, retro
Length 0.36s
Made of swoosh-121 at 0.00s, hit-052 at 0.23s
File /Users/flavio/Library/Application Support/Blips/sounds/trash/trash-003.wav
For a single sound, show also prints the jsfxr parameters and an Edit link to sfxr.me, if you want to make a variation.
Export the files under the names the app uses
Exporting copies a sound out of the library into your project. The --name flag is the important part. A file called success-011.wav tells the next person nothing, while saved.wav says what it’s for, and it means you can swap the sound later without touching the code that plays it. Without an export, your app would point into ~/Library/Application Support, which only exists on your Mac. The file has to live inside the project so it ships with the build.
Example 1: a saved and a deleted sound for a Mac app
You liked success-011 and trash-003. The agent copies them into the app’s resources:
cd /Users/flavio/dev/recipe-box
blips export success-011 --to Resources/Sounds --name saved.wav
blips export trash-003 --to Resources/Sounds --name deleted.wav
/Users/flavio/dev/recipe-box/Resources/Sounds/saved.wav
/Users/flavio/dev/recipe-box/Resources/Sounds/deleted.wav
Each command prints the path of the file it wrote. The folder is created if it isn’t there. Agents usually add --json, which gives them the ID and path to read back:
[
{
"id" : "success-011",
"path" : "/Users/flavio/dev/recipe-box/Resources/Sounds/saved.wav"
}
]
Be careful with a second run. The help says it plainly: “Existing files are replaced.” There’s no prompt. If you already shipped a different saved.wav, exporting again overwrites it, so commit the sound files before you let the agent try alternatives. Then git diff shows a changed binary, and git checkout -- Resources/Sounds/saved.wav brings the old one back.
Example 2: a click and a sent sound for a web app
A web app keeps static files somewhere like public/sounds. Without --name, the files keep their IDs as names, and you can export several at once:
blips export click-002 sent-001 --to public/sounds
/Users/flavio/dev/recipe-box-web/public/sounds/click-002.wav
/Users/flavio/dev/recipe-box-web/public/sounds/sent-001.wav
--name only works with one sound, so this is the form for a batch. The --format flag converts with afconvert, to m4a, caf or aiff. The skill says WAV works in every browser and starts right away. M4A makes longer sounds smaller, but AAC adds a few milliseconds of silence at the start, so keep WAV for clicks. A half-second sent-001 is a fair candidate for m4a. A 0.06 second click-002 isn’t.
Write down the IDs and the seed
An exported file doesn’t remember where it came from. Six months later you want a slightly softer delete sound, and nobody knows that deleted.wav was trash-003. The skill tells the agent to record the Chip Pops ID of each file in the app’s AGENTS.md, so the next chat can find the neighbours of the sound you picked. The seed matters too. Chip Pops generates its whole library from a seed, and success-011 is the same sound on every Mac only as long as everyone is on the same seed.
The library you get from Generate the Library comes from seed 1. Library → Generate… can make a different library with New Sounds or Seed…, and then every ID points at a different sound. blips show prints the seed on its Library line.
Here’s the kind of note the agent adds. The wording is an example. The skill only asks for the ID, and the seed when it isn’t 1:
## Sounds
Resources/Sounds/saved.wav Chip Pops success-011 (seed 1)
Resources/Sounds/deleted.wav Chip Pops trash-003 (seed 1)
When the agent exports again from a note like that, it should pass the seed. --seed doesn’t change anything. It checks that the library is the one you mean and stops if it isn’t.
Example 3: an export from the wrong library
A teammate’s note says success-011, seed 48213. Your library is the default one:
blips export success-011 --to Resources/Sounds --seed 48213
blips: These sounds are from seed 1, not 48213. Run 'blips generate --seed 48213' first.
The command exits with status 1 and writes nothing. Without --seed, it would have quietly exported a different chime under the same ID. The fix is in the message, but think before you run it: generate replaces every sound in your library, and the skill tells agents to ask before using it. Afterwards, blips generate with no seed brings back the main library. According to the skill, that takes about 15 seconds.
Play them quietly in the app
The last step is code, and the skill gives the agent a few rules for it. A sound that’s too loud, or that fires on every hover, is the fastest way to make people mute your app. The skill says to play interface sounds quietly, at a volume around 0.4, not on every hover, and to give people a setting to turn them off. If your agent writes the playback code without those rules, ask it to apply them. You’ll hear the difference the first time you save something.
For Mac and iOS apps, the skill says to put the WAV files in the target’s resources and play them with NSSound or AVAudioPlayer. For web and Electron apps, it gives a one-liner:
new Audio('/sounds/saved.wav').play()
Before wiring anything, play the exported file from the project, to make sure the copy is the sound you picked:
afplay Resources/Sounds/saved.wav
Undoing the whole thing is ordinary: delete the files from Resources/Sounds and the lines that play them. Nothing in your project depends on Chip Pops being installed. The skill and the library stay on your Mac for the next app.
If something looks wrong
If the agent says zsh: command not found: blips, the command isn’t on its PATH. Run Install Command Line Tool… and add ~/.local/bin to your PATH. The skill also tells agents to fall back to "/Applications/Chip Pops.app/Contents/Helpers/blips".
If the agent never mentions Chip Pops and writes its own sound code instead, the skill isn’t in its folder. Check ls -l ~/.claude/skills/blips (or .cursor, .codex), open that agent once, and run Install Agent Skill… again.
If you get blips: There's no library in … yet. Run 'blips generate' to make it., Chip Pops was never opened, or BLIPS_HOME points at an empty folder. Open the app and click Generate the Library, or unset BLIPS_HOME.
If blips list prints No sounds match., that tag doesn’t exist in that category. error --tag soft gives nothing, for example. Drop the tag, or try --search with words from the sound names.
If you see blips: There's no sound 'success-999'. Run 'blips list' to see them., the agent guessed an ID. Make it pick IDs from a blips list it ran, not from memory or from an example in a README.
If the export fails with blips: --name only works with one sound, and this exports 2., split it into one export per file, each with its own --name.
If blips: These sounds are from seed 1, not 48213. appears, your library isn’t the one the note was written against. Decide whether you want to regenerate, because generate replaces every sound, or pick a new sound from the library you have.
If saved.wav suddenly sounds different, an export ran again and replaced it. Restore it from git, and check AGENTS.md for the ID it should be.
Get Chip Pops
Find and export about 6,000 8-bit sound effects for apps and games. Includes a Mac app, the blips command and full MIT source code.
See Chip Pops → · Read the docs · $20. See the app page for tax details, with full source code.
Want me to talk about your product? You can sponsor this site.