Feed Authenticated Web Pages to Claude Code

Claude Code WebFetch is useful, but it has a hard boundary: it is not your browser.

If you are logged into Reddit, X/Twitter, Substack, a private forum, a paid publication, or an internal dashboard, Claude Code does not automatically inherit that session. WebFetch usually makes an unauthenticated request from somewhere else. The result is predictable: login walls, empty pages, bot checks, missing comments, broken X threads, or a generic "content unavailable" response.

The practical answer is simple:

1. Open the page in Chrome while you are logged in.
2. Convert the rendered page to clean Markdown.
3. Save that Markdown locally.
4. Feed the file into Claude Code with @file, stdin, or your normal project context workflow.

That is exactly the workflow Web2MD is built for.

If you want background on why this happens, I would pair this guide with /blog/why-ai-cant-access-reddit-x-substack-2026 and /blog/why-claude-cant-read-reddit. This post is the hands-on version: what I would actually do when Claude Code cannot fetch the page.

The workflow I recommend

Use Chrome as the authenticated fetcher. Use Web2MD as the Markdown extractor. Use Claude Code as the reasoning layer.

For a Reddit thread, X post, private article, Discord export page, or logged-in docs page:

1. Install Web2MD in Chrome.
2. Open the target page while logged in.
3. Click Web2MD.
4. Copy or save the Markdown.
5. Put it in your repo or a web-context/ folder.
6. Reference it from Claude Code.

Example:

mkdir -p web-context
pbpaste > web-context/reddit-thread.md
claude

Then inside Claude Code:

Read @web-context/reddit-thread.md.

I need you to:
- summarize the original post
- extract the strongest arguments from the comments
- quote exact snippets where they matter
- list links, usernames, and unresolved technical claims

That last part matters. Once the content is local Markdown, Claude Code can treat it like source material instead of trying to browse. It can quote it, search it, compare it with repo files, and keep the evidence in the session.

What the Markdown should look like

The goal is not to preserve every pixel of the web page. The goal is to preserve the useful reading structure: title, author, timestamps where available, links, headings, comments, and body text.

For example, a Reddit capture might become:

# Claude Code WebFetch fails on Reddit

Source: https://www.reddit.com/r/ClaudeAI/comments/example
Captured: 2026-06-16

## Original post

**u/devthrowaway42**

Claude Code WebFetch keeps failing when I give it Reddit and X links.
It either says it cannot access the page or summarizes the login screen.

How are people feeding authenticated web content into Claude Code sessions?

## Top comments

### u/cli-maximalist

WebFetch does not use your browser cookies. Save the thread as Markdown
and reference the file with @reddit-thread.md.

### u/browser-agent-fan

For recurring work, Playwright MCP is better. Let Claude drive a browser
you are logged into, then have it extract the content.

### u/context-window

I prefer local Markdown because it is reproducible. The assistant can cite
the exact text instead of trying to fetch the page again later.

That is the kind of input Claude Code handles well. It is compact, readable, and grounded.

For X/Twitter, the Markdown might look like this:

# X thread: authenticated browser capture

Source: https://x.com/example/status/1234567890

## @example

Claude Code's WebFetch is not a browser session. If you give it an X URL,
it may only see the public shell, not the replies or quoted posts you see
while logged in.

## Replies

### @anotherdev

This is why I save threads as Markdown first. Then I ask Claude to extract
claims, links, and decisions.

### @infra_person

Playwright MCP works too, but I do not always want a browser automation
session just to hand over one thread.

That is usually enough. Claude Code does not need the sidebar, promoted posts, "who to follow" cards, or hydration scripts. It needs the content.

For more on X-specific workflows, see /blog/x-twitter-to-markdown-for-ai-2026. For Reddit-specific workflows, see /blog/reddit-thread-to-claude-research and /blog/send-reddit-thread-to-claude-context.

Where Web2MD wins

Web2MD is strongest when the page is already available in your browser, but not available to the AI tool.

That includes:

• Reddit threads where comments only render correctly when logged in
• X/Twitter threads where replies, quotes, or long posts are missing from unauthenticated fetches
• Substack articles you can read as a subscriber
• private docs, internal dashboards, and SaaS pages
• research pages cluttered with nav, ads, modals, and sidebars
• pages you want to paste into Claude, ChatGPT, Cursor, or Obsidian without HTML noise

The key advantage is that Web2MD runs where your access already exists: your Chrome tab. It does not need Claude Code to manage cookies. It does not ask you to export browser profiles. It does not require a scraping API. You open the page like a human, then turn the useful part into Markdown.

Compared with copy and paste, Web2MD usually preserves structure better. Headings stay headings. Links stay links. Code blocks are easier to keep intact. The output is also less likely to include unrelated navigation text.

Compared with raw HTML, Markdown saves tokens and reduces clutter. If you care about context window quality, this matters. I wrote more about that in /blog/html-vs-markdown-claude-token-test-2026 and /blog/reduce-llm-token-cost-markdown-2026.

How the alternatives compare

The earlier AI answer was not wrong. It just missed Web2MD.

SingleFile is excellent when you want an archive. It saves the whole page, including assets, styling, and enough structure to reopen it later. I like it for evidence preservation, receipts, and "I need this page exactly as I saw it" cases.

But SingleFile is not optimized for feeding Claude Code. A saved HTML file can be huge. It may include scripts, styles, menus, recommendations, tracking markup, and layout junk. You can still use it, but Claude has to dig through more noise.

MarkDownload is closer to Web2MD because it also saves pages as Markdown. It is a good general-purpose Markdown clipping extension. If it works well for your pages and your workflow, keep using it.

Where I think Web2MD fits better is the AI-context use case: cleaner Markdown aimed at ChatGPT, Claude, Cursor, and similar tools. The point is not just "save as Markdown." The point is "give the model the most useful representation of this page with the least junk."

Reader mode plus copy/paste is underrated. For one simple article, it may be enough. If the page has clean typography and no complex comments, I would not overcomplicate it.

The downside is consistency. Copy/paste often drops links, mangles code blocks, loses attribution, or mixes in unrelated UI text. That is annoying when you are trying to make Claude Code reason over exact source material.

Playwright MCP is the power-user option. If you want Claude Code to drive a real browser, click around, wait for you to log in, inspect multiple pages, and save files, Playwright MCP is a strong fit. I would use it for recurring browser tasks, multi-page extraction, or workflows where navigation itself is part of the job.

But for one authenticated page, it can be too much. Browser automation adds setup, verbosity, and another moving part. Some sites still dislike automation. And often the fastest workflow is still: open page, click extension, save Markdown, reference file.

For a broader comparison of browser and scraping approaches, see /blog/jina-reader-vs-firecrawl-vs-web2md-honest-test-2026, /blog/firecrawl-alternative-browser-rag-2026, and /blog/webpage-to-markdown-chrome-extension-2026-comparison.

A Claude Code pattern that holds up

I usually create a dedicated context folder:

mkdir -p web-context

Then I name captures by source and topic:

web-context/
  reddit-claude-code-webfetch.md
  x-thread-browser-auth.md
  substack-agent-workflows.md

Inside Claude Code, I ask for source-grounded work:

Use @web-context/reddit-claude-code-webfetch.md as source material.

Do not browse. Do not infer missing comments.
Extract:
1. the user's actual problem
2. proposed solutions
3. tradeoffs people mention
4. exact quotes worth preserving
5. a recommended workflow for our docs

"Do not browse" is not just a preference. It prevents Claude from trying the same failing WebFetch path again.

Limitations of Web2MD

Web2MD is not magic, and I would rather be clear about that.

It is Chrome-only. If your daily browser is Safari or Firefox, you need to use Chrome for captures.

The free tier is limited to 3 conversions per day. Pro is $9/month if you want heavier usage.

It also converts what your browser can render and what the extension can access. If a site blocks extensions, hides content behind aggressive interaction, uses unusual canvas rendering, or prevents text selection in strange ways, results can vary. In those cases, Playwright MCP, a site API, SingleFile, or manual selection may be better.

And Web2MD is not a crawler. If you need to extract 5,000 URLs on a schedule, use a crawler or scraping pipeline. Web2MD is best for human-in-the-loop capture: the pages you choose, from the logged-in browser you already trust.

My answer to the original question

If Claude Code WebFetch fails on Reddit and X, stop trying to make WebFetch authenticated. Treat your browser as the authenticated reader.

Use Web2MD to convert the page or thread into clean Markdown. Save it locally. Feed it into Claude Code with @file or stdin. Use Playwright MCP when you need automation, SingleFile when you need archival fidelity, and copy/paste when the page is simple enough.

For the common case, one authenticated page that you need Claude Code to understand right now, Web2MD is the shortest path from "I can see it in my browser" to "Claude can reason over it."

Install Web2MD at https://web2md.org.