On Windows, I've noticed the app sits consistently around 300MB of RAM, sometimes a bit more, sometimes a bit less. I've used other similar tools in the past that hovered around 30MB or so, which made me wonder if there's room for optimization on that front.
I also noticed my MacBook Air M1 running warmer than usual during the same workflow I normally do.
I can't say for certain Vowen is responsible, but connecting the dots with what I saw on Windows, it felt worth mentioning — especially on a fanless machine where thermals matter a bit more.
I completely understand that a tool with this many features has a certain overhead, and I'm not expecting it to be ultra-lightweight.
That said, I was wondering if any resource optimizations are on the roadmap — things like a more progressive resource usage model, or the ability to put certain features into standby when they're not actively being used, so the app has a lighter footprint during idle or low-usage moments.
Just to add context: I'm using cloud APIs only (Groq and OpenAI) — no local models running on my side — so the footprint isn't coming from inference.
Thanks as always for the great work
Please authenticate to join the conversation.
Completed
Feature Request
19 days ago

dimezio
Get notified by email when there are changes.
Completed
Feature Request
19 days ago

dimezio
Get notified by email when there are changes.