Original Summary

I’m building Hermo, a local tool that lets you demonstrate a task on a website, define its inputs and outputs, test it, and expose it through REST or MCP. The idea is simple: if you repeatedly open a website, enter something, click a button and copy the result, you should be able to make that task callable from your own software. So far, I’ve got workflows working locally with ChatGPT, Claude and Gemini. Hermo generates its own keys for calling those recorded workflows through my signed-in browser sessions. They aren’t official provider API keys. It’s still an early prototype. The biggest limitation is that execution currently depends on keeping the connected website and companion tabs open. I’m exploring background execution and eventually a hosted runner so requests could work while my computer is off. Cloud execution isn’t working yet. I’m also considering releasing the local core as free, open-source software. I’d appreciate honest feedback: - What website task would you actually want to turn into an API? - Would local execution be useful, or would you need cloud hosting? - What would make you trust this enough to use regularly?   submitted by   /u/MKP_Nimilka [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/15 03:33:00