Best music tools for Codex game devs

Brief one: the desert crawl

The first cue is for exploration under pressure — the player is low on water, the level is long, nothing is chasing them yet. That is a scene, not a genre, and writing it that way is what gets sparse percussion instead of generic action music.

Brief two: the camp

The second cue is the opposite state — the player has stopped, the danger is outside, the music should stay out of the way. Same service, same price, brief rewritten around the moment rather than around a mood word.

What the two runs show

Same price, same service, three times the length and four times the render time between them. Track length is not something you set — the model decides, and a brief that implies more development gets more of it. For a game that is usually fine: a three-minute bed loops as easily as a one-minute one, and trimming or crossfading is ordinary local work the agent does for nothing. It matters only if you are scoring to picture, where you should generate long and cut rather than hope for an exact duration.

The two candidates per run are the other thing worth planning around. One charge, two takes, and they are genuinely different arrangements rather than two renders of the same idea — so the practical loop is to brief once, listen to both, and keep the one that fits. That makes a five-cue soundtrack five runs, not ten.

Writing a brief that behaves

1. Describe the moment, not the genre

   "Player is low on water, nothing is chasing them yet" produces better material than "tense music". Instrumentation follows from the situation.

2. Say instrumental as an instruction

   Ask the agent to switch instrumental on in the call rather than writing "no vocals" in the sentence. Written as prose, a brief can end up sung — we watched that happen on a previous run.

3. Put the style in the tags

   Genre, mood, and instruments belong in the tags field; what to avoid belongs in the negative tags. The prompt field is for the scene.

4. Generate long, cut locally

   You cannot order a 45-second cue. Take the longer track and let the agent trim and loop it — that pass is free and repeatable when the level changes.

Where a generated cue stops being enough

A generated track is a finished piece of music, and a game needs music that reacts. Neither of the cues above knows when the player enters combat, when the boss health bar drops, or when the level ends. What you get is a bed; the layering, the stingers, and the transitions are still your job, and they are usually done in the engine or in an audio middleware tool rather than in the model. Generate the beds, then treat them as the raw material for that system.

The practical consequence is that briefs should be written per state rather than per level. "Desert level" is one track that has to cover exploration, tension, and combat and does none of them well. "Desert exploration, nothing chasing the player yet" and "desert chase, drums forward" are two runs, two prices, and two beds that cut between each other cleanly because they share instrumentation and tempo — which is worth saying in both briefs.

The three models and what they cost

Suno v5 and v5.5 are both $0.20 per run; MiniMax Music is $0.40 per run and has a different sound. All three go through Actionway's music and sound capability, which sits next to the speech services — so a cue, a barks pass, and a trailer voiceover come out of the same session and the same wallet, with each run itemised.

At these prices a whole soundtrack is a rounding error next to the rest of a project. Five cues, two candidates each, is ten tracks for $1.00 for 5 runs at $0.20 per run — which is why the useful discipline is not saving money on runs but keeping the briefs specific enough that you can tell the takes apart.

Running it from Codex

Set it up once

npm install --global @actionway/cli@latest
actionway init
mkdir -p "$HOME/.codex/skills"
cp -R "$HOME/.actionway/skill/actionway" "$HOME/.codex/skills/actionway"

You need Node.js 20 or newer and an Actionway account. Claude Code users copy the same folder into ~/.claude/skills/actionway instead, and both routes reach the same catalog and the same wallet — the get started page lists the steps per client side by side.