AbletonGPT is now Yuma

AbletonGPT is now Yuma. It's the same product: same app, same team, same account, same credits, same Ableton integration.

AbletonGPT, and now Yuma, are built to be the most powerful AI integrations with Ableton Live. The reason is simple: Yuma doesn't stop at generating a file. It connects to the Ableton set you have open, reads musical context, writes clips, works in Session View and Arrangement View, places audio, draws automation, and keeps everything editable inside the DAW.

The name changed because the product grew past the old name. Ableton is still the deepest integration. Yuma now also makes MIDI, vocals, samples, drum kits, and preset files you can use in Logic, FL Studio, Pro Tools, Bitwig, or any other DAW.

Short version

If you were an AbletonGPT user:

• Use the same account. Your email and password still work on Yuma.
• Keep the same credits. Active plans and pre-purchased credits carried over.
• Look for Yuma in Ableton. The Remote Script now registers as "Yuma" in the Control Surface dropdown.
• Re-run the script installer if Ableton can't see it. The one-click installer in the desktop app puts the script in the right folder.

Every customer who purchased AbletonGPT before the rebrand also received 4,000 free credits during the migration.

What's new since AbletonGPT

The name changed from AbletonGPT to Yuma across the app, website, installer, and Remote Script. The product also became broader and more practical for real production work.

The important technical detail is the Remote Script folder. The old folder was named AbletonGPT. The new folder is named Yuma, and Ableton lists it as "Yuma" under Control Surface.

That only affects people who installed the old script by hand. If you used the in-app installer, the desktop app can repair the setup for you.

The bigger product change is what Yuma can do with the connection. AbletonGPT started as a direct AI layer for Ableton Live. Yuma keeps that core and expands it into a fuller music production assistant.

Area	What AbletonGPT started	What Yuma is building now
Ableton connection	Remote Script control surface	Deeper Session View and Arrangement View workflows
MIDI	Generate ideas and clips	Write MIDI into the set with better session awareness
Audio	Generate sounds	Save vocals, samples, and effects as normal WAV files
Automation	Early parameter control	Clip automation for filter sweeps, volume rides, panning, and device movement
Drum kits	File generation	Sample folders, manifests, and Ableton Drum Rack assets
Instruments	Prompt-to-music experiments	More native Ableton device and preset workflows over time

That is the shape of the product: chat that produces real DAW objects instead of disconnected demos.

What stayed the same

The product carried forward. Yuma is still the AI assistant that sits next to your DAW and helps you make music from chat.

• Accounts: same login.
• Plans: same active subscription.
• Credits: same balance, plus the 4,000-credit migration grant for early paid users.
• Files: anything generated before the rename still belongs to you.
• Ableton control: Yuma can still read your session, create clips, write MIDI, control playback, and work through the Remote Script.

Ableton is still the center

Yuma supports portable files because music production doesn't happen in one app for everyone. Producers use Ableton Live, Logic, FL Studio, Pro Tools, Bitwig, Reaper, hardware, sample folders, and plugin presets. A serious assistant needs to make assets that travel.

But Ableton is still where Yuma goes deepest.

Inside Ableton Live, Yuma can work with the open set instead of treating the DAW like an export destination. That means it can read tempo, track context, clips, devices, and playback state, then write back into the session.

Session View

Session View is where a lot of producers sketch. Yuma is useful there because it can create and edit musical ideas without making you leave the grid.

You can ask for:

• A drum clip on the selected track.
• A bassline that follows the current chord idea.
• A melody variation for the next scene.
• A clip that matches the tempo and length of the session.
• A quick playback move while you listen.

This is the old AbletonGPT idea at its best: chat next to the session, with the assistant aware of what you're building.

Arrangement View

Arrangement View is where ideas become songs. Yuma is getting more useful here because generated audio can become an actual audio clip on the timeline. The file stays visible in your Yuma folder, and the clip can live in the song.

That matters for vocals, samples, impacts, risers, one shots, textures, and sound effects. When Yuma makes an audio file, the file can live in ~/Documents/Yuma/Audio, and Ableton can place generated audio on an Arrangement audio track.

Arrangement is also where automation matters. A loop can sound fine for eight bars, then fall flat because nothing changes. Yuma can now help write movement into clips: filter sweeps, volume rides, panning, and other parameter moves you can keep editing in Live.

Native Ableton objects

The best version of Yuma creates objects Ableton understands: MIDI clips, notes, automation envelopes, audio files, Drum Rack assets, and presets. You should be able to keep producing after Yuma helps, with the session still feeling like your session.

That is why the product direction includes more native Ableton instrument and device work. If Yuma helps with a bass, pad, rack, drum kit, or effect chain, the result should land as something you can open, edit, save, resample, or replace in the DAW you already use.

What former AbletonGPT users should do

Most users only need to sign in.

If you still have the old desktop app installed, download the latest Yuma build from your account. If you had a manually installed AbletonGPT Remote Script, run the Yuma installer from the desktop app so Ableton sees the new control surface name.

After the installer runs, fully quit Ableton Live and reopen it. Then go to Preferences, Link, Tempo and MIDI, and choose "Yuma" from the Control Surface dropdown.

Your account does not need a migration form. Your plan and credits are already on the Yuma account tied to the same email.

If Ableton can't see Yuma after updating

This usually means the old manually installed AbletonGPT folder is still on disk.

Fix it like this:

1. Open the Yuma desktop app.
2. Run the one-click Remote Script installer in setup.
3. Fully quit Ableton Live.
4. Reopen Ableton.
5. Go to Preferences, then Link, Tempo and MIDI.
6. Pick "Yuma" in the Control Surface dropdown.

Ableton has to fully restart before it sees a newly installed control surface.

Why the new name

AbletonGPT described the first version. Yuma describes the product we're building now.

Yuma is still the same AI Ableton integration that people found through AbletonGPT. It is also becoming a larger music production assistant: a desktop app that can control Ableton, generate usable files, organize assets, and help move a musical idea from prompt to session.

The name needed room for that.

Same product. Better name. Bigger direction.

Sign in to Yuma or create an account.