Agentic coding workflows

[Bart]

@Christoph-Hart So practically everything

Wow it's really nice.. Being able to modify the module tree and the interface components without scripting them, marvelous.. Enough to get me started - keep at it!

[David Healey]

@Christoph-Hart Is it possible to tell the AI not to do some of those tasks? I'm thinking tokens are expensive and I don't want to waste them on starting and quitting HISE :p

[dannytaurus]

@David-Healey That's probably not the level at which you want to be optimising token usage.

I feel like my token usage is mostly around regenerating context. That's the main battle I'm trying o win. How do we have a central 'brain' of everything related to a project? How do agents read/write to it?

[Christoph Hart]

Is it possible to tell the AI not to do some of those tasks?

sure. I mean you have to tell it to use these tools in the first place, so if you keep it a secret from your robot, it will never call hise-cli. Once the dust settles I'll try setting up system prompts / agents.md file templates that teach the AI the optimal usage of this tool.

The ROI on it letting it compile the project for you is pretty narrow, so that particular set of commands might not be the most thrilling thing to teach the agent - however the hise-cli offers a script runner that can perform build steps for you.

/hise launch   # open HISE
/builder reset # clear the module tree
/project       # Enter project mode
export dll     # compile the DSP network dll
load MyProject.xml # load your XML preset backup
export project # VST3 as default
export project with format=Standalone # export App
/exit          # leave project mode
/hise shutdown # good bye

is basically the full cross-platform build script that automates the export for you. you then just need to call hise-cli --run "build.hsc" (or even register hise-cli as shell script runner, then the script file itself becomes executable).