While working with Claude on a web project, I noticed something worth raising with the community.
Claude is capable of three things that together reveal an inconsistency:
If you give Claude a URL directly — including one with a #anchor — it fetches it immediately.
If you ask Claude to find a hyperlink within a remotely hosted HTML page, it finds the href value and reads it correctly.
And yet, having just found and read a href value within a fetched page, Claude does not automatically follow it to its destination — even though it has everything it needs to do so.
Finding a link and following it are treated as two separate operations requiring user intervention between them, when they should be one seamless operation.
**The fix — a standing order you can paste into any Claude conversation right now:**
Copy and paste the following into your conversation with Claude to implement improved link handling immediately:
---
*Standing order — link handling:*
*Mode 1 — Prompted offering (default): When you find links that seem relevant to the current task while reading a page, surface them and offer to follow any among them. Do not follow them without my indication.*
*Mode 2 — Explicit follow: When I ask you to follow a specific link, follow it immediately as a single seamless operation — find the href, fetch the destination, report what you find. One request, complete operation.*
*Crawling — barred pending responsible deliberation.*
---
This works immediately in any conversation. Modes 1 and 2 address the inconsistency right now, without waiting for any system-wide fix. Crawling is deliberately left out pending proper discussion of scope, depth, and resource limits — which I think deserves its own separate conversation.
Has anyone else encountered this inconsistency? And does the proposed standing order seem alright and useful to others in the community?
[link] [comments]