OpenClaw is an open-source AI agent that can run shell commands and use CLI tools to interact with external services. By installing Steel CLI and the steel-browser skill, it gains access to a real cloud browser with stealth mode, proxies, CAPTCHA solving, and computer actions via Playwright.

How do you give OpenClaw browser access with Steel?

Install Steel CLI with `curl -LsSf https://setup.steel.dev | sh`, then add the steel-browser skill with `npx skills add https://github.com/steel-dev/cli --skill steel-browser`. Get a free API key at app.steel.dev. Paste it in chat when OpenClaw asks, or add it as an environment variable through OpenClaw's interface so it's not stored in your conversation history.

Can an AI agent fill out web forms automatically?

Yes. With Steel CLI installed, OpenClaw can navigate to a form, explore the fields, fill them out, and submit. It handles most standard form elements, though browser-native dropdowns require a fallback approach: the agent takes a screenshot, translates the target to coordinates, and uses a Playwright computer action to click the right option. Complex forms may take multiple session attempts.

How do you watch what an AI agent is doing in the browser?

Steel provides a live session URL for every active browser session. OpenClaw includes this URL in its responses, so you can open Steel's dashboard and watch the browser render in real time. If the agent misclicks or gets stuck, you see it happen and can intervene. Steel also keeps a full session replay after the fact, so you can review every navigation, click, and retry even if you weren't watching live.

What web forms work well for AI agent automation?

Multi-field web forms without aggressive bot detection work well. The more CAPTCHA checkpoints or dynamic conditional logic a form has, the more session attempts it will take. For sites where you're already logged in, use `steel profile import` to copy your Chrome session over before starting — this is faster and more reliable than having the agent handle authentication from scratch.

What is steel profile import and when should I use it?

`steel profile import` copies cookies and login state from your local Chrome browser into Steel. Sessions started with an imported profile inherit your existing authentication, so the agent starts already logged in to Gmail, Slack, dashboards, or any other site you're signed into. Use it for any site that requires authentication — it avoids OAuth flows, 2FA prompts, and credential entry entirely.

6.8K

OpenClaw + Steel Browser: Let Your AI Agent Fill the Forms

Apr 9, 2026

San Francisco

Nikola Balic

OpenClaw can shell out. Give it Steel CLI and the steel-browser skill and it has a real cloud browser: stealth mode, proxies, CAPTCHA solving, computer actions via Playwright. We pointed it at the AI Engineer World's Fair call for speakers and told it to apply.

It took 15 minutes. Swyx is probably not happy about what got submitted. OpenClaw did it.

Setup

Install Steel CLI:

curl -LsSf https://setup.steel.dev | sh

curl -LsSf https://setup.steel.dev | sh

curl -LsSf https://setup.steel.dev | sh

curl -LsSf https://setup.steel.dev | sh

Install the browser skill:

npx skills add https://github.com/steel-dev/cli --skill

npx skills add https://github.com/steel-dev/cli --skill

npx skills add https://github.com/steel-dev/cli --skill

npx skills add https://github.com/steel-dev/cli --skill

Get a free API key at app.steel.dev. Paste it in chat when OpenClaw asks. Better: add it as an environment variable through OpenClaw's interface so it's not sitting in your conversation history.

What happened

We gave OpenClaw one instruction:

I would like to submit an application for the call for speakers for AI Engineer World's Fair. Could you figure out what the fields are, what we need, and how I can apply to become a speaker?

The agent created a Steel session and started navigating. We watched from Steel's dashboard.

It found the right page on its own. Explored the form. Drafted a submission.

Watching it work

You don't have to watch. But it's useful sometimes.

OpenClaw pipes Steel's live session URL back into its responses. Open it and you see exactly what the browser is rendering as the agent works. When it misclicks or gets stuck in a modal, you see it. Step in, say something, the agent adjusts.

When you can't watch live, you replay. Steel keeps the full session: every navigation, every click, every retry.

OpenClaw is good at brute forcing

Works on regular web forms. The more bot-detection a site has, the slower it gets. Multi-step forms with dynamic fields or aggressive CAPTCHA checkpoints will eat sessions.

For sites where you're already logged in, don't start from scratch. steel profile import copies your Chrome session over and the agent picks up from there. The CFP form worked without any of that, but for Gmail, Slack, or any dashboard: use a profile.

Try it

curl -LsSf https://setup.steel.dev | sh
npx skills add https://github.com/steel-dev/cli --skill

curl -LsSf https://setup.steel.dev | sh
npx skills add https://github.com/steel-dev/cli --skill

curl -LsSf https://setup.steel.dev | sh
npx skills add https://github.com/steel-dev/cli --skill

curl -LsSf https://setup.steel.dev | sh
npx skills add https://github.com/steel-dev/cli --skill

Find a form you've been meaning to fill out. Give OpenClaw the URL and a one-sentence brief. Watch the session. Let it fight through the dropdowns. Report back.