Hey,
I am not telling you something new when I say AI is being rolled out basically everywhere and more often than not it is quite useful and can empower users. I was thinking about it would be neat to have a Claude connector / mcp simply because I use Claude myself the most but it could be any other AI provider. I imagine that this could be used to create graphs from scratch, optimize existing graphs, create plugins or code devices. In fact the latter I already used in World Machine together with Claude quite successfully and created nodes that didn’t exist before and probably would be a ton more work to build/code manually since I am not a coder.
For example I created a sand simulation device after Werner’s dune model or non-uniform directional warp and slope blur from Substance Designer, among others. Not everything works perfectly but I also didn’t invest a ton of time/tokens to be honest. I attached my file so you can check it out.
claude_worldmachine_playground.tmd (1.3 MB)
Are there any plans to integrate AI functionality in World Machine?
Kind regards 
2 Likes
First of all, very cool dune sim, I’m impressed!
Like it or not (and believe me, do I have some complex feelings on AI overall myself…), there’s no question that AI is here to stay and is incredibly useful. It really turned the corner about a year ago, and since then I’ve given some thought to how best to do exactly this.
I think it splits neatly into:
-
An MCP to Drive WM itself: Allow an agent to add devices, wire things, set parameters, and retrieve visuals of the result so it can inspect. This is the largest scope option.
-
More narrowly, add additional hooks and improvements to the Code device to let agents more easily author custom devices. This would include things like allowing all device setup to be done by an additional constructor script file, something that some people prefer for human generated devices too. This could be an MCP, or it could be things like mapping sourcecode to to actual files on disk and watching them so they can then be edited by the ai directly.
This will not appear in Dragontail, but there is the potential for it to appear in the succeeding named version next year.
3 Likes
Sounds great. If anything don’t let the code device die even if it always stays experimental, there is already so much cool stuff you can do with it using AI :). Improving it would be even cooler. Of course a full fleshed MCP would take the crown.
2 Likes
I agree about the code device! One of the major reasons why I wanted a fully sandboxed scripting language like lua is so that Code-authored devices can be freely shared without security concerns.
The macro library never took off the way I wanted, but I blame a big part of on how high-friction it was and still is to share and download macros.
Something that will be coming next year is a reboot of the macro library - except modernized and browsable from directly within WM. It will support ALL custom devices, whether they are macros or code devices.
So in the future if you write a cool new device, you can publish it right from inside WM. Users can find it by clicking the ‘Explore’ tab in the next-gen device library browser! This is also why I made sure that the library in dragontail has support for including an example world - it’s always been frustrating to download someone’s macro and realize you have no idea how they intended to have things hooked up.
3 Likes
Also sounds great, love it! Keep up with the great work
1 Like