Ah, the code itself won't really help with that.

My setup is: LM Studio running the local model Qwen3.8-27V, quantized down to Q4 with Q8 for the KV cache, on my system that gives me 128000 tokens context. The harness is VS Code with the Qwen Code Companion installed.

I opened the folder that has all the music I wanted to organize as a workspace, adding a git repository with all the actual music folders gitignored. This was the first prompt I gave the agent once all that was in place:

The folder you're in, and the subfolders inside it, are where I've been putting the music that I've generated using various AI music generation services (and my own local Ace-Step 1.5 model) over the past year or so. I've stored a lot of metadata (usually in a .json file) along with the music files themselves, along with lyrics in .srt and .lrc form, cover art, and so forth - different formats, different sources, not entirely consistent. I've decided that it's about time that I try to organize this all a bit better, and I'll be enlisting your aid. :)

[ A few specific paragraphs about the details of the filesystem layout omitted]

Before I explain the format the text files are in and how I'd like them to be converted, would you like to take a look around the folders to familiarize yourself with them and write whatever preliminary memories and notes you might want? And of course ask me questions about the stuff in here if anything isn't clear in its purpose or organization.

Then after it had looked around and had read the various different metadata formats, it asked me some questions about what data I'd like to have in "unified" metadata files for each of the tracks, file naming conventions, and whether I wanted it to do anything with the cover art and subtitle files. I answered the various questions (telling it to leave the cover art and subtitles alone for the time being) and it wrote some python scripts that ran through all the existing metadata to tidy up the stuff that fit existing patterns and create a list of all the oddball exceptions it ran across for me to fix manually. It found stuff like situations where the punctuation was different between music file and metadata file, where there were cover images with no apparent music associated with them, and so forth.

It became a back-and-forth exchange of me telling it what to fix and it finding new things that I didn't know needed fixing. Eventually I had enough random Python scripts to wrangle that I asked it to write a GUI, which made it much more convenient for me to edit the metadata by hand wherever needed as well.