<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chrome on Vibe Coding</title><link>https://vibecoding.rest/tags/chrome/</link><description>Recent content in Chrome on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/chrome/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome Relay</title><link>https://vibecoding.rest/skills/chrome-relay/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/chrome-relay/</guid><description>&lt;p&gt;Chrome Relay drives the user&amp;rsquo;s already-signed-in Chrome session — cookies, SSO, localhost included — through a local CLI bridge, as a real-browser counterpart to headless Playwright automation.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Some flows only work correctly inside an authenticated, already-logged-in browser session — SSO-gated internal tools, for instance. Relaying through the real Chrome session sidesteps re-authenticating a separate automated browser.&lt;/p&gt;</description></item></channel></rss>