Sorry ImageSharp
github.com/recursive-ai-oss/…
Survived 102s and dropped 53 kills (Berserker) at 82% accuracy in the 3D Minecraft Aim Trainer. Real Minecraft sensitivity, full-360 horde — beat it. mcrpg.com/minecraft-aim-trai…
Made a babysitter app for Alera, so one agent can babysit another and send me a message on telegram when it's done.
Agentic Operating System: Creating Minesweeper & FreeCell in Alera (Recursive AI) youtu.be/vKg34I_IkjY?si=cb2T… via @YouTube
I had an idea earlier this week for a self-improving AI architecture. I've been spending evenings this week designing it, and I finally had some time this evening to spin up 25 AI agents to build it.
This is actually an iteration on a project I built last summer. The original project is called Flows. It took me about 6 weeks to build it - and I still use it all the time. This new iteration, called Routines, is significantly more complex.
I spent probably 4 or 5 hours this week fleshing out the architecture for the project. I spent about 2 hours yesterday evening architecting the agent swarm to build it. Now I'm about 6 hours into managing the bots that are building the project. Essentially I'm checking in on them every 5 or 10 minutes, manually moving them through check points so I can keep tabs on the project.
Issues I've run into:
- I had to completely wipe the last module because the instructions the coding bot was given were pretty terrible. I had the master bot rewrite the instructions, and it performed vastly better the 2nd time
- The AI *loves* to write things like `// TODO: implement this`. I have to prod it to make sure it doesn't get lazy
- When writing the last module I realized a flaw in my architecture. This wasn't an AI error, but I had to go back and refactor one of the first modules to make everything work.
Aside from that, it's been pretty smooth sailing. The agents are still chugging along as I type this, doing their coding, testing, documenting, and reviewing loop. The end is in sight, though! It's currently working through the final integration tests.
Tomorrow I'll get to start building some routines and see if the architecture is actually effective. Tonight I'll sleep well knowing I didn't have to spend 2 months building this.
If you're a software engineer and you want to learn how to use those same techniques I'm using to spin up a bunch of agents to write code for you, shoot me a DM. I'm hosting a series of classes this month to teach engineers how to build and use their own AI tools.
Example of why "ai coding is slower" is stupid. #vibecoding #metaengineering
I have code writing a long list of products to a YAML file, which I will feed to an LLM. But, to help the LLM see those products as separate entities, I want a blank line between products in the YAML.
Me: 30 seconds to type a prompt
Agent: 5 minutes to write, build, debug, test
Me: 10 minutes to review, test, commit the code
Start to finish, we're 15 minutes in, for a feature with a tiny impact on the end result.
Made this: unclassified.news
It's a strategic conflict analysis site that aggregates news and information on the Israel / Iran conflict and does scenario analysis and strategic assessment of the situation.
LLMs are capable of so much more than writing CRUD code.
Just had a RecursiveAI Agent write enable headless agents on the RecursiveAI Agent platform. Took all of 5 minutes. Zero bugs.
The biggest mistake people make with AI is thinking it's plug and play and the results are what they are.
Kurtis Welch retweeted
Passwordless login (via email) *and* a place to store user data – with barely any lines of js. Looks… perfect?
uthentic.net/documentation/q…
I liked a @YouTube video youtu.be/J5_bnZX5CHA?a "I'm Scared," Songs About Emotions by StoryBots
Most unethical ad I have ever seen. "No intro offer" "No big promises" Blatantly contradicted an inch away. @GetSpectrum









