Your AI stops at the login wall
If you've ever told an AI agent to "read this page," you've probably hit the wall. Public blogs and news articles? Fine. But hand it a logged-in dashboard, an internal company tool, or your own feed on a social platform, and the agent comes back empty-handed. The built-in search and fetch tools simply don't carry your login session with them.
web-access fills exactly that gap. It's a Skill that gives an AI agent full internet access, and its defining trait is that it attaches to the browser you already use every day.
The problem it solves
An agent's default web tools are missing two things: a strategy for choosing which tool to use when, and the ability to drive a real browser. They can read static text, but they stall on dynamic pages where you have to click to reveal content, and on screens visible only after login.
web-access supplies both. It decides on its own whether to reach for search, fetch, curl, Jina, or live browser control depending on the situation, and when needed it drives your actual browser.
How it works
The standout piece is the CDP Proxy. It does not spin up a separate automation-only browser. Instead it connects directly, over remote debugging, to the Chrome or Edge you're already logged into. That means it inherits your existing logged-in state with no separate sign-in step, and uses it to read pages, click, and upload files.
Clicking comes in three flavors: a JavaScript click, a real mouse-event click that mimics a physical cursor, and a dedicated file-upload path. The design goes beyond reading a screen toward faithfully reproducing what a human would actually do.
Setup
The simplest route is the skills CLI.
npx skills add eze-is/web-access
For Claude Code, you can also install it as a plugin.
claude plugin marketplace add https://github.com/eze-is/web-access
claude plugin install web-access@web-access --scope user
CDP mode requires Node.js 22 or newer and a browser with remote debugging enabled. Open chrome://inspect/#remote-debugging in Chrome or edge://inspect/#remote-debugging in Edge, and check 'Allow remote debugging for this browser instance'.
A real scenario
Picture a team that wants an AI to summarize an analytics screen that only loads after login — say a creator dashboard on a social platform. The old way, the agent would freeze at the login wall. web-access attaches to the browser that's already authenticated and reads the screen as-is.
It also helps when investigating many targets at once. Ask it to compare five product sites in parallel and it dispatches sub-agents that run concurrently while sharing a single Proxy, isolated at the tab level. The more you work a given domain, the more it stores site-specific operating experience per domain and reuses it across sessions.
When not to use it
There are real cautions. Driving social platforms through browser automation carries a risk of rate-limiting or account bans, and the README strongly recommends using a secondary account rather than your main one. If you only need to read a handful of public pages, plain search is enough — there's no need to switch on CDP mode at all.
From v2.5.2, if the browser you specified isn't running, it won't quietly fall back to another one; it errors out clearly and stops. That's a deliberate guard against connecting to an unintended browser, but the flip side is that a half-prepared environment blocks you immediately, so getting the initial setup right matters.
How it compares
Tools that launch a fresh automation-only browser force you to rebuild the login session from scratch. web-access takes the opposite bet: borrow the browser you're already signed into. For work where the logged-in state is the whole point, that difference is large. Conversely, if you need automation in a fully isolated, clean environment, a dedicated-browser approach may suit you better.
Wrap-up
The real value of web-access isn't "it searches well" — it's "your AI sees the logged-in screen on your behalf." If you regularly work with post-login data, check how it attaches to which browser, and settle your secondary-account policy, before you adopt it.
🐦 Faster updates on X: @baegseungh7061
📚 More in this series: AI Insights
💌 Subscribe: Follow on X or grab the RSS
댓글
댓글 쓰기