{"slug": "i-built-a-cookie-bridge-then-changed-my-entire-agent-setup", "title": "I built a cookie bridge, then changed my entire agent setup", "summary": "A developer built Browser Cookie Bridge, a macOS app that transfers cookies from Chromium browsers like Brave into AI coding agents' in-app browsers so agents can start from existing logged-in sessions. After hitting RAM limits with the Codex desktop app and session-sync gaps including passkeys, the developer moved to terminal agents in cmux and adopted Vercel Labs' agent-browser MCP with a Chrome profile-reuse rule in AGENTS.md, logging 616 agent-browser calls across 11 threads from October 8 to 11. Vercel CEO Guillermo Rauch replied to the shared setup, \"This is the way. more to come!", "body_md": "I wanted my coding agents to use the websites I was already logged into. That small problem ended up changing my whole setup.\n\nI started with the Codex desktop app and its in-app browser. Importing my Chrome session was convenient: the agent could work with sites where I was already signed in.\n\nThen I switched to Brave, and the import option I needed was missing. My accounts were signed in over there while the agent was working somewhere else.\n\nSo I built Browser Cookie Bridge, a macOS app that started by moving Brave cookies into Codex and grew to support more Chromium browsers.\n\nWhen I tried Grok Bot later, I used Cookie Bridge there too, exporting a cookie bundle into its browser. I kept wanting the same thing: let the agent start from the session I already have.\n\nThe code: [https://github.com/apoorvdarshan/browser-cookie-bridge](https://github.com/apoorvdarshan/browser-cookie-bridge)\n\nThe RAM usage of the Codex desktop app eventually pushed me toward terminal interfaces. I started using cmux, which also had an in-app browser with session import built in.\n\nThat helped, but I still had to sync often. Some Google sessions did not come across properly, and some passkey flows did not work as expected.\n\nI would start a task and end up spending time getting the browser signed in again. Cookie transfers helped, but they could not carry everything, including passkeys.\n\nEventually I tried agent-browser from Vercel Labs and added this rule to my AGENTS.md:\n\nUse the agent-browser MCP for web browsing by default (headless, logged out). If a site needs my login, relaunch it with `--profile Default` to reuse my Chrome logins.\n\nMost browsing starts without my accounts. When a task needs a login, the agent uses the Chrome profile flow. That flag launches a temporary copy of the profile, so session reuse becomes part of the workflow instead of another import I have to arrange by hand.\n\nI still handle a fresh login or passkey approval when needed. But now I can use Claude Code, Codex or OpenCode in cmux with the same browser rule.\n\nI shared the setup on October 9:\n\n// Detect dark theme var iframe = document.getElementById('tweet-2108313693696188526-473'); if (document.body.className.includes('dark-theme')) { iframe.src = \"https://platform.twitter.com/embed/Tweet.html?id=2108313693696188526&theme=dark\" }\n\nGuillermo Rauch replied, \"This is the way. more to come!\" A nice surprise after all that fiddling with browser sessions.\n\n// Detect dark theme var iframe = document.getElementById('tweet-2108314389170516471-245'); if (document.body.className.includes('dark-theme')) { iframe.src = \"https://platform.twitter.com/embed/Tweet.html?id=2108314389170516471&theme=dark\" }\n\nI checked my saved agent threads before writing this. Across October 8 to 11, the audit found 616 recorded agent-browser calls and command batches in 11 threads. That includes retries and batches with multiple actions, so it is a usage count, not 616 completed tasks.\n\nThose threads covered the Omi website and leaderboard, a ringtone editor, my portfolio and resume, marketing, and research. I knew I was using it a lot. The history made that obvious.\n\nThis was my follow-up:\n\n// Detect dark theme var iframe = document.getElementById('tweet-2109099239699890312-532'); if (document.body.className.includes('dark-theme')) { iframe.src = \"https://platform.twitter.com/embed/Tweet.html?id=2109099239699890312&theme=dark\" }\n\nBrowser Cookie Bridge still helps when I want sessions inside an in-app browser. For everyday work, I now prefer terminal agents with a browser tool they can call when needed.\n\nThanks [@vercel](https://x.com/vercel), [@v0](https://x.com/v0) and [@rauchg](https://x.com/rauchg) for the work you're putting into tools for builders. agent-browser has saved me a lot of time. I get to spend more of it actually shipping.\n\nI wanted to build apps. I did not expect browser logins to shape so much of how I build them.\n\nTry it: [https://agent-browser.dev](https://agent-browser.dev). Chrome profile details: [https://agent-browser.dev/sessions](https://agent-browser.dev/sessions).\n\nOriginally published on [X](https://x.com/apoorvdarshan/status/2109119525954216286).", "url": "https://wpnews.pro/news/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup", "canonical_source": "https://dev.to/apoorvdarshan/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup-3e2", "published_at": "2026-10-11 06:18:19+00:00", "updated_at": "2026-10-11 06:21:39.585876+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "agent-protocols"], "entities": ["Browser Cookie Bridge", "Codex", "Brave", "cmux", "agent-browser", "Vercel Labs", "Guillermo Rauch", "Claude Code"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup", "markdown": "https://wpnews.pro/news/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup.md", "text": "https://wpnews.pro/news/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup.txt", "jsonld": "https://wpnews.pro/news/i-built-a-cookie-bridge-then-changed-my-entire-agent-setup.jsonld"}}