Is the HISE REST server ready for use?
-
@ustk Nice!

-
@David-Healey One of the best aspects of using the CLI/REST setup is a much tighter iteration loop, where Claude can test the changes and fix mistakes itself, without involving me.
That means it delivers a working feature, instead of a code-only change where I have to open HISE, test it manually, provide Claude with compiler errors and/or UI bugs and do that round-trip several times to get to a working state.
-
@Christoph-Hart Specific bug: Claude says the screenshot endpoint is giving a 404 error.
Latest HISE build 6446c4a
-
@dannytaurus how are you doing this?
-
@Chazrox Which part? Do you already use Claude in your plugin project? If not, that's the place to start. I can help with that.
If you're already using Claude, it's just a matter of getting the CLI installed and REST server running. I can help with that too.
-
@dannytaurus Claude "in" my project no. I use Claude yes. Can you help me with the CLI part? Tbh I have no clue what CLI or REST is.....but I feel like I need it. lol. Forgive me. haha.
-
@Chazrox
CLI means command line interface - it's a console app where you can put commands.
REST is the system used to send and receive data from a server. -
@David-Healey Aha.
Thanks. This should be interesting. I was using Claude with Cursor for a little bit. Still getting a hang of that but havent used it much lately. Is this a similar kind of situation? Or would I still be prompting from Claude app interface? -
@Chazrox Claude can self install/link with hise. It analyses the REST API and the CLI structure of Hise and can pul git, install, link, test, until ready for running...
That being said, it's always better to understand what it does... -
I havent used Claude but Codex works better than expected as well.
Ive used it with VS Code and linked it directly to my HISE projects.
No GUI creation or anything but with effects, scriptnode, debugging, etc it has been a huge time saver.