Original Summary

We kept running into the same problem with browser agents: the user is already on a page, already signed in, and already has context—but the agent often starts again in a fresh browser somewhere else. So we built SiteWake around the opposite idea. The user-facing agent lives in the website and works in the visitor's current session. The part we care about most is the definition of “done.” If a user asks the site to complete a workflow, clicking the final button is not enough. The agent should check the resulting page state or business outcome before reporting success. We also built a capability path: a successful task can be turned into a reusable capability, independently replayed and validated, then published so the next matching request does not need to rediscover the path. The current version is self-hosted and open source: https://github.com/sitewake/sitewake Where it honestly stands: the execution, session, site-knowledge, and capability-validation pieces work. Learning and failure recovery still need much more real-site testing. We do not expect arbitrary websites to be zero-maintenance today. If you include the kind of site and task you have in mind, we can turn the feedback into a concrete test or roadmap decision.   submitted by   /u/sitewake [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/14 11:03:59