I got what you saying and agree. Ive certainly get too entousiastic and should definitively have spend more time on the packaging before sharing it.

If i endedup doing like this is not bacause of lack of interest of willing todo but lack of time and different perspective i guess.

I'm working with LLM every day and all the time and i'm actually not working like i was a few years ago. I dont valuate good documentation or deliveryr that much where i will not integrate things by hand in a first place. I wont say you should do the same but that the way i work.

In another hand, the various things i published on reddit from now never aims to be like big gift to humanity but rather a way to get interest on tdmcp-rs which is the thing i've actually spend a lot of time on it and its a good tool imap, what i shared is just a demo, not an habile one apparently

you awnsering to your own message is not a conv is what we call "vider son sac" in french

feel free todo whatever you want with your hands and if you want to discuss i'm here

100% true that why you need a well made MCP/tools so your agent can speak to td and curated skills/documentation so he wont guess

If you get comfortable with any harness (claude code, codex ect) you should definitively give a shot to tdmcp-rs it can be game changer for many cases but its especially good at coding and does it whitin td rather than asking you to copy past everything

Its true but for your exact use i think what you missing is a proper integration of the llm inside td. Hallucinations ect are normal, think about your llm a person you call by the phone and ask him to build your python code. He have to do it anyway. He will generate you some piece of code, probably well oriented but nothing that can work w/o a few iterations and live testing in the real environment. What is missing here is the proper MCP to make your LLM see and play with the same tools then trust me he wont hallucinate much and even if it does, it will be able to correct and iterate w/o you in the loop and that where it starts beign usefull ;)

Hi, i agree with you actually even if it might not look like it. Yes i too hardly find any practical use of AI (i'm saying AI but actually speaking LLM) inside touchdesigner. But i'm also convinced its due to the absence of proper tool to do it.

Using chatgpt or equivalent is nothing close by what LLM can does with the proper harness and understanding of the system it plays with (td).

That why i've spend a good part of the summer building my own agentic integration/harness (not literally a harness but an extension for most cc, codex, dsh). This integration i made isn't going to get much interest until i spend some more time finishing the doc and making it available to no technical i think but its already really good at integrating into existing and trully understanding td (not just generating shaders) which is honestly game changer when you try to push boundaries of touchdesigner for some applications that would usually require thrid party sofwars ect.

For the ethic i have my own opinions on those but i'm also realistic: the whole internet get ingested into thoses long time ago and the only thing we can do about it is take advantages and make the tools our own instead of letting the big boys own everything (that again why i spend [..] you get the idea).

I agree and its probably the major reason why i love td and keep using it. Also i wont say its all black or white because here is a thing, i could also ask claude to write the full render from scratch or for unreal engine ect but i'm keep using touchdesigner for a good reason and that what you spoke about: beign able to see, tweak and understand. And imao it allows much more complexe system that i wont ever dreamed about if i willing todo it by hand and while understanding every piece of it.

i would like to know which brand of coffee you using then

Depending on how you see the thing: i'm sharing a tool that OK isn't the beast you wanted to pay 5e to get access to on patreon BUT I provide the gears you need to make the one that trully match your needs in a matter of minutes and for virtually free... if you rely on cheap LLM which you can do now that i published a fully open source integration that allow you using the tools that the world is getting crazy about...

as i said its a single prompt project and the point here is more to showcase tdmcp-rs than providing something trully usefull out of the box

yes it does, for the little story i've started the mcp because of multi-instances un-reliability with others available mcp, this is one of the main focus ;) (every tool call reference the target pid/machine and get synchronous response its not like you send a call and all td instance get it, the agent specify the target and that allows a world of possibility with the others studio automations -> you can ask an agent to explore your projects, dump interesting tox into a sandbox project and make a showcase for example but that just the surface it can do much more)

https://reddit.com/link/p72rmot/video/duo3e41uksmh1/player

A quick overview of what you can get using two simple prompt (first: do a glitchy effect that apply after a webcam in top. second: give 5 variations, impresse me)

https://preview.redd.it/64o54nxyjsmh1.png?width=2080&format=png&auto=webp&s=983f554cb28dd2766fd2615543481660e5f62fb3

Federation

https://preview.redd.it/bi5y7tsqjsmh1.png?width=2080&format=png&auto=webp&s=2574e938f1d0f95e00f4ce403a5218179cdc302a

Here is the palette GUI, dont get it wrong td-mcp-rs is a MCP but it came with a nice GUI to handle the complexe task of managing various td instances locally or over the network :)

Not sure to get your question quite right tbh but the way federation work is the following:
- On every machine you want to mesh you get the daemon running.
- There is a master and N slaves.
- From the master, touchdesigner process running on slaves instances are visible the same as local one/provide the same tools no difference for the agent.

I have to be honest i feel bad about what i said and afterward i think you where 100% right, i lost my way with generative AI and i acted like an ass hole... Sorry again for my bad attitude and as a signe of gratitude (and because the idea is cool) i've reworked the tool entierly so its 100% native to td/require a single tox for install. Still pretty young/not curated but already work fine in "simple scenario" :) u/itzelezti
(same repo as before)

https://preview.redd.it/u2d5sgd0tmgh1.png?width=1251&format=png&auto=webp&s=0e757e5a5a059d342aaf93827cd7aef9f7743da3

> Note: i will make a dedicated post once the tool is a bit more "polished"

Cursor won’t let you pick a custom model for subagents — so I built a bridge to OpenCode

Cursor’s native Task tool only schedules built-in models. If you want a cheaper / OpenRouter / OpenCode model for a background subagent, you’re stuck.

open-delegate is a small Cursor MCP plugin that hands the job to a real OpenCode agent instead: isolated session, your choice of model, await/status/transcript/cancel from chat.

Alpha — not on the marketplace/npm yet, but usable if you run it from source (tested on windows and macos) / npx once published.

Repo: https://github.com/Verbalize-public/open-delegate

Happy to take feedback / bug reports.

No need to be aggresive, at least i'm some how trying to be constructive. btw have you read the repo yourself ? i mean your comment arrive like less than an hour after my publication so i higlhy doubt you read anything by your own and can confidently say that you just geniumly reporting what an AI said (stop acting like an LLM yourself and try to use your own judgment might be a good start so people like me dont get anoyed)

Constructively, I don't really see what your comment adds to the discussion.

We're in a period where the way we build software is changing quickly, and I think it's worth exploring these new posibilities instead of dismissing them based on assumptions that were true five years ago but may not be true much longer. Some experiments will absolutely fail, some architectures will be disposable, and some ideas will turn into genuinely useful tools. That's how new paradigms usually emerge.

I also think it's important to separate the quality of a prototype's architecture from the value of an idea. This repo was never presented as a polished framework or production-ready codebase. It's an experiment shared publicly to gauge interest and iterate on a workflow that I personally already find useful.

For context, I'm not approaching this as someone who has never written software outside of AI tools. I've been a professional developer since 2018 (specialized in system development in RUST) and have been passionate about computer science since I was a kid. I'm well aware of the trade-offs and the technical debt in the current implementation. If this evolves into something worth maintaining, I'd happily redesign large parts of it rather than treating the prototype as untouchable.

If the architecture seems flawed, I'd genuinely be interested in hearing specific suggestions or alternative approaches. I think that would be a much more productive discussion than dismissing the project as "AI slop" and calling me with some fancy hyped word that actually means nothing.

I genuinely disagree. I think that perspective was absolutely right about five years ago, but the tooling has changed quite a bit since then

A couple of points:

• With Cursor (or similar) getting this running is often just a matter of a single prompt. The dependency pain isn't what it used to be.
• Even if you consider it an "AI slop" project, it still captures a detailed UX, workflow, and product idea. That's valuable. Spend a week with it, and you could turn it into a properly packaged application with a clean architecture.

I don't think every AI-generated repo is worth saving, but dismissing them entirely because the architecture is messy misses where the value often is today. The implementation may be disposable, but the workflows, UX, and product concepts frequently aren't.

Fair ! it get vibecoded in a bunch of days so your analyse is right, i'm sharing this in the current state to see if there is an interest and if it worth spending time on it (btw i'm already using it and find it usefull in the current state as a one shot scene editor, ofc not for live performances).

I just updated the repo due to weird edge case ^^' but i endedup with something stable finnaly (costed me a bunch of tokens)

there is the magic parsing/description that feel odd but it work pretty well (i was able to parse all my library w/o error) and i think its usable as it but next step would be testing bunch of ableton versions + OS interoperability maybe (i tested only on windows)

i did it using composer 2.5/cursor and a pretty simple prompt but with exit condition