EstimAI Roadmap & Feature's requests

KairosJS · 2026-05-31T12:03:28+00:00

Current Roadmap, WIP & Ideas Below are some important features that I've started working on, or that I'm envisioning for EstimAI. I'm not sure they'll a...

Welwa

ElectricFrog you can see the full response of the AI with all the stim info in the saved sessions, and also in the full chat log during the session (side bar menu, and then click on the conversation icon)

ElectricFrog

Welwa Thank you for this insight! I just tested, and you are correct for the case of seeing it during an ongoing session. Clicking the conversation icon shows the full response, including the stim (I had never clicked that icon before, I thought that was the chat history shown directly when opening the side bar, i.e. that I already had that info opened by default). This is really good news, this is basicly what I was after!

However, when I exit that session, and then open the same from saved session by clicking on Edit, the stim info part is not there. The rest of the conversation history is there, including the "system time" stamps. But the line for stim info is missing. So I'm a bit confused there. Am I in the wrong place, or some weird bug that make that info save for you but not for me...?

Ezrek123

Thank you for your hard work!

Could you add a feature in the Normal Eudaimonia mode(i use image generation) that during the end of the session orgasm time, you can choose that its only using images of the mistress?(live generated)
Sometimes i get the ending where is its only images of her, but most of my endings its the images from "Use your own random pics".

Additionally, but less important, an option to completely disable other images/videos. So it only ever shows images of the mistress which are live generated.

I can kinda imitate it by saving generated images in a folder and using these as "Use your own random pics" but i dont have videos for that and if i dont select my own videos, it uses generic ones

I would love for it to be possible to only see my mistress during the whole session and nothing else.

BobRoss235

Just saw the note about Civet support — awesome! Mine arrived in the mail and works really well, way easier to set up than the Mercury1k + Venus2k + EOM3k combo.
Looking forward to the update — as always, really appreciate the hard work!

KairosJS

BobRoss235

Thanks!
I'm currently working on the stage detection algorithm: close / edge / orgasm. I'd also like to explore an intermediate stage between edge and orgasm. The work for now is still very early and I'm not satisfied with the results yet.

The sensor itself is really precise and responsive, which is great. As a solo dev I'll definitely lack data when the first version ships, so hopefully many users will agree to share theirs to improve detection for everyone.

lolsnololsno331

hopefully it works better than the edge-o-matic, most expensive toy I've bought and the instructions are crap and it's really hard to figure out what's going on. Your implementation looks very straight forward

KairosJS

Ainavirin

lolsnololsno331

What I'm trying to build is something that fits Eudaimonia specifically: the user can (and must) fight the edge, resisting, holding, etc., rather than just hitting a ceiling value. I also give the AI as much information as possible, plus tools to play with you around it.

Results are getting better, but I'm still not sure how this will be released. It will probably ship as a "beta", and I'll keep refining it over time.

Ainavirin

I've received my Civet and tested it once, the DG LAB 4 makes a very good job for calibrating it, and offers advanced settings such as "adaptive threshold":

slowly decreasing the edging threshold if no edging is detected after x seconds (i.e. if the edging threshold is set too high)
slowly decreasing the edging threshold after each successful edging to compensate for the decrease in sensitivity to stimulation
leak compensation (automatically decrease the edging and building threshold to compensate for the fact that the plug slowly deflates over time. Default value is decreasing by 3 kPa per hour.

It's really great.

ToBs

Are there any news regarding information from last update?

First: a new scenario that takes full advantage of the new features should be released soon. I believe you'll like it, as it's a Eudaimonia adaptation of a classic.

KairosJS

ToBs The update is ready. As I said, it's mostly small improvements and bug fixes. The scenario is also ready, and I'm working on an alternative version of it. This scenario was designed with image generation (and newer models such as Krea 2) in mind. It's big and will probably require large frontier models (the context ranges from 16k to 24k tokens).

I still want to spend this week working on the Civet before releasing the update. So hopefully, this week end!

Ezrek123

hello,
could you change instead of the "Lower resolution" on/off button, a slider or a select menu to change the resolution a bit more specific? so i can min/max my gpu usage more, when i run a llm at the same time it takes 1 min with lower resolution off and with it on it takes 10 seconds, i would like to use something inbetween if possible

Misty

KairosJS

First of all, thanks for making this wonderful playground. It has transformed my 2B into such an immersive toy.

I’m very eager to order myself a Civet once you’ve got something stable that you are happy to publish.

— Out of curiosity, could the Civet input function be reverse engineered with a ‘clenching challenge’ instead of detecting arousal. e.g char instructs user to clench X amount of times in 10 seconds and punishes or rewards as an outcome. Or instructions to clench once every 5 seconds for a duration or receive pain as a punishment. Or as an orgasm routine, you receive the same clench strength pattern back translating to an ‘analogue’ (pun intended) stim sequence -with or without X seconds delay.

The scenario could dictate how the tasks slowly increase difficulty or simulate a specific penetration fantasy. Gamify the kegels.

The places my wicked mind wonders…

KairosJS

Misty Thank you, that's very much appreciated!

For now I'm focusing on the basics: edge detection, ruined orgasms, and feeding the LLM good information so it can actually use the sensor during a session.

But your idea is a good one, and definitely doable. The Civet opens up a lot of possibilities, and I intend to explore them over time. Right now my main focus is getting the edge detection algorithm to work reliably for everyone. Since I'm working alone, the data I have is still pretty limited, and I've taken a somewhat different route from DG-Lab. Instead of asking the user to stay calm and steady, let the edge come without fighting, and cutting at the first involuntary contraction, I want the user to fight and resist the incoming edge. So I measure a sliding average that takes deliberate kegels into account, which I think suits Eudaimonia better. Hopefully this will work!

I expect this to stay in a "beta / experimental" state for a while, but I do have your kind of features in mind for later!

MalteP

@KairosJS Would love to check it out my civet just arrived!

Tycho

Feature Requests:
(I admit, I have not dug around in the console to see if this information is already there or if there was some other browser-side workaround to already do this.)
-An "enhanced" or verbose scenario debug mode would be useful. Specifically, to troubleshoot the new Phases feature, I would like the option to have the current phase (and maybe other things like Triggers and Variables) displayed and logged (witch the scenario history). When testing scenarios, I can't reliably determine what phase (if any) the scenario is currently in.
-A feature in the phase system to trigger an explicit piece of dialogue or exposition (similar to first messages or example messages).

western55

@KairosJS

Hello - Thank you for all your work.

I have one feature request. When a timer is set, it is possible to re-engage the AI and the timer is ignored at that point. Would like an option to make it so the AI interaction is disabled or hidden while there is an active timer.

« Previous Page