Disclosure: I’m sharing EvoForge on behalf of the product team. It’s a Windows/macOS desktop agent that can work across files, a browser, desktop apps and a terminal. Users connect their own model API key or a compatible local model service. The aim is to carry a task across those tools without making the user move every intermediate result by hand. One design choice is to keep the agent core free and charge for optional specialist modules. Basic covers coding, research and documents; the creative module adds a writing desk, an image-editing canvas and a video timeline. Model API usage is separate, so “free Basic” does not mean free cloud inference. The part I’d like feedback on is permission friction. When an agent can edit a local file and also send an email or publish something, those actions need different boundaries. What would you let it do without interrupting you, and what should always pause for approval? A concrete example from your own workflow would be useful. Current limits: desktop only, no Linux build, and you need to configure a model. Optional Creator, Game Development and Embodied AI modules are paid. Product and download details: https://evoforge.cc   submitted by   /u/victor666888 [link]   [comments]