Verify GitHub wiki pages render correctly in the browser
A user asked Claude to check that several GitHub wiki pages rendered properly; Claude in Chrome opened the tab on the local PC rather than in the VM they expected, so it only partly worked as intended. ·
Done withClaude in ChromeClaude
- What they did
- The user asked Claude to verify that a few GitHub wiki pages rendered correctly, following Claude’s own suggestion to check them in the browser. Claude triggered its Chrome integration, but because the Claude in Chrome extension was signed into the user’s local Chrome, the browser action opened on the host PC instead of the lab VM reached over RDP; a commenter said this access is account-scoped, not machine-scoped.
- How it went
- It only partly worked for the intended setup: Claude could open the pages, but in the wrong environment, so it did not truly verify rendering inside the VM. The post reports Claude initially gave several incorrect explanations before landing on the account-linked extension behavior.
- Worth knowing
- If you want isolation on lab VMs, keep the extension out of your normal host Chrome profile or use a separate signed-out profile except when needed.
Try it yourself with Claude in Chrome
Open each of these GitHub wiki pages in my browser: [list of wiki page URLs]. For each one, check that the formatting renders correctly, including headings, tables, code blocks, images, and internal links, and click a few links to confirm they don't lead to 404s. When you're done, give me a list of pages that look fine and, for any that don't, a description of what is broken and where. Don't edit anything; just report.
Want help getting this working? Join the Vibe Coding Academy ↗ Run by Alex Finn, who also runs this site.
Source: Reddit · Sep 7, 2026
Related use cases
Build a C compiler with a team of parallel agents
Anthropic's engineering write-up on tasking Opus 4.6 agent teams with building a C compiler.
Run real estate transactions with autonomous agents
A poster built a platform where agents, including a SellerBot, handle listings, pricing strategy and buyer inquiries, built with Claude as the coding assistant.
Update fields on 400 ERP transactions in the browser
The author had Claude's Chrome extension edit 2 fields across about 400 ERP transactions; it was slow, asked for confirmation at each step and burned token limits, but ran in the background.
Turn tickets into merged pull requests
Pulls tasks from GitHub Issues or Linear, then runs Claude Code or Codex in isolated Kubernetes pods to carry each one through to a PR.
Build a first real project with Replit Agent
A student completed a real build with Replit Agent, spending about $65 in agent usage and finding the cost unexpected.
Auto-pull proven skills for Cursor on an analytics dashboard
On their analytics dashboard, Cursor's agent pulled in skills for event-store design, instrumentation and API security, adding rate limiting and input validation.
Get 5 like this every morning
The best things people got an AI agent to do, each with the prompt to try it.