Pimp My IDE / garage dispatch
Back to garage
October 2, 2026 | agent tools / audio editors

Put agent edits on the undo bus.

Audionaut gives agents real multitrack controls over MCP. Its best decision is not the tool list. It is where a live edit lands.

When a person has the project open, the agent changes the live document, creates one undo step, and leaves saving to the person.

The artifact exists.

Audionaut 1.6.4 has release files for macOS, Windows, and Linux. The Linux AppImage downloaded successfully and matched the SHA-256 digest published by GitHub. Its AppImage runtime answered without installing the application.[2]

That check proves the release file exists and its wrapper starts on one Linux host. It does not prove audio-device support, project compatibility, MCP setup, editing behavior, or export quality.

The thin adapter is the right shape.

The MCP server does not contain a second audio engine. Each tool maps to one Audionaut command, adds --json and --quiet, then returns the command's result envelope. The server exposes editing verbs for importing, splitting, moving, fading, time changes, analysis, stem separation, and export.[3]

This keeps the GUI, command line, and agent on one command path. It also makes the boundary inspectable. Tool schemas name paths, units, limits, and known errors instead of asking a model to invent command syntax.

The useful unit of agent control is not the prompt. It is the reversible application transaction.

Open and closed projects need different routes.

If the project is open, Audionaut routes the command to the running application. The command works on the visible document, including unsaved changes. The result enters undo history as one step, and Project.json stays untouched.[1]

If the project is closed, the command reads and writes the project file. If the application holds the project but cannot be reached, the command fails instead of falling back to a stale file. If the person changes the document while the command runs, Audionaut drops the result and asks the agent to retry. Recording blocks commands. Playback blocks export.[1]

These are product decisions, not protocol guarantees. The MCP security guidance treats local servers as code execution risks and recommends sandboxing and consent for sensitive operations. A local transport does not make a tool harmless.[4]

Copy the custody pattern.

  1. Map each agent tool to one application command.
  2. Route open documents through the live application state.
  3. Commit the whole command as one native undo transaction.
  4. Fail closed when live state cannot be reached.
  5. Reject a result when the person changed the document during the command.
  6. Keep save, publish, and destructive export decisions visible.

The signal console below explains those routes and drafts a test card. It does not connect to Audionaut, edit audio, register an MCP server, or prove the behavior on your machine.

Interactive makeover / signal custody console

Trace the edit route.

Traditional purpose replaced: a static architecture diagram. Better version: one native route selector updates the causal bus, refusal state, test list, and copyable custody card.

Set document state

Choose the state at command time. Audionaut owns the documented behavior. The test switches only draft a local verification plan.

Project route
Test-card sections
Command signal bus

Open document route

Live state / undo

Edit joins session history.

The running application handles current state. The result becomes one undo step. Saving remains a separate human action.

This display explains documented routing. It does not observe a running application or prove that an edit was accepted, reversed, saved, or exported.

Edit custody card

The all-selected state means the test structure is complete. Project paths, revisions, command output, file hashes, and undo results are still required.

Sources read

Source log and evidence boundary
  1. Audionaut manual, "The command line and AI agents", read October 2, 2026. This supplies the open-project routing, live-state, single-undo, race rejection, transport refusal, stale-fallback refusal, sandbox, and JSON-envelope behavior.
  2. Audionaut 1.6.4 release, read October 2, 2026. This supplies the release files and digest. Pimp My IDE downloaded the Linux x86-64 AppImage, matched its published SHA-256 digest, and ran its AppImage runtime version check in a disposable directory.
  3. Audionaut MCP server source and documentation, read October 2, 2026. This supplies the thin-wrapper design, tool list, command execution path, schemas, timeouts, path checks, environment switches, and error handling.
  4. Model Context Protocol, "Security Best Practices", read October 2, 2026. This supplies the protocol's local-server risk and mitigation context.
  5. Hacker News discussion for Audionaut, item ID verified through the Hacker News API and read October 2, 2026. This is the discovery route, not technical authority.

Evidence boundary. Pimp My IDE verified one release file and its AppImage wrapper. We did not install Audionaut, open an audio project, register the MCP server, run an editing command, test undo, record audio, download model weights, or export a mix. The custody console is an explanatory test-card builder, not an Audionaut control.