<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Browser Automation on Po-Wei Chen, MD — Physiatrist &amp; Builder</title><link>https://drpwchen.com/en/tags/browser-automation/</link><description>Recent content in Browser Automation on Po-Wei Chen, MD — Physiatrist &amp; Builder</description><image><title>Po-Wei Chen, MD — Physiatrist &amp; Builder</title><url>https://drpwchen.com/og-default.png</url><link>https://drpwchen.com/og-default.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 09 Aug 2026 22:50:00 +0800</lastBuildDate><atom:link href="https://drpwchen.com/en/tags/browser-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Storing Passwords in the Browser While Letting AI Drive It: Is This Safe?</title><link>https://drpwchen.com/en/posts/kimi-webbridge-lockdown/</link><pubDate>Sun, 09 Aug 2026 22:50:00 +0800</pubDate><guid>https://drpwchen.com/en/posts/kimi-webbridge-lockdown/</guid><description>A junior colleague asked a great question. Breaking the answer down into two layers: where to store passwords is easy to solve, but the real issue is AI operating the browser with your logged-in identity. Testing shows that the extension&amp;#39;s site access whitelist can&amp;#39;t stop these tools; what actually works is the browser policy layer—built into an open-source, one-click setup tool.</description></item></channel></rss>