Yeah, we're here. I'm a professional programmer but I haven't written an actual line of code in quite a while now, and I've been having so much fun with my local model (Qwen3.8-27B Q4) doing all sorts of cleanup tasks on my lifetime's giant pile of accumulated files. For example, all my generated music - I ended up having Qwen build a GUI music manager and whipped up a website generator for my favourites so I can more easily share them through free hosts without having to hand them over to spotify or whatever.

I'm curious, is the game you mentioned modding Rimworld? I've been pondering modding it for some time now, it's one of my favourite games, if you've got experience using AI for that I wouldn't mind some pointers. It was always a "I know how to do this stuff but it takes way more time and attention than I've got available right now" sort of task but AI can help so much there. :) Your description of the "engine changed but compatibility is remarkably good" matches what I've seen of Rimworld's recent 1.7 update.

It was indeed a good day.

It later got squandered, sure. But that day was good.

Hey, at least Alberta's UCP lets you look at your conservative party and think about how much worse they could have been.

Alas, "the least-worst candidate who had a plausible chance of winning" is generally the best outcome for most democracies.

Don't let the perfect be the enemy of the good. Or the "well he's okay I guess", in this case.

So the good guys won but didn't win hard enough for your tastes.

Just take the W and have a nice night. Now there's an opportunity for improvement, that's a good thing.

The Alberta separatists getting brutally stomped on last week was also very nice.

Let's see how the American midterms go now.

On the plus side, from what I've read they're mostly old fashioned sane conservatives rather than Trumpian lunatics. Some of them are on the far right edge but hopefully the rest will keep them in check, the party's actual policies aren't too bad.

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.