On Sunday night an agent built me a techno loop and said: "I haven't heard it, so your ears decide whether it's good."
That's been the deal with agents for the last two weeks. They do the work. I listen, I look, and when something can't be undone, I press the button.
The agent had warned me at the start: "One limit up front: I can't hear audio." I didn't have a DAW either. I told it to set up everything it needed and "let's get onto cracking something". Ten minutes later there was a 32-second loop.
"Okay, not bad, not bad," I told it. Then the notes. Whatever was in the background, "like the... oscillating?", was "a little sharp". I wanted vocals, and three minutes. Just after eight it played me "Hold Me Under", dark techno with a sung vocal it had generated and cut into place. The voice "overpowers after the intro". When the first chorus came in, the bass "thumps but feels... muddied?"
Each time it went and found out why. The sharp thing was a rim shot made of two pure sine pings. The mud was three things at once. One was the kick and the bass sitting on the same F, with the kick ringing for nearly a full beat. It also admitted the "cleanup" filters it had been describing to me "barely did anything".
On 1 November I asked why stuff on our Minecraft server was stacking to two stacks. It found the cause in under a minute: a stack-size mod someone had added that day, which doubled everything to 128. The why came the next afternoon, from the admin: "I wanted a stacking potions mod, but it made me download 2 extra mods." It put normal items back to normal stacks, kept potions and stews stacking, and rebooted the server.
That evening I asked it for a Create gantry, for an automatic wheat farm. It put a test copy in my creative world. I flipped the lever and reported: "nothing seems to happen."
It told me to kick it. "So I broke the shaft, replaced it, flicked the lever off, on, off again." Then I told it to check the docs: "I think we might just need to glue it? But idk."
It had already told me glue wasn't needed. The problem was a row of grass on top of the shaft, which its test build hadn't cleared. One command cleared it, and a couple of minutes later I typed "Very nice! it moved."
My next note was about looks: "The gantry is visible now though. I do not like that."
On 28 October, a little after ten at night, the research server I rent stopped letting anyone log in. It had done the same that afternoon and come back by itself. This time it was full of jobs the agents were running for me, and it stayed down.
The agent working with me watched it for half an hour, then recommended a hardware reset. It said what that would cost: a run that had been going for about three hours, plus every other job on the box.
The hosting console said the server was running, so I asked: "Any idea when it'll come back on its own? Takes a few hours, or?" It said nobody could say, and maybe never. "Server is running" only meant the machine had power.
Then I opened the console in my browser and got stuck: "I just see reset.. rescue.. not restart." It took over the tab, found the right server, and told me Reset is the restart. It hadn't selected or sent anything. It said it could click it for me if I said yes.
The button was mine, as it usually is. "Clicked it.. send."
It came back at 23:15, with memory caps on the jobs and a queue so they can't all pile on at once. The three-hour run died in the reset. It had told me that before I clicked.
