MagickML

BabyAGI in Magick. I'll work on a better video soon walking through the graph. But so stoked that Magick is finally in a state where I can do this. And this is only the beginning.

We have sub-spells. Nested graphs are coming to Magick. The next step will be sub-spells as tools. The socket inputs and outputs on the sub-spell are given descriptions, and we can transform them into tool schemas. Then we parse and call the sub-spell, returning the result. This is going to open up all kinds of possibilities.

Another dev log since it has been a while. I did some work under the hood on the runtime engine underneath Magick. These changes have allowed me to run a dedicated engine instance per spell and finally implement the "on tick" event. The Magick Engine runs similarly to a game engine at 30FPS. You can tie into this runtime using the on-tick event which is called once per frame. This lets us do some pretty wild stuff. This first test was simply seeing if I could shuttle a message from the onMessage event over to the core loop using a basic string variable. However, we could likely use an array variable for this and create a simple queue system. Under the hood, these changes to the engine essentially mean that different event channels can have dedicated engines running on them continuously. I previously underestimated the power and performance of a single engine as an even processor and so missed out on these possibilities. Now that the functionality is there, I will be starting to implement more complex systems with an ongoing cognitive loop designed to process and think. I have some ideas next to experiment with as well to make some improvements to my original BabyAGI implementation in Magick to create different looping processors for tasks and queues.