Give It Eyes

Every website on the internet.

That's what becomes accessible to Claude once you install a browser plugin. Not a search result. Not a cached summary. The actual pages - with full pricing tables, job requirements, competitor listings, contact info. One plugin is the unlock. That's what this newsletter is about.

The 90-second prospect file
A sales consultant runs browser-enabled Claude through a list of 50 companies each morning. For each one, it visits the website, checks for recent news, flags open job listings, and writes a two-sentence brief. What used to be 45 minutes of tab-switching prep takes under two minutes. His outreach is more specific. His response rate went up.

The overnight price monitor
A small e-commerce operator set up a browser agent to check competitor pricing on 40 products every night. When anything drops below a threshold, it logs the gap and drafts a recommendation. No integrations. No API keys. Claude Code, a browser plugin, and a spreadsheet. She's been running it for six weeks.

The job application machine
A developer built a system that reads job listings overnight, scores them against his criteria, and submits applications with customized notes for anything that qualifies. He's not home when the applications go out. He wakes up to a log of what was sent. That last story is mine - more on that below.

I built the job application machine - and it ran last night

Every night, an agent polls my Gmail for job alerts. When one arrives, it opens the listing page - the real page, not just the email text - reads the requirements, and scores it against a rubric I defined: clear scope, verified payment history from the client, realistic budget, right stack. If it scores high enough, it writes a proposal in my voice and submits it.

I'm not there when any of this happens.

The numbers: over the past six weeks, the agent has processed 300+ job postings. About 5% pass the scoring filter. Every one of those gets a proposal.

The thing I didn't expect: browser access changed the scoring quality significantly. Reading the actual job page - not just the snippet in the email alert - surfaces requirements that clients bury in the description. Budget context. Red flags. Things that change whether a job is worth pursuing.

That's the real lesson. Browser access isn't about convenience. It's about the difference between acting on a summary and acting on the source.

Week 4 of 6: Give Claude browser access

First, open your terminal - the regular one on your computer, not Claude Code's chat window - and run:

Restart Claude Code. Then, in Claude's chat, type:

You'll see Claude open a real browser, navigate to the page, and return the actual live headlines - not something from its training data, not a cached result. What's on the page right now.

Once that works, you have browser access. Point it anywhere: a competitor's pricing page, a supplier's product catalog, a job board, a news feed. Anything public on the web is now something Claude can read and act on.

Stuck? Reply to this email.

Next week: you give Claude a research question before you go to sleep. It browses, reads multiple sources, writes a structured brief - and then uses the same Playwright plugin to publish it. To a Notion page, a CMS, a Google Doc, wherever you tell it. Research to published output, no human in the loop. That's the full thing.

Manu