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.

Nope, didn't help or harm in the slightest. As I said, going back to what I was doing before, this exchange was pointless.

Alright, got the name-calling tantrum out of your system? I'll go back to doing exactly what I was doing before, now.

Damned conservation laws.

Oh no, one fewer shines for neo-Nazis to worship at!

Okay. So presumably you now feel happy.

What does using that word change about the practical matters being discussed here? Any effect at all?

There's a fine-tuned version called Swift that's been trained to use 58.3% fewer reasoning tokens, apparently with almost no loss of quality. I've not been in a hurry with my personal usage (I set my coding agent loose on a task and then go have tea or whatever) so I haven't experimented with it much but it might be worth checking out if the verbosity of reasoning is a problem.

Qwen4 will be coming out soon too, it has a 27B version, so perhaps they'll have incorporated more efficient reasoning into it from the start. I'm looking forward to testing it out.

Ooh, this looks fantastic. My first thought was "doesn't this just move all the costs to the relay?" But the relay has a 30-day retention limit, so that'd keep storage costs well under control there.

Heh. I use Qwen3.8-27B as my main coding agent, and I sometimes feel really bad for it as I watch the stream of thought go by filled with "wait... am I doing this right? What if I'm completely wrong about this? Is this really what I should be doing??" I want to pet it and assure it that it should have more confidence in itself. :)

But it's the tradeoff that Qwen made to cram that much smarts into such a small bundle of parameters, I guess.

If they pay you money then you can exchange that money for huge amounts of raw meat, if that's what you really want. :)

Oh, I'm sure you wouldn't love to look at it. :) It's not exactly messy, AIs are good at keeping things tidy, but everything about it is ad-hoc. It was never intended to be seen my another mortal's eyes than mine. I don't think there are any API keys or other secrets tucked away in the repo's history but I'd rather not risk it.

Your mess of files is different from my mess of files and the things you'd want to do with them is different from what my code does, I'd suggest getting your own agent on the task from a blank slate. That's the whole point I've been arguing here, that coding agents make these kind of bespoke "home-cooked" applications a lot easier to spin up.

As I recall, my first steps weren't even to have the coding agent write code. I explained my general goal and told it to look through the folders itself to see what work it thought needed doing. That was how I learned that almost all the cover art I'd downloaded from Udio years ago was actually AVIF format that had just been given the file extension JPG, for example - I didn't even know that needed to be fixed.

Make sure you back up your files before turning an AI loose on them, of course. Mine's been very well behaved (I warned it that avoiding data loss was the most important priority) but mistakes can be made.