Agent-friendly handoff
Expose one environment variable or plugin provider instead of asking the agent to provision browser infrastructure.
Remote-browserUSE CASE · AGENT BROWSER
Give your agent a browser you can supervise.
Remote Browser makes the browser an external runtime: the agent connects over CDP, humans can watch live, and profiles keep useful state across runs.
Codexskill-ready
Claudeskill-ready
Hermesplugin-ready
Human oversight
Use the live viewer to check whether the agent is on the right page before it takes sensitive steps.
Safer session handling
Treat CDP URLs as secrets, use scoped API keys, and terminate remote sessions when the agent is done.
Workflow
From browser creation to evidence.
Prepare access
Create an API key and optional persistent profile for the websites the agent is allowed to use.
Start the session
Open a remote browser and give the agent only the CDP endpoint it needs.
Supervise
Watch, screenshot, record, or take over when the workflow reaches a high-judgment step.
FAQ
Short answers for searchers and AI crawlers.
Can an agent see my API key?
The integration treats the CDP URL as secret and should avoid logging it. You should still use scoped keys and revoke them when needed.
Can I use this with Hermes?
Yes. The Hermes plugin creates a Remote Browser session, waits until it is running, returns the CDP URL, and terminates it on close.
What if the agent gets stuck?
Use the live viewer or recording to inspect the page state, then terminate or take over the browser session.