An AI Agent That Doesn't Get Blocked by Bot Detection

You gave a cloud agent a real errand, like reordering on Amazon, checking Costco, booking a flight or grabbing a Resy table, and it hit a wall. An error page, a CAPTCHA it could not solve, or a login it never got past.

Have Aside do the task instead. Its agent works inside your own browser on your Mac or Windows PC, in the session you already have. It tries CAPTCHAs itself and hands you the step when a site wants a code or a passkey.

Why do AI agents get blocked?

Most agents run in a cloud browser that has none of your history. The site sees a brand-new device on a data-center address, no cookies, no login, and clicks that arrive faster than a person's. That is what a bot looks like, so the site answers with a CAPTCHA, an error page or a flat block.

A cloud-browser provider's own guide (Kernel, updated Oct 29, 2026) puts it plainly: blocks happen because "the site can't tell who the agent is," because the agent comes from a cloud IP, or because it logs in from scratch every run.

The big agents hit this in public. When Meta's Muse tried Amazon, The Register (Sep 21, 2026) printed what Muse told its user: "Hit a snag: Amazon is showing an anti-bot wall that blocks automated browsers outright – the browser couldn't even get to the search page."

Amazon's notice to a Muse user, Sep 2026. Source: @jwegener on X

OpenAI's Dot ran into the same thing. In The Verge's hands-on (Oct 2, 2026), Dot gave up on one site with "This particular check needs a sustained mouse hold that my browser controls don't support," and could not log in to Ikea because of a "looping security check." In WIRED's test (Oct 7, 2026), Dot asked "TikTok's website has a puzzle captcha blocking the Wildwonder cancellation… May I solve it?" and then "failed and suggested I solve the captcha myself."

Why does an agent in your own browser get blocked less?

Because the site sees what it sees when you browse: your home internet address, your cookies, your saved logins and months of history. An agent working inside that browser inherits all of it. Sites can still challenge it, but it starts out looking like a known customer instead of a new device from a data center.

People who build and run agents say the same thing. In a 23-agent comparison on r/AI_Agents (Oct 28, 2026), the poster split agents into two kinds: "a cloud agent spinning up its own browser… versus one driving your actual already logged in browser profile… the second kind inherits your real device fingerprint, timezone and session history."

On r/MuseAgent (Oct 22, 2026), a user complained that "Some websites will show an error page right when you login." The most upvoted reply: "I run it in my MacBook and it'll bypass them."

That is how Aside is built. The agent does not open a separate browser somewhere else. It runs each task in the Aside browser on your computer, in the tabs and profile you already use.

How do you give an AI agent your logins without giving it your passwords?

In Aside, you save your logins in Aside Vault, the built-in password manager. When a task reaches a sign-in page, Vault fills the form. The agent does not receive the raw password. You keep the secret, and the agent gets a signed-in page to work on.

One r/LLMDevs user (Jun 26, 2026) found this fix by hand: "i stopped letting the agent log in at all… captcha and 2fa basically disappear as problems because i already cleared them as a human." Aside makes that the default. Your browser is already signed in, and Vault handles the sites that are not.

A reviewer on Tistory (SCV, Aug 18, 2026) described the change after setting up Vault: "Before, even when AI entered a site it often stopped at the login step and I had to step in, but after finishing the password integration, the flow of finding the needed site, checking the login state and continuing to the next task felt much more natural."

Aside's task view after signing in to Amazon with a saved login, Nov 5, 2026.

What happens when a site shows a CAPTCHA or MFA?

Aside tries CAPTCHAs itself: it ships a solver for checkbox, slider and image CAPTCHAs. When a site asks for MFA, a passkey approval or an identity check, the task pauses and waits for you. You complete the visible step in the tab, and the task picks up where it left off. A CAPTCHA that beats the solver pauses the task the same way.

On r/AI_Agents (Aug 14, 2026), one user described an agent that tried to push through: "the second the site throws a captcha or some weird modal it just loops. watched it re-open the same popup 11 times." A check Aside can't clear pauses the task and asks you, and the task carries on in the same session once you clear it.

When we signed in to Alaska Airlines, the site texted a 6-digit code. Aside read the code from Messages on the Mac and finished the sign-in. On a site where it can't, you type the code and the task continues.

Alaska Airlines' text-message check during an Aside sign-in, Nov 5, 2026.

For anything that spends money or speaks in your name, turn on Final confirm in the task composer. The agent then asks before it sends, pays, deletes or submits. It's off by default.

Can an AI agent shop on Amazon?

Only on Amazon's terms. Amazon's Conditions of Use, updated Aug 14, 2026, say that "No Agent may access… Amazon Services unless, at all times, it identifies itself." Aside does not offer a way around that. Amazon can also show a human check in the middle of a task, and whether to continue is your call.

Amazon has enforced this. GeekWire (Sep 2026) printed the message Muse hit: "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use." Amazon's statement, in The Register, was that agents "should operate openly and respect service provider decisions about whether or not to participate."

Amazon is not alone. CNBC (Nov 1, 2026) reported that Amazon, Kohl's and Neiman Marcus restrict agents on purpose, and that "37 block shopping agents largely by accident." Engadget (Nov 2, 2026) noted that Walmart, which partners with Muse, still hit it with verification checks.

The law is still moving. In Amazon's case against Perplexity, a court granted an injunction on Mar 9, 2026; the Ninth Circuit vacated it on Aug 4, 2026, reasoning that "it was the user who 'accessed' Amazon's computers." That ruling is about who is doing the accessing, not a license to ignore a site's terms.

Questions people ask

Can I watch the agent work?

Yes. The task runs in tabs inside your own Aside window, and the task view shows a live preview of the tab it's working in.

Can the agent see my passwords?

No. Aside Vault signs in on the agent's behalf and keeps the password itself out of the agent's hands.

Does it work on sites like Costco?

It runs in your logged-in browser, so it starts from your session. One user on X (@msg, Sep 11, 2026) wrote: "has anyone gotten their agent with a cloud computer to successfully login to costco's website and order for them. i even have tailscale exit note to home computer and no dice. in the meanwhile going to have @AsideAI take care of it for me locally." Any site can still show a human check, and that step is yours.

Can I keep a site away from the agent?

Yes. Run the task in incognito. The agent gets a session with none of your logins, and Aside Vault stays off, so it can't sign in anywhere.

Download Aside for Mac or Windows at aside.com/download.