<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sz-chrome-remote-extension.git/scripts/sync-manifest-version.js, branch master</title>
<subtitle>pi-chrome, patched to drive a signed-in browser on another host through a broker, with an MCP server
</subtitle>
<id>https://git.soarez.net/sz/sz-chrome-remote-extension.git/atom?h=master</id>
<link rel='self' href='https://git.soarez.net/sz/sz-chrome-remote-extension.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/sz-chrome-remote-extension.git/'/>
<updated>2026-05-13T11:51:17+00:00</updated>
<entry>
<title>pi-chrome 0.14.9: trusted-mode primer + auto-sync manifest version</title>
<updated>2026-05-13T11:51:17+00:00</updated>
<author>
<name>Tianren Dong</name>
<email>tianrendong.dtr@gmail.com</email>
</author>
<published>2026-05-13T11:51:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/sz-chrome-remote-extension.git/commit/?id=e88e8a3a7a2258c5e7152da192effd8c788ae677'/>
<id>urn:sha1:e88e8a3a7a2258c5e7152da192effd8c788ae677</id>
<content type='text'>
- Primer teaches agents the trusted:true escape hatch for CSP-locked pages
  (github.com, banks, many SaaS) where chrome_evaluate/chrome_snapshot throw
  EvalError due to missing 'unsafe-eval'. Agents now self-escalate instead
  of giving up and asking the user.
- Corrects stale primer claim that chrome_evaluate works without 'unsafe-eval'.
- scripts/sync-manifest-version.js wired to npm version + prepublishOnly
  lifecycle hooks; kills the recurring browser-extension manifest version
  drift (cf. 0.14.4, 0.14.8).
</content>
</entry>
</feed>
