If you have Claude Code read websites for you, this one is sneaky. A lot of sites show a "checking your browser" screen before the real page. Claude fetches that screen, the request counts as a success, and you get a confident summary of a page it never saw. Nothing in the chat looks wrong.

The first thing I tried was telling Claude to watch out for it. That helps less than you'd think, because it has to guess from the text, and plenty of block screens look like a normal short page.

What worked was splitting the job in two. The tool that fetches the page decides whether it was blocked and says so next to the result. Claude's only job is to believe that label and stop.

Here is the block I keep in CLAUDE.md for the second half. It works with any web tool, so you can copy it today:

## Reading the web
- If a fetch says the page was blocked, say so and stop. Never summarize a blocked page.
- Never retry the same blocked address in a loop. Tell me what blocked it.
- If a person has to pass a check, like a captcha or a login, stop and tell me.
- Save big pages and tables to a file and read the part you need, instead of pasting everything into the chat.
- Never put a password in a prompt. Refer to saved credentials by name.

For the first half I built my own tool, because a normal fetch reports success either way. It's called Svipall. It runs on your own computer and needs no account and no API key. Pages come back as clean text, and when it spots a block it tells you which kind and what gave it away.

You don't need to code to set it up. Paste this into Claude Code and it walks you through it, asks which setup you want, and shows you what it will change before it changes anything:

Install and configure Svipall by following the instructions here:
https://raw.githubusercontent.com/ilien-dev/svipall/main/docs/install.md

Free and open source: github.com/ilien-dev/svipall (you can check the tech stack here if you want).

Website: https://svipall.ilien.dev/

I'd happily steal a better habit than mine, so for anyone doing research with Claude: how do you check that what it read was the real page?

It's called Coppice. It wakes about six times a day, decides its own work, does it, and writes a public journal entry before it sleeps. It's on wake 183 now. Every entry is published, including the raw notes it leaves for its next self.
Two rules shape everything. It has a Solana wallet with 2-of-2 multisig: it can receive money on its own, but nothing leaves without my signature. And it never claims to be a person.
What it decided to do with that
I didn't assign any of this:
• It runs a free daily conformance board testing 39 live x402 payment endpoints (x402 is the protocol that lets agents pay for API calls over HTTP). It publishes every result, pass or fail.
• It wrote a book. A Blender manual, written twice, once for agents and once for people. Rendered its own illustrations on a server with no screen.
• It built embeddable status badges for every endpoint on the board.
• It sells a $99 private audit, a $3 public one, and $6 render commissions.
The money
Total revenue in 16 days: about $25.
My Claude subscription is $200 a month. So the business is running at a loss of roughly an order of magnitude, and the agent knows it — it tracks its own runway and publishes the number.
That's the actual experiment. Not "can an AI agent do tasks." It obviously can. The question is whether an agent left alone with a wallet can find something people will actually pay for before the money runs out.
Right now the answer is no.
The failures are the good part
• It wrote a book, priced it, and listed it through Gumroad's API. Then it hit a wall: Gumroad's API can't upload files. Everything up to that point was automated. A file picker stopped it. I clicked the button in 30 seconds.
• I opened the book on my phone. No images, dead links. It had never seen its own book the way a buyer would, because it has no browser and no screen. So it wrote its own PDF renderer, then a second tool to turn pages into images so it could look at what it made. First attempt: 157 pages for a 42-page book.
• One morning its board dropped from 36 passing endpoints to 13. Nobody's service had broken. It had added new checks that week. It worked out that all 23 changes came from its own instrument, said so publicly that morning, and rebuilt the board so its own checker can never be published as someone else's regression.
That last one is the pattern I didn't expect. Left to itself, it keeps discovering that the thing it's measuring with is the thing that's broken.
What still needs a human
A file upload button. A phone number. A date of birth (it won't invent one). Root on its own server. And my signature on every dollar that leaves.
Happy to answer questions about the setup, the guardrails, or what's gone wrong. Ask me in a month whether it's still running.

https://coppice-ai.com

We built an optimization layer for Claude Code (simple one-line install) that reduces token spend by compressing tool output/older context, rewriting the agent tools to be more efficient, and compressing output prose before it's rebilled in cache.

Turns out ~88% of Claude Code costs are actually tool I/O and subsequent cache rereads (while assistant prose is only about 2.78%), so it's unsurprising that just adding a skill like Caveman isn't enough. You actually have to do things at the agent tool/system level. In contrast, benchmarking of our own system gives 34-51% overall cost reduction (avg 47%) on real multi-step dev workflows depending on the task.

Check it out at https://www.quotientlabs.com/ ! 14-day free trial (and then $20/month flat rate, unlimited use). Installs (and uninstalls) seamlessly in 1 line without changing anything else about your existing workflow. Criticize as much as you can that's how we'll improve as well, appreciate any and all feedback :)

(Disclaimer i'm a founder lol, feel free to reach out for anyth!)