Prepare AI-assisted song batches, manage multiple workspaces, monitor or recover automation, and export SongJob files into the MAGLAB pipeline.
Price
$119
One-time · 2 devices
Program 01 of the MAGLAB pipeline turns a brief, reference or structured recipe into reviewable lyrics, styles and titles, then controls a visible per-tab queue on Suno. Export a stable SongJob for MAGLAB Song Downloader and LongPlay Studio without putting full lyrics, style prompts or secrets in the handoff file.
API keys and extension settings are stored locally in Chrome. When an AI feature is used, the required prompt or song content is sent only to the AI provider selected by the user. Pro activation sends the license key and a device identifier to the MAGLAB licensing service only to verify entitlement and device limits.
References to Suno are made solely to describe compatibility. MAGLAB Music Automation is an independent product and is not affiliated with, endorsed by, sponsored by or officially connected with Suno.
1–50
Quick planning
1–1,000
Album planning
10
Files in the visible queue
5
Prompt languages
These are extension workflow limits, not guaranteed generation counts. Real output remains subject to your plan, quota, rate limits and the terms of Suno and each AI provider.
PROGRAM 01 · MAGLAB PIPELINE
01 · PLAN
Use AI GEN to prepare lyrics, a Suno-safe style prompt, title and advanced settings, then review the output before anything is added to a run.
02 · RUN
Bind the run to the exact Suno tab and workspace. Follow each item through progress and activity logs, or stop before another action is committed.
03 · CHOOSE YOUR AI
Configure the provider and model you want. Credentials stay in extension-local storage and are never included in SongJob exports.
MAGLAB MUSIC AUTOMATION
Prepare and review song recipes in a visible workspace before starting automation.
Monitor progress and diagnostics, then stop or recover work without losing the queue.
Use the cloud, local or OpenAI-compatible provider that fits your workflow.
QUICK START · FOLLOW EACH SCREEN
Every image is based on the real extension interface. Follow the sequence and validate one test song before scaling into a batch.
STEP 01 · INSTALL
Use Chrome 116 or later. Install from the Store when the listing is live, or load unpacked 4.2.6 from the delivery email after buying Pro, then pin MAGLAB Music Automation.
✓ Before starting, verify the exact account and workspace you intend to use.
Install from Chrome Web StoreThe Chrome Web Store listing is still under review. Pro buyers can load unpacked 4.2.6 from the delivery email right away.
If the install button is disabled, leave Guest/Incognito mode and reopen the link in a regular Chrome window.
chrome web store
Sign in
MAGLAB Music Automation
maglab-ai.com
Open the Chrome Web Store listing
Verify the publisher and details, then select Add to Chrome.
Add MAGLAB Music Automation?
Chrome shows the permissions the extension needs before installation.
Confirm the installation
When Chrome asks for confirmation, select Add extension.
MAGLAB Music Automation
Ready to open the side panel
Pin it to the toolbar
Open Extensions and pin MAGLAB Music Automation for quick access.
READY TO START
Open a supported work tab, then select MAGLAB to begin setup.
STEP 02 · CONNECT AI
Open API, select a language, provider and model, then add your own key or use a configured local provider.
✓ Cloud API usage may be billed separately by the provider you choose.
STEP 03 · PLAN
Quick is designed for 1–50 songs. Album plans larger runs up to 1,000 songs with split files and resume support.
✓ Start with one song to validate language, format and output quality.
STEP 04 · REVIEW
Select approved prompts, choose Fixed or Variation, and confirm the song count before generating a .md file or adding work to the queue.
✓ Runner style prompts must remain within 1,000 characters per song.
STEP 05 · RUN
Return to CREATE, import .md, .txt or .json, review each title, lyric and style, then bind the run to the intended tab.
✓ If the tab or workspace is wrong, stop and select it again before continuing.
STEP 06 · HANDOFF
Choose a friendly Project, Production Channel and Volume, then export a SongJob JSON that preserves the work's identity.
✓ SongJob excludes full lyrics, full style prompts, API keys, tokens and cookies.
Best for drafting a set, testing a direction or preparing a batch that needs item-level review.
Best for large-project planning, estimating scale and structuring work before provider resources are used.
SONGJOB · LOCAL ARTIFACT HANDOFF
Choose a friendly Project, Production Channel and Volume. Stable job and song UUIDs let Downloader and LongPlay identify the same work without guessing from filenames.
Cloud APIs may charge separately. Local providers are installed and maintained by the user. MAGLAB does not place provider keys in the content script or SongJob.
Keys are stored in extension-local storage and external requests are orchestrated from the service worker.
Review the selected tab, workspace and item before a Create action that may consume credits.
The currently published runtime has no quota counter, trial lock, Pro activation or device entitlement.
Send MAGLAB your song count, input format and current workflow for a practical review.
No. Program 01 prepares and controls generation. Export the SongJob and use MAGLAB Song Downloader for owned-media download and packaging.
Quick planning supports 1–50 songs and Album planning supports up to 1,000. The visible import queue accepts up to 10 files; actual generation remains subject to Suno and provider limits.
Cloud providers use credentials you supply. Local providers such as Ollama or LM Studio can be configured instead. Provider charges are separate from MAGLAB.
Yes. Free includes the existing preparation, AI, editing and SongJob tools, and can complete 10 verified song creations per Chrome installation. Pro is a one-time website purchase that unlocks unlimited automation on up to 2 devices. Paste the license from the delivery email into LICENSE, then Activate this device.
Stable project, channel, volume and song identities plus allowed matching metadata. It intentionally excludes full lyrics, full style prompts, API keys, tokens, cookies and authorization data.
