SuperAPI AI Directory

soundcraft-editor

General & other

View repository

Updated 11-04 23:02

About this skill

soundcraft embedded editor
  1. From the tool list of the currently loaded plugin, find the soundcraft-editor service. Call it with the absolute path of this task's workspace: open_editor, passing workspaceon the first call; relative file paths can be handed to the specific open tool once the editor is ready.
  2. Render ui://soundcraft/panel.htmlwhen the host supports native MCP Apps. A text-only tool result does not mean the interface has opened.
  3. When Codex does not automatically present the panel, call open_browser_editor, and hand the returned editorUrl to the host's built-in browser opening capability. Codex Desktop can call open_in_codex, with target set to browser and url set to the actual return value. Do not guess a fixed port for the local page path.
  4. Open only one editor page per instance. Call editor_status, and wait until attached or ready is true before proceeding; if loading fails, handle the page error first.
  5. All editing in this round uses the same service. The native CLI and the Web editor are not the same in-memory document; you must save and explicitly reopen before switching.

Use open_session/new_session to manage sessions; import_audio to import, inspect_session to inspect, check the live tools for other edits; save_session to save the project, bounce_mix to output audio.

If the host supports only MCP, tool-calling capability and the embedded UI are two different things. You can use the same editorUrl in an external browser, but you must clearly state that this is not embedded-in-host acceptance.

When the development candidate is missing ui/dist/adapter.mjs , you need to build it first according to plugin ui/README.md . Do not guess paths from arbitrary caches, and do not bypass validation. This skill's standalone installation does not include the editor service; you need to install the companion plugin or configure its MCP backend.

When the tool is not registered, once you have the plugin's actual directory, you can run node ui/dist/adapter.mjs --servein the project terminal, specifying this task's workspace via the environment variable CRAFT_WORKSPACE_ROOT . Keep that process alive; this mode can display the UI, but automation must still connect to the corresponding MCP instance and must not start a separate backend claiming to share the session.

When done, save the project and reopen it to check; read the actual exported file. Browser storage, preview screenshots, and submitted render jobs do not count as workspace delivery.