Not sure if its only me, but most of the texts in this page aren't showing up. https://i.imgur.com/E4HloO7.png
(It's not even a font rendering issue - the text is totally absent from the page markup. I wonder how that can happen.)
31–40 of 433 posts
Not sure if its only me, but most of the texts in this page aren't showing up. https://i.imgur.com/E4HloO7.png
(It's not even a font rendering issue - the text is totally absent from the page markup. I wonder how that can happen.)
> We’re launching with 1,000 Max users and expanding gradually based on what we learn. This measured approach helps us validate safeguards before broader deployment. Somewhat comforting they’re not yolo-ing it too much, but I frankly don’t see how the prompt injection issues with browser agents that act on your behalf can be surmounted - maybe other than the company guaranteeing “we’ll reimburse you for any unintenti…
And you could whitelist APIs like "Fill form textarea with {content}" vs more destructive ones like "Submit form" or "Make request to {url} with {body}".
Edit: It seems to already do this.
Granted, you'd still have to be eternally vigilant.
> Malicious actors can hide instructions in websites, emails, and documents that trick AI into taking harmful actions without your knowledge, including: > * Accessing your accounts or files > * Sharing your private information > * Making purchases on your behalf > * Taking actions you never intended This should really be at the top of the page and not one full screen below the "Try" button.
It's insane how we're throwing out decades of security research because it's slightly annoying to have to write your own emails.
* Mislead agents to paying for goods with the wrong address
* Crypto wallets drained because the agent was told to send it to another wallet but it sent it to the wrong one.
* Account takeover via summarization, because a hidden comment told the agent additional hidden instructions.
* Sending your account details and passwords to another email address and telling the agent that the email was [company name] customer service.
All via prompt injection alone.
> Malicious actors can hide instructions in websites, emails, and documents that trick AI into taking harmful actions without your knowledge, including: > * Accessing your accounts or files > * Sharing your private information > * Making purchases on your behalf > * Taking actions you never intended This should really be at the top of the page and not one full screen below the "Try" button.
It's insane how we're throwing out decades of security research because it's slightly annoying to have to write your own emails.
https://support.anthropic.com/en/articles/12012173-getting-s...
It's much less nice that they're more-or-less silent on how to mitigate those risks.
Ah, so the attacker will only get full access to my information and control over my accounts ~10% of the time. Comforting!
Today, most of these "AI agents" are really just browser extensions with broad permissions, piping whatever they see into an LLM. It works, but it feels more like a stopgap than a destination.
Imagine instead of opening a bank site, logging in, and clicking through forms, you simply say: “transfer $50 to savings,” and the agent executes it directly via the bank’s API. No browser, no login, no app. Just natural language!
The real question is whether we’re moving toward that kind of direct agent-driven world, or if we’re heading for a future where the browser remains the chokepoint for all digital interactions.
> Malicious actors can hide instructions in websites, emails, and documents that trick AI into taking harmful actions without your knowledge, including: > * Accessing your accounts or files > * Sharing your private information > * Making purchases on your behalf > * Taking actions you never intended This should really be at the top of the page and not one full screen below the "Try" button.
It's insane how we're throwing out decades of security research because it's slightly annoying to have to write your own emails.
Having played a LOT with browser use, playwright, and puppeteer (all via MCP integrations and pythonic test cases), it's incredibly clear how quickly Claude (in particular) loses the thread as it starts to interact with the browser. There's a TON of visual and contextual information that just vanishes as you begin to do anything particularly complex. In my experience, repeatedly forcing new context windows between sc…