<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>BrowserMan Blog</title><description>Field notes on AI agents, real browser automation, delegated access, and practical workflows with BrowserMan.</description><link>https://blog.browserman.run/</link><item><title>Browser agents need completion contracts, not just approval prompts</title><link>https://blog.browserman.run/blog/browser-agents-need-completion-contracts/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agents-need-completion-contracts/</guid><description>Approval gates stop risky browser actions. Completion contracts prove whether an agent used the right session, stayed inside scope, handled drift, and left evidence that the work actually finished.</description><pubDate>Sat, 23 May 2026 00:00:00 GMT</pubDate></item><item><title>Why browser agents stay stuck as POCs</title><link>https://blog.browserman.run/blog/browser-agents-stuck-as-pocs/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agents-stuck-as-pocs/</guid><description>Browser-agent demos do not fail because the agent cannot click. They fail when real logged-in browser work needs reliability, scope, traces, receipts, recovery, and revocation.</description><pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate></item><item><title>The browser session is an authority surface</title><link>https://blog.browserman.run/blog/browser-session-authority-surface/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-session-authority-surface/</guid><description>Agent demos make browser use look like a control problem. In production, a real logged-in browser session is delegated authority.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate></item><item><title>The Approve Button Is the Boundary Between Drafting and Doing</title><link>https://blog.browserman.run/blog/approve-button-boundary-drafting-doing/</link><guid isPermaLink="true">https://blog.browserman.run/blog/approve-button-boundary-drafting-doing/</guid><description>Drafting is cheap. Doing creates side effects. For browser agents that can refund, publish, message, or update records, approval gates and receipts are the real product boundary.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate></item><item><title>Browser-action receipts are not logs</title><link>https://blog.browserman.run/blog/browser-action-receipts-are-not-logs/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-action-receipts-are-not-logs/</guid><description>Browser-agent logs help developers debug. Browser-action receipts prove what authority was delegated, what changed, and how a team can review or undo the handoff.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate></item><item><title>Screenshots Are Not Browser State</title><link>https://blog.browserman.run/blog/screenshots-are-not-browser-state/</link><guid isPermaLink="true">https://blog.browserman.run/blog/screenshots-are-not-browser-state/</guid><description>Why coding agents need real Chrome loops — and why logged-in browser work needs delegated authority, approval lines, and receipts.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate></item><item><title>Browser agents do not fail at clicking. They fail at handoff.</title><link>https://blog.browserman.run/blog/browser-agents-fail-at-handoff/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agents-fail-at-handoff/</guid><description>Browser-agent demos prove capability. Production workflows fail at the handoff between systems, permissions, receipts, and user control.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate></item><item><title>Browser delegation is not a replacement for clean APIs</title><link>https://blog.browserman.run/blog/browser-delegation-is-not-a-replacement-for-clean-apis/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-delegation-is-not-a-replacement-for-clean-apis/</guid><description>Use APIs, CLIs, and MCP when they expose the right action. Use delegated browser access when real work is trapped inside logged-in web UIs.</description><pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate></item><item><title>The fixed workflow is the product</title><link>https://blog.browserman.run/blog/fixed-workflow-is-the-product/</link><guid isPermaLink="true">https://blog.browserman.run/blog/fixed-workflow-is-the-product/</guid><description>No one buys an agent with browser access. They buy repaired workflows: lead follow-up, CRM state, WISMO, support escalation, and logged-in context that stays under control.</description><pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate></item><item><title>Trust-sensitive agents need visible friction</title><link>https://blog.browserman.run/blog/trust-sensitive-agents-need-visible-friction/</link><guid isPermaLink="true">https://blog.browserman.run/blog/trust-sensitive-agents-need-visible-friction/</guid><description>Browser agents do not need friction everywhere. They need visible surfaces, proof before high-risk clicks, approval thresholds, and receipts after trust-sensitive actions.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate></item><item><title>Logs Are Too Late for High-Value Browser Actions</title><link>https://blog.browserman.run/blog/logs-are-too-late-high-value-browser-actions/</link><guid isPermaLink="true">https://blog.browserman.run/blog/logs-are-too-late-high-value-browser-actions/</guid><description>Browser agents need preflight policy, approval gates, and receipts before they can be trusted with refunds, publishing, deletion, spending, and other high-value actions.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate></item><item><title>The Browser Agent Demo Is Not the Product. The Permission Model Is.</title><link>https://blog.browserman.run/blog/browser-agent-demo-permission-model/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agent-demo-permission-model/</guid><description>Browser agents become useful when they touch real logged-in work. That is also when the product stops being the click loop and becomes scope, approval, receipts, and revoke.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate></item><item><title>Enterprise portals are where browser agents become workflows</title><link>https://blog.browserman.run/blog/enterprise-portals-browser-agents-workflows/</link><guid isPermaLink="true">https://blog.browserman.run/blog/enterprise-portals-browser-agents-workflows/</guid><description>Browser-agent demos prove an agent can click. Enterprise portals test whether the browser layer has saved actions, permission boundaries, approvals, receipts, and recovery.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate></item><item><title>Browser agents need authority-aware execution</title><link>https://blog.browserman.run/blog/authority-aware-browser-delegation/</link><guid isPermaLink="true">https://blog.browserman.run/blog/authority-aware-browser-delegation/</guid><description>Cloud agents solve where the agent runs. Browser handoff solves whose account it can safely use. For logged-in workflows, agents need permission boundaries, not just browser access.</description><pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate></item><item><title>Boring admin SaaS is where browser agents become real</title><link>https://blog.browserman.run/blog/boring-admin-saas-browser-agents/</link><guid isPermaLink="true">https://blog.browserman.run/blog/boring-admin-saas-browser-agents/</guid><description>Browser agents stop being demos when they enter logged-in admin SaaS. That is also where browser access becomes delegated authority.</description><pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate></item><item><title>Existing Chrome profiles are becoming a product primitive for agents</title><link>https://blog.browserman.run/blog/existing-chrome-profiles-product-primitive-agents/</link><guid isPermaLink="true">https://blog.browserman.run/blog/existing-chrome-profiles-product-primitive-agents/</guid><description>Browser agents keep collapsing back to the user&apos;s real Chrome profile. That solves auth, but it creates a delegation problem: session authority, approval boundaries, and receipts.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate></item><item><title>Delegated browser access vs cookie sync: the browser session is authority</title><link>https://blog.browserman.run/blog/delegated-browser-access-vs-cookie-sync/</link><guid isPermaLink="true">https://blog.browserman.run/blog/delegated-browser-access-vs-cookie-sync/</guid><description>Cloud cookie sync, isolated profiles, local Chrome attach, and delegated browser access are different authority models for AI agents. Here is how to tell them apart.</description><pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate></item><item><title>Browser access is not one permission</title><link>https://blog.browserman.run/blog/browser-access-is-not-one-permission/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-access-is-not-one-permission/</guid><description>A logged-in browser session is delegated authority. Browser agents need separate gates for read, draft, update, publish, refund, delete, and spend.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate></item><item><title>How to choose between OpenClaw hosting and Hermes Agent hosting in 2026</title><link>https://blog.browserman.run/blog/how-to-choose-openclaw-hermes-hosting-2026/</link><guid isPermaLink="true">https://blog.browserman.run/blog/how-to-choose-openclaw-hermes-hosting-2026/</guid><description>OpenClaw and Hermes Agent solve different hosting problems. Use this guide to decide when you need an always-on operator, a specialist worker, or both.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Browser agents compared: automation, infra, and delegated browser access</title><link>https://blog.browserman.run/blog/browser-agents-compared-delegated-browser-access/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agents-compared-delegated-browser-access/</guid><description>Browser agents, browser infrastructure, and delegated real-browser access solve different parts of the same problem. Here is how to tell them apart.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Browser agents should be auditable, not undetectable</title><link>https://blog.browserman.run/blog/browser-agents-should-be-auditable-not-undetectable/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agents-should-be-auditable-not-undetectable/</guid><description>Once an AI agent can use a real logged-in browser session, the product question changes: can the system scope, gate, replay, and revoke what the agent did?</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Real-Browser Agent Prompts: 6 AI Workflows for Market Research, Competitor Research, and Brand Monitoring</title><link>https://blog.browserman.run/blog/real-browser-agent-prompts-workflows/</link><guid isPermaLink="true">https://blog.browserman.run/blog/real-browser-agent-prompts-workflows/</guid><description>A practical collection of real-browser AI agent prompts for market research, competitor research, daily brand radar, ecommerce product research, social listening, and logged-in SaaS operations.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate></item><item><title>How to Build an AI Agent for Market Research with a Real Browser</title><link>https://blog.browserman.run/blog/ai-agent-market-research-real-browser/</link><guid isPermaLink="true">https://blog.browserman.run/blog/ai-agent-market-research-real-browser/</guid><description>A practical workflow for using an AI agent to collect market research from Reddit, Amazon reviews, G2, competitor pages, Taobao, and other real web sources before writing analysis.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate></item><item><title>How to Use OpenClaw and BrowserMan to Collect Taobao Market Data</title><link>https://blog.browserman.run/blog/ai-agent-taobao-sunscreen-market-analysis/</link><guid isPermaLink="true">https://blog.browserman.run/blog/ai-agent-taobao-sunscreen-market-analysis/</guid><description>A practical step-by-step guide to using OpenClaw, BrowserMan, and a real browser session to collect Taobao search results, clean ecommerce data, and turn it into market-analysis inputs.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate></item><item><title>China Sunscreen Market Report — April 2026</title><link>https://blog.browserman.run/blog/china-sunscreen-market-report-april-2026/</link><guid isPermaLink="true">https://blog.browserman.run/blog/china-sunscreen-market-report-april-2026/</guid><description>An AI-assisted market report based on 264 Taobao sunscreen search results and 140 cleaned product listings, covering price bands, claim structures, use-case segments, and complaint opportunities.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Build a Daily Brand Radar Agent with OpenClaw and BrowserMan</title><link>https://blog.browserman.run/blog/daily-brand-radar-agent-openclaw-browserman/</link><guid isPermaLink="true">https://blog.browserman.run/blog/daily-brand-radar-agent-openclaw-browserman/</guid><description>A practical setup guide for building an AI agent that uses Google Search and a real browser session to discover a brand&apos;s website, social links, competitors, and daily signals, then reports every morning.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate></item><item><title>AI marketing needs customer language, not another copy prompt</title><link>https://blog.browserman.run/blog/customer-language-bank-browser-agents/</link><guid isPermaLink="true">https://blog.browserman.run/blog/customer-language-bank-browser-agents/</guid><description>Useful marketing agents should not start from a blank chat box. They should read Amazon reviews, Reddit threads, TikTok comments, G2 complaints, support tickets, and turn real customer language into a hook bank before writing.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate></item><item><title>The accountability layer for browser agents is the execution boundary</title><link>https://blog.browserman.run/blog/accountability-layer-browser-agents-execution-boundary/</link><guid isPermaLink="true">https://blog.browserman.run/blog/accountability-layer-browser-agents-execution-boundary/</guid><description>Browser agents do not just need better dashboards. Once an agent touches a real logged-in session, accountability has to live at execution time: session scope, task intent, gates, audit logs, and revocation.</description><pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate></item><item><title>The browser-agent control plane: scope, audit, handoff, rollback</title><link>https://blog.browserman.run/blog/browser-agent-control-plane/</link><guid isPermaLink="true">https://blog.browserman.run/blog/browser-agent-control-plane/</guid><description>Browser agents do not become production-ready when they learn to click reliably. They become delegable when the product defines a control plane around the browser session: scope, approval gates, audit trails, handoff, and revoke or rollback.</description><pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Agent, Subagent, Workspace: what OpenClaw users actually need to understand</title><link>https://blog.browserman.run/blog/agent-subagent-workspace-execution-layer/</link><guid isPermaLink="true">https://blog.browserman.run/blog/agent-subagent-workspace-execution-layer/</guid><description>Agent is a role. Subagent is an isolated task instance. Workspace is often shared. The real challenge in multi-agent systems is not spinning up more agents, but coordinating execution.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate></item><item><title>What happens when your company inbox gets an AI operator?</title><link>https://blog.browserman.run/blog/cloudflare-agentic-inbox-openclaw-field-notes/</link><guid isPermaLink="true">https://blog.browserman.run/blog/cloudflare-agentic-inbox-openclaw-field-notes/</guid><description>Every company inbox quietly runs part of the business. We connected an OpenClaw agent to a real inbox to see what changes when AI can triage, draft, and send — and where the real risks begin.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why BrowserMan exists</title><link>https://blog.browserman.run/blog/why-browserman-exists/</link><guid isPermaLink="true">https://blog.browserman.run/blog/why-browserman-exists/</guid><description>Local browser tools can access a real browser. Cloud browsers can serve remote agents. BrowserMan exists because real workflows need both.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Launching the BrowserMan blog</title><link>https://blog.browserman.run/blog/launching-the-browserman-blog/</link><guid isPermaLink="true">https://blog.browserman.run/blog/launching-the-browserman-blog/</guid><description>Why BrowserMan is splitting the blog into its own Astro project and what will be published here.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate></item></channel></rss>