Ablegent

Make your first change in Live

Ablegent turns a clear request into a concrete change in the Live Set open on your Mac. It inspects your Set, makes the requested move when it can, and tells you what changed or what stopped the work. Start small, listen back, then ask for the next move.

First run

  1. Open Ableton Live 12 and load the set you want to work on.
  2. Start Ablegent from the Applications folder.
  3. Find Ablegent in the macOS menu bar. It lives there, not in the Dock.
  4. Show or hide the chat panel from the Ablegent menu bar icon.
  5. Confirm Ablegent shows Live as ready. If setup or connection needs attention, follow the visible setup step first.
  6. Ask for one clear production move tied to the current set.
  7. Give the first prompt a little time while Ablegent reads the set.
  8. Review Ablegent's summary and play the changed section in Live.

Good first requests

  • Turn the 8-bar loop into a 45-second intro and first drop.
  • Create a cleaner drum scene from the clips already in this set.
  • Lower the harsh synth layer and stage the master bus with more headroom.
  • Add automation so the pad opens up across the build.
  • Check why this set is silent and fix the routing if it is safe.

Avoid vague first prompts

  • Finish this track.
  • Make it professional.
  • Make a hit.
  • Do whatever sounds best.

Prompts that keep you in control

  • Ask for one move at a time when control matters.
  • Point to the part of the set Ablegent should change: track names, scene numbers, bar ranges, locators, clips, or devices.
  • Say the intended direction, not only the tool operation: "make the transition less abrupt" is more useful than "add automation" by itself.
  • Name constraints up front: keep the bass, avoid changing drums, preserve the vocal timing, or do not add new instruments.
  • Use Ablegent for setup and repair work too. Routing, silence, gain staging, scene cleanup, and export prep are valid tasks when they are the next useful move.
  • Save important versions before destructive or broad changes.
  • Stop and retry with a narrower request if the result moves away from your intent.

Before the session

Use an Apple Silicon or Intel Mac running macOS Sonoma or newer with Ableton Live 12 (non-Trial, non-Beta) installed. Ablegent is built for Ableton Live in English at launch; other Live UI languages may degrade the experience.

Open the Live Set you want to work on before asking Ablegent to change it. Save the set first if the work matters, especially before arrangement, routing, device, or export-prep changes.

Ablegent's local tools work with Ableton Live on your Mac. Cloud services handle account access, usage, updates, and model access. Raw musical material stays local.

Plans, credits, and limits

Ablegent Core gives you the Ablegent app, setup, updates, diagnostics, and support while using your supported ChatGPT/Codex account for model access. Core does not include bundled Ablegent AI credits, Ablegent usage windows, or credit packs. Free ChatGPT plans and API keys are not supported.

Ablegent Mini and Ablegent Pro include bundled Ablegent AI credits. A credit is an Ablegent usage unit, not a token, dollar amount, or fixed number of tasks. Simple requests usually use fewer credits; larger workflows use more.

Mini and Pro usage is account-level. If you connect Ablegent on more than one Apple Silicon or Intel Mac running macOS Sonoma or newer, those installs share the same account credits and limits.

Mini and Pro have bundled plan windows for monthly, 5-hour, and weekly usage.

Credit packs are one-time top-ups for the matching bundled plan. Mini packs work with Mini, Pro packs work with Pro, and Core cannot use packs. Matching pack credits can keep requests moving after those bundled plan windows would otherwise stop new requests.

Pack credits extend credits you can still use after bundled plan windows would otherwise stop new requests.

Your account page shows current plan usage, remaining credits, pack credits when present, and the short-window percentages. If Ablegent stops because a limit is reached, add a matching credit pack where eligible, wait for reset, or change plan.

Safety

Ablegent runs in a sandboxed local environment. It does not browse your personal files or use the open web. When it needs reference material, it uses curated Ablegent resources.

Ablegent works through Ableton Live and changes only what the task requires. It does not overwrite or save a Live Set unless you explicitly ask it to. If a request needs broader access or a risky action, Ablegent should ask, explain what stopped it, or fail instead of guessing.

AI can still make mistakes. Back up critical work, keep important versions, and check the changed section in Live before you build on it.

Ablegent lives in the menu bar

Ablegent is a menu bar app, not a Dock app. That keeps it close to Ableton Live, but it may feel disruptive if you keep a minimal menu bar or avoid always-available helper apps.

Use the Ablegent menu bar icon to show or hide the chat panel. Quit Ablegent from the same menu when you are done with a session or do not want it available in the background.

You can also show or hide the panel from the keyboard. The default shortcut is Control-Shift-F1. Change it in Ablegent Settings under "Show or hide chat" if it conflicts with your Live setup, keyboard, or other Mac shortcuts.

Full-screen Ableton Live is supported. The chat panel stays on top, so you can ask for changes without leaving Live.

You can keep working in Live while Ablegent is running. If you edit the same tracks, clips, devices, or routing Ablegent is trying to change, it may adapt to the new state or explain what stopped it. That is recoverable. Avoid changing the exact target of a running task unless you intend to redirect it.

If you use more than one display, open the panel from the display where you want it to appear. To move the panel to another display, close it, move your pointer to the intended display, then use the Ablegent menu bar icon from there.

Ablegent does not provide a chat history or chat selector. The visible chat is the active working context. Use "New conversation" from the menu bar when you want a fresh context; the current chat is left behind and the new chat becomes active.

Create a new chat when you change songs, start a different version, abandon an old direction, or want Ablegent to stop carrying assumptions from earlier requests. Stay in the same chat when you are refining the same production move, asking follow-up questions, or building on the result Ablegent just made.

The first prompt in a new chat may take longer while Ablegent gathers context from the current Live Set. Follow-up prompts in the same chat are usually much faster because Ablegent has already done that initial inspection.

Link Set keeps a saved Live Set attached to the right Ablegent chat. When you reopen that Set, Ablegent can bring the matching chat back instead of mixing context between songs, versions, or client projects.

When Link Set is on, Ablegent checks the saved Live Set you are working in. If that set is already linked to a chat, Ablegent can resume it. If the set is new to Ablegent or linked somewhere else, Ablegent asks before it uses this chat, starts a new chat, switches to the linked chat, or continues without a link.

Starting a new chat while Link Set is on can link the new chat to the current saved set after confirmation. Starting a new chat while Link Set is off, or while the set is unsaved, creates an unlinked chat.

Only saved Live Sets can be linked. Unsaved sets do not have a stable file identity, so Ablegent treats them as unlinked. Save the set first if you want Ablegent to remember which chat belongs with it.

Link Set decisions appear above the composer, not inside the transcript. Your draft text stays editable and is restored after the decision. Ablegent does not send a draft, switch chats, or link a set without an explicit choice.

Turn Link Set off if you want every new chat to stay independent of the current Live Set.

Steer while Ablegent is working

When Ablegent is already working, the composer changes from "Ask Ablegent" to "Steer Ablegent." Use Steer to correct the current task before it finishes: narrow the target, stop it from changing a track, point it at a better section, or add a constraint.

The composer holds one message at a time. A normal ask, a draft, and a steer message all use the same composer. If you have a draft in the composer and start typing a steer message, you are replacing that draft. Send or clear anything you want to keep before steering a running task.

After you submit a steer message, the composer holds that text until Ablegent accepts it, fails it, or you stop the turn. If the steer succeeds, the composer clears. If it fails or you stop during steering, Ablegent restores the text so you can revise or resend it.

Read it, then listen

After each task, Ablegent should name the useful change, the Live state it observed, and any caveats. Look for concrete details: tracks, clips, devices, routing, locators, meters, snapshots, or setup checks.

If Ablegent says it could not complete a task, treat that as part of the result. The reason should be specific enough to act on: Live was not ready, a device was unavailable, a route was unsafe, account access failed, usage ran out, or the request needed a clearer target.

Do not rely on text alone for musical judgment. Play the changed section in Live. Keep what works, undo or revise what does not, and ask for the next specific move.

Learn Live from your Set

Ablegent can help you learn Ableton Live concepts by explaining them and showing examples in the set in front of you. It is not a full Live course or a replacement for your own taste, but it can make unfamiliar production moves easier to inspect.

Direct learning questions

  • “What is gain staging? Show me an example.”
  • “What does a return track do? Create one I can inspect.”
  • “What is automation? Add a simple filter movement to this clip.”

Guided practice

  • “How do I create a return track? Explain step by step and let me do it.”
  • “How do I automate this filter by hand?”
  • “How do I check whether this track is clipping?”

Make a small change and explain it

  • “Create a return reverb and explain how the routing works.”
  • “Fix the gain staging on these tracks and tell me what you changed.”
  • “Build a simple automation curve for this filter so I can inspect it.”
  • “Arrange this loop into two scenes and explain why each scene is different.”

This works best when you ask for one concept at a time: routing, scenes, automation, device chains, clip organization, gain staging, arrangement sections, or export prep. After Ablegent finishes, inspect the changed tracks, clips, devices, or locators in Live, then ask a follow-up if something is still unclear.

For learning, ask for an example when a concept feels abstract. Ablegent is strongest when the explanation is tied to visible state in your current Live Set.

Keep Ablegent fresh

Keep Ablegent up to date from the menu bar icon: choose "Check for Updates...". Updates do not install silently; follow the prompts when Ablegent finds one.

Thanks for trying Ablegent. A lot of work went into making a small app that can read a real Live Set, make useful changes, and show what happened while your taste stays yours. Ablegent will keep getting sharper as the app, setup flow, and Live tools improve. Send bugs, help requests, and sharp suggestions to support.

Contact support

Use the in-app support form from the Ablegent menu bar icon when setup, connection, account access, a repeated stop, or a suggestion needs a reply. It collects the details support needs without asking you to send Live Sets, samples, audio, MIDI files, screenshots, or other musical material.

Need help? Contact Support.