diff --git a/blog/posts/automating-linkedin-content-with-ai-agent.html b/blog/posts/automating-linkedin-content-with-ai-agent.html
index 7337bb4..7e0209f 100644
--- a/blog/posts/automating-linkedin-content-with-ai-agent.html
+++ b/blog/posts/automating-linkedin-content-with-ai-agent.html
@@ -79,7 +79,7 @@
 
         <ul>
             <li><strong>Hermes Agent</strong> — Skilled with the <code>linkedin-company-post</code> and <code>linkedin-group-posting</code> workflows. It knows exactly which buttons to click, what the editor looks like, and how to verify a successful post.</li>
-            <li><strong>Chrome DevTools Protocol over SSH reverse tunnel</strong> — Brave runs on my workstation. A persistent reverse tunnel exposes its CDP endpoint at <code>127.0.0.1:9222</code> on my server. The agent sends WebSocket commands (navigate, click, type, evaluate JS) to drive the browser remotely.</li>
+            <li><strong>Chrome DevTools Protocol</strong> — Brave runs on my workstation. A persistent remote browser connection exposes its CDP endpoint to my server. The agent sends WebSocket commands (navigate, click, type, evaluate JS) to drive the browser remotely.</li>
             <li><strong>UTM-aware linking</strong> — Every link to derez.ai automatically gets <code>?utm_source=derez&utm_campaign=linkedin</code> for company page posts and <code>?utm_source=derez&utm_campaign=groups</code> for group posts. No manual tracking.</li>
             <li><strong>German UI, English content</strong> — My LinkedIn is in German. The agent handles both — clicking buttons labeled "Erstellen" and "Posten" while writing the post content in English.</li>
         </ul>