今日已更新 246 条资讯 | 累计 21112 条内容
关于我们

Show HN: Reverse-engineering web apps into agent tools

pancomplex 2026年07月09日 23:45 1 次阅读 来源:HackerNews

Hey HN! We built a browser-based agent that runs inside an authenticated web app, watches how the app calls its own APIs, and automatically turns those into agent tools. You can think of it as an auto-generated MCP server that self-updates as the host app changes. The result is a skilled AI assistant that actually integrates deeply with any product (not just chat and RAG) with minimal effort. Check out these short demos below that show the agent in software you're probably familiar with: - Jira:

Hey HN! We built a browser-based agent that runs inside an authenticated web app, watches how the app calls its own APIs, and automatically turns those into agent tools. You can think of it as an auto-generated MCP server that self-updates as the host app changes. The result is a skilled AI assistant that actually integrates deeply with any product (not just chat and RAG) with minimal effort. Check out these short demos below that show the agent in software you're probably familiar with: - Jira: https://demo.frigade.com/hn?skill=jira - Spotify: https://demo.frigade.com/hn?skill=spotify - Hacker News (lol): https://demo.frigade.com/hn?skill=hackernews - Full Demo: https://demo.frigade.com/hn?skill=full-demo As you can see in the examples, you can do way more (and faster) than what you normally would be able to via point and click. And we never even touched the source code of these products! Why do this? In an ideal world, every application has an MCP server or an easily-digestible API available for AI agents to feed from. In practice, we found that even very modern software tends to have a spider web of confusing APIs and services that AI agents simply cannot use out of the box. Security also becomes a huge issue as applications have different (often homebrewed) standards for how endpoints are secured (JWTs/cookies/mix of both). Finally, having an actual browser agent go in and use the application on behalf of the user (i.e. computer-use), is simply too brittle, slow, and burns a lot of tokens. We took our existing browser agent that’s already trained to use and learn authenticated applications, and added an extra step that automatically turns the app’s authenticated APIs into "recipes". A recipe is a mix of the following: - API endpoint + method - Authentication method (and how to retrieve refresh auth tokens/cookies) - Response schema - Input schema (for POST/PUT) - Human readable description of what the tool does Putting it all together, these become reusable tool
本文内容来源于互联网,版权归原作者所有
查看原文