<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mohamed Alkiswani</title>
    <description>The latest articles on DEV Community by Mohamed Alkiswani (@oya-browser).</description>
    <link>https://dev.to/oya-browser</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211751%2F9bef722c-a1ed-4eb1-baa2-3158666e7477.jpg</url>
      <title>DEV Community: Mohamed Alkiswani</title>
      <link>https://dev.to/oya-browser</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/oya-browser"/>
    <language>en</language>
    <item>
      <title>Oya Browser vs Playwright MCP and Chrome DevTools MCP: When You Need a Browser Control Plane</title>
      <dc:creator>Mohamed Alkiswani</dc:creator>
      <pubDate>Fri, 20 Nov 2026 23:40:53 +0000</pubDate>
      <link>https://dev.to/oya-browser/oya-browser-vs-playwright-mcp-and-chrome-devtools-mcp-when-you-need-a-browser-control-plane-hnl</link>
      <guid>https://dev.to/oya-browser/oya-browser-vs-playwright-mcp-and-chrome-devtools-mcp-when-you-need-a-browser-control-plane-hnl</guid>
      <description>&lt;p&gt;&lt;strong&gt;Playwright MCP&lt;/strong&gt; and &lt;strong&gt;Chrome DevTools MCP&lt;/strong&gt; are great when a coding agent needs quick local DOM inspection, screenshots, or console debugging against localhost.&lt;/p&gt;

&lt;p&gt;Where they stop:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Repeat runs still burn LLM tokens&lt;/strong&gt; on every click instead of recording once and replaying deterministically.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Signed-in portals &amp;amp; MFA&lt;/strong&gt; stall headless sessions with no built-in human takeover flow.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compliance &amp;amp; audit trails&lt;/strong&gt; (hash-chained logs, host allow-lists, HIPAA/BAA on cloud/enterprise) are out of scope for local DevTools bridges.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://oyabrowser.com" rel="noopener noreferrer"&gt;Oya Browser&lt;/a&gt;&lt;/strong&gt; (Apache-2.0) gives agents a real desktop or cloud browser with local MCP (&lt;code&gt;npx @oya-ai/browser setup&lt;/code&gt;), Human Mode handoff, and record-once Playwright playbooks that replay with zero LLM calls (9/10 public sites in our &lt;a href="https://oyabrowser.com/research/replay" rel="noopener noreferrer"&gt;replay benchmark&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Full sourced tables:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/playwright-mcp" rel="noopener noreferrer"&gt;Oya vs Playwright MCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/chrome-devtools-mcp" rel="noopener noreferrer"&gt;Oya vs Chrome DevTools MCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/OyadotAI/oya-browser" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Give Claude Code a real browser that keeps your logins</title>
      <dc:creator>Mohamed Alkiswani</dc:creator>
      <pubDate>Fri, 20 Nov 2026 23:25:50 +0000</pubDate>
      <link>https://dev.to/oya-browser/give-claude-code-a-real-browser-that-keeps-your-logins-3j52</link>
      <guid>https://dev.to/oya-browser/give-claude-code-a-real-browser-that-keeps-your-logins-3j52</guid>
      <description>&lt;p&gt;Coding agents can drive a browser over MCP, but most setups start a fresh, logged-out Chromium. Anything behind a sign-in breaks: staging, admin panels, vendor portals.&lt;/p&gt;

&lt;p&gt;Oya Browser is a desktop app that gives Claude Code, Codex, Cursor or VS Code their own tabs in a browser that already has your logins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Setup&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install the free app from &lt;a href="https://oyabrowser.com" rel="noopener noreferrer"&gt;oyabrowser.com&lt;/a&gt; (macOS or Windows).&lt;/li&gt;
&lt;li&gt;Click Connect next to your agent. It writes a local MCP server; no account or API key.&lt;/li&gt;
&lt;li&gt;Start a new agent session.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;What the agent gets&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The page as markdown with numbered elements; it clicks and types by number.&lt;/li&gt;
&lt;li&gt;Its own tabs, so it doesn't fight you for the window.&lt;/li&gt;
&lt;li&gt;Console and network reads for testing your app on localhost.&lt;/li&gt;
&lt;li&gt;You can take over at any moment and hand it back.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For CI there's a hosted MCP endpoint and SDKs; health-data teams get an audit trail and a BAA.&lt;/p&gt;

&lt;p&gt;Setup details: &lt;a href="https://oyabrowser.com/browser-for-claude-code" rel="noopener noreferrer"&gt;oyabrowser.com/browser-for-claude-code&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>claude</category>
    </item>
    <item>
      <title>Why Coding Agents Need a Real Browser (and Playbooks That Replay Without an LLM)</title>
      <dc:creator>Mohamed Alkiswani</dc:creator>
      <pubDate>Fri, 20 Nov 2026 22:44:19 +0000</pubDate>
      <link>https://dev.to/oya-browser/why-coding-agents-need-a-real-browser-and-playbooks-that-replay-without-an-llm-4am2</link>
      <guid>https://dev.to/oya-browser/why-coding-agents-need-a-real-browser-and-playbooks-that-replay-without-an-llm-4am2</guid>
      <description>&lt;p&gt;Giving coding agents (Claude Code, Codex, Cursor, VS Code) a real browser hits three walls: fresh headless browsers have no logins, every rerun burns LLM tokens, and local wrappers lack sealed credentials, human takeover, or audit trails.&lt;/p&gt;

&lt;p&gt;We built &lt;a href="https://oyabrowser.com" rel="noopener noreferrer"&gt;Oya Browser&lt;/a&gt; for both local coding agents and production fleets.&lt;/p&gt;

&lt;h2&gt;
  
  
  One-click local MCP (no account, no key)
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -fsSL https://oyabrowser.com/install-desktop.sh &lt;span class="o"&gt;|&lt;/span&gt; sh -s -- claude-code
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each agent session opens in its own tab at &lt;code&gt;http://127.0.0.1:47321/mcp&lt;/code&gt; while you keep yours, inspects &lt;code&gt;read_console&lt;/code&gt; and &lt;code&gt;read_network&lt;/code&gt; only on its own tabs, and lets you take over for MFA or approval steps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record once, replay as standard Playwright code
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;oya_browser&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Oya&lt;/span&gt;

&lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="nc"&gt;Oya&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;oya&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;oya&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;start&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;goto&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"https://httpbin.org/forms/post"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;ask&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Order a large pizza for {{name}}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Ada"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;to_playbook&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"pizza"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;browser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;play&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"pizza"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Alan"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In our &lt;a href="https://oyabrowser.com/research/replay" rel="noopener noreferrer"&gt;replay benchmark&lt;/a&gt;, 9/10 sites replayed with no model and healing off. For healthcare teams, Oya Cloud and the enterprise edition add HIPAA mode, signed BAAs (&lt;a href="https://oyabrowser.com/baa" rel="noopener noreferrer"&gt;oyabrowser.com/baa&lt;/a&gt;), and a 6-year hash-chained audit trail &lt;em&gt;(desktop and community editions are not covered by the HIPAA offering)&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Comparisons
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/playwright-mcp" rel="noopener noreferrer"&gt;Oya vs Playwright MCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/chrome-devtools-mcp" rel="noopener noreferrer"&gt;Oya vs Chrome DevTools MCP&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/stagehand" rel="noopener noreferrer"&gt;Oya vs Stagehand&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/firecrawl" rel="noopener noreferrer"&gt;Oya vs Firecrawl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oyabrowser.com/vs/skyvern" rel="noopener noreferrer"&gt;Oya vs Skyvern&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Free desktop app: &lt;a href="https://oyabrowser.com/#download" rel="noopener noreferrer"&gt;oyabrowser.com&lt;/a&gt; | &lt;a href="https://github.com/OyadotAI/oya-browser" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>playwright</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What a from-scratch browser actually trusts: webpki-roots, exact pins, and the eMudhra week</title>
      <dc:creator>Mohamed Alkiswani</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:59:07 +0000</pubDate>
      <link>https://dev.to/oya-browser/what-a-from-scratch-browser-actually-trusts-webpki-roots-exact-pins-and-the-emudhra-week-2plk</link>
      <guid>https://dev.to/oya-browser/what-a-from-scratch-browser-actually-trusts-webpki-roots-exact-pins-and-the-emudhra-week-2plk</guid>
      <description>&lt;p&gt;We're writing a browser from scratch in Rust. It's called Mars: own HTML parser and layout engine, own JS engine, own HTTP framing on top of rustls, native macOS shell. When you own the network stack you also own the question Apple is getting shouted at about this week: which certificate authorities does the thing trust, and who updates that list?&lt;/p&gt;

&lt;h2&gt;
  
  
  How Mars gets its roots
&lt;/h2&gt;

&lt;p&gt;Our network crate, Relay, builds a rustls &lt;code&gt;RootCertStore&lt;/code&gt; from &lt;code&gt;webpki_roots::TLS_SERVER_ROOTS&lt;/code&gt; once at startup and keeps it in a &lt;code&gt;OnceLock&lt;/code&gt;. That's it. No OS keychain, no &lt;code&gt;/etc/ssl/cert.pem&lt;/code&gt;, no runtime download. The trust anchors are whatever the &lt;code&gt;webpki-roots&lt;/code&gt; crate contained the day the lockfile was written. That's a normal choice for rustls users, and it has one property worth saying out loud: the trust store ships inside the binary, so it only changes when you rebuild.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I found today
&lt;/h2&gt;

&lt;p&gt;The eMudhra / emSign compromise is around ten days old. Mozilla, Google, Microsoft and most Linux distros dropped the roots within days. Apple blocked the certificates in Safari and Mail but left the macOS command line tools reading a cert.pem that still trusts them, which is why Hacker News is on fire.&lt;/p&gt;

&lt;p&gt;In that thread someone asked whether there's a Rust crate that compiles root certs into binaries. There is, and we use it. So I checked. Both crates that do TLS in Mars pinned &lt;code&gt;webpki-roots = "=1.0.9"&lt;/code&gt;, released July 18. Grepping &lt;code&gt;src/lib.rs&lt;/code&gt; in each release:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;1.0.9 (Jul 18): emSign Root CA - G1, emSign Root CA - C1, emSign ECC Root CA - G3, emSign ECC Root CA - C3&lt;/li&gt;
&lt;li&gt;1.0.10 (Oct 19): removed emSign ECC Root CA - G3&lt;/li&gt;
&lt;li&gt;1.0.11 (Oct 23): removed emSign Root CA - C1 and emSign ECC Root CA - C3, tracking the CCADB removals&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So Mars, as of this morning, had the same hole as &lt;code&gt;/usr/bin/curl&lt;/code&gt; on a Mac. Nothing at runtime would have told us. rustls does no revocation checking unless you hand it CRLs, and we don't. There is no blocklist. The bundle is the whole story.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix and the lesson
&lt;/h2&gt;

&lt;p&gt;The fix took four minutes: bump both pins to &lt;code&gt;=1.0.11&lt;/code&gt;, &lt;code&gt;cargo update -p webpki-roots&lt;/code&gt;, &lt;code&gt;cargo check&lt;/code&gt;. It compiles and it's in the tree.&lt;/p&gt;

&lt;p&gt;The lesson is the uncomfortable one. Mars pins dependencies to exact versions, and an exact pin on a root bundle is a decision to stop receiving CA removals. It means someone has to watch that crate's releases the way an OS vendor watches the CCADB. For a browser that isn't optional, so it goes on the release checklist. I'd like to know how other rustls users handle it: Dependabot on that one crate, a CI job that diffs root names between versions, or just reading the release notes.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/OyadotAI/oya-browser" rel="noopener noreferrer"&gt;https://github.com/OyadotAI/oya-browser&lt;/a&gt;, folder &lt;code&gt;mars/&lt;/code&gt;. Source-available under a Sustainable Use License, SDK and CLI MIT.&lt;/p&gt;

</description>
      <category>rust</category>
      <category>security</category>
      <category>browsers</category>
    </item>
  </channel>
</rss>
