Code Compass is an AI agent that helps engineers determine the best task to work on next, given the codebase context from the engineer’s current task.- Code Compass indexes a GitHub repo with AST parsing, enabling agents to understand where developers are developing codebase context [1]- Given a current linear ticket, Code Compass's agent provides context about the relevant codebase locations,...
One risk with these new standards for agent auth - which we will of course support if our customers want it - is that the websites that need them the most are the least likely to adopt them.
The main use cases for browser agents are for paying utility bills on old government websites or finding receipts for an expense report on a website without an API. There is a no reason to use browser agents on a website like Linear for example. A developer is better off integrating via API or MCP.
Therein lies the main challenge; the websites where browser agents are most useful are the same websites that are least likely to adopt new technology (it was their not adopting new technologies that made them good candidates for this browser agents in the first place).
I think this new standard is awesome, but I fear that the websites that support it will be those websites that didn't need it in the first place (because they could just as easily add an API).
When our agent signs in, we input the forwarded otp code to get access.
Right now, we're focused on building connectors for our customers, which has not yet involved Captcha solving.
Hey HN, We’re Alex, Land, and Rajit. We’re building Prism (prismai.sh), a tool that helps browser agents authenticate onto websites with user credentials. Developers pass in credentials, Prism logs into a website on their behalf, and hands them back the cookies so they have an authenticated session. Here’s an example of how developers can use Prism to complete username/password flows...