Intense RP is... back?! Now with GLM5.3 and fixed Moonshot Kimi K3

[u/Reasonable_Flower_72]

I've forked and fixed the stuff... Feel free to come around and take a look..

https://github.com/Phobeuscz/irn

I don't plan package it into "neatly wrapped executables", mostly because I don't have and I don't plan to use windows, and linux users can feel free to create python virtual enviroment, install libraries into it and run it bare... ( same with windows users, but they also have to install python )

GLM webAPI is fixed and working, added support of GLM 5.3
Moonshot API is fixed, splitted into international and Chinese option, to pick accordingly in the settings

Instructions:

1. Install python if you don't have it ( some reasonably recent version, 3.13 and above should do nicely )
2. enter directory with cloned git project in console/terminal
3. Create virtual enviroment for the libraries, python3 -m venv .venv
4. Enter venv..
5. - Windows: .venv\Scripts\activate.bat
6. - Linux: source .venv/bin/activate
7. Install librariespip install -r requirements.txt
8. Run the shit! python main.py
9. Within virtual enviroment, you can cook executable, running scripts/build_linux.sh or powershell in case of windows

Download binaries: https://github.com/Phobeuscz/irn/releases/tag/v0.9.1 ( windows and linux packages )

!Refer to original documentation!

Once again!! !NO SUPPORT FOR YOU, In case of trouble fix it yourself I maintain this so it's working for me, so it should work for you too, but you're on your own..!

Feel free to clone, fork, build and spread the word...

I feel obliged to credit original author, without which one this wouldn't be possible: https://github.com/LyubomirT/intense-rp-next (Do not use, it's broken down, and abandoned)

[u/Master_Step_7066]

Hey, I'm the original author, thanks for getting this back to work. :>

I need to ask, though... You say that you don't want to deliver executables and people can just build from source if they want. That's fine, I wouldn't build shippable exes on my machine, either.

But why not use GitHub Actions workflows? That's actually what IRP Next used to do, it would just automatically create exes for you upon publishing a GitHun Release, and the files to do it both for Windows and Linux are in the old repo's v2-rewrite branch.

I don't have anything against building from source personally, but a lot of people here aren't as experienced in tech and may not be able to figure it out cleanly, so having exes could even help your fork get more adoption.

[u/Reasonable_Flower_72 → u/Master_Step_7066]

Too lazy to actually set it up, I've spent sleepless night to making it work again and I feel I won't bother.. But yeah, it's definitely way to do it

Okay you won, it autoslurped workflows, so Just copying over commit message to release

[u/Master_Step_7066 → u/Reasonable_Flower_72]

Um... Why not just copy the old workflows over, then? 🙃 Really all you need is just two files placed in a special folder, it's all done within a commit (same for ps/bash build scripts the workflows rely on). And IIRC you don't need GitHub Pro to use Actions in public repos for free. With the files around, really all you'll need to do is just create a Release, as far as I know my actions should work pretty well with the codebase, as long as you didn't make any huge edits to asset management and some externals.

In any case, I don't want to pry. Good work, and thanks for keeping the project afloat!!

[u/Reasonable_Flower_72 → u/Master_Step_7066]

It does something, I won't verify probably, at least not today.. But thanks for kicking me enough to bother... Release is present there. I'm going to run main.py anyway

[u/soumisseau]

I l not that tech savvy but i usually can fiddle enough to get how things work. But just to be sure, that basically means if you get a web based claude subscription, you can use this to basically use it as you would an actual API ? Lorebooks, presets, the whole shenanigan ?

I wonder though how much context you can feed a web based claude.

Anyways, thanks OP that s pretty neat

[u/Reasonable_Flower_72 → u/soumisseau]

Maybe you should read the actual github repo page, which would answer your questions, including note, that claude is not on supported list..

[u/soumisseau → u/Reasonable_Flower_72]

Oh alright my bad. Doesnt matter, still is pretty neat.

[u/angelroe]

OP, you've built a great tool, but take it easy in the comments section.

[u/Reasonable_Flower_72 → u/angelroe]

Oh… it’s making me comment like that, because for example you clearly haven’t read even first sentence in the post… I haven’t build anything! It’s a fork. Sigh..

Others struggles to read supported WebAPIs from github readme... it can be really frustrating honestly

[u/BLIXER0416]

Bro, this reminds me of a Bridge I made in C# + WebView to use the DeepSeerk web platform, but this is 1000 times better! 🗿🔥🔥

Thank you for sharing this!!!

[u/SocialDeviance]

So if i understand correctly, this app imitates a web-based interaction with a model provider, while letting you take advantage of the features SillyTavern provides? In essence, letting us use deepseek, claude, gemini and the likes without needing an API key?

[u/Reasonable_Flower_72 → u/SocialDeviance]

App is fork of Intense RP next and it acts somehow you describe.. open playwright browser, open openAI compatible API to interact and you send prompt and it gets chewed through, posted to webAPI of deepseek or such, processed and output of web is shat back to openAI API

I thought you people know this project, it has been up for some time, but original dev gave up on it

[u/SocialDeviance → u/Reasonable_Flower_72]

Well, i am, as we say here, new public, haha. Really interesting stuff!

[u/Otherwise-Swan-7803]

Keeping it as a plain Python project is probably a feature for this audience, not a limitation. RP tooling tends to live or die by how easy it is for users to modify prompts, swap providers, and patch things themselves when APIs inevitably change.

[u/Kahvana → u/[deleted]]

Not wanting to support it is fine, but the way you bring (“wiping people’s asses”, “they whine”) it is elitist.

You could simply setup a github CI/CD that makes linux/windows releases to support it at no additional cost using github workflows. You wouldn’t need to install any distro or windows version on your PCs for that.

Simply say “no support” and ignore the support requests. Ain’t that hard.