Tutorial3 mins

OpenClaw for beginners
A first run with OpenClaw, written as the steps I wish someone had handed me before I opened it.
OpenClaw is another AI agent, and this is the walkthrough I followed on my first run. An agent takes a goal in your own words and works through the steps to reach it, instead of waiting for you to click each one. I wrote this for a beginner who has the tool open and no idea what to type first.
Everything below is a task I checked by hand afterwards, so nothing here rests on trust I had not earned yet.
Step one, give it a goal you can check
I started with a task where I already knew the right answer. I asked OpenClaw to read three files in a folder and tell me which one was the longest.
I picked this on purpose. If I hand an agent a job I cannot verify, I have no way to tell a good answer from a confident wrong one. A task with a known answer is how I learn what the tool is like before I depend on it.
Step two, watch the steps, not the answer alone
OpenClaw does not answer in one jump. It works in steps, and it shows them. It opened each file, counted the length, and compared the three. Reading those steps mattered more than the final line, because a wrong answer usually comes from one bad step I can point to.
On my run it opened the three files and named the longest one. The answer was right, and I could see the step where it measured each file, so I believed it for the right reason.
Step three, hand it a tool and set a limit
The part that makes an agent more than a chat window is that it can use tools. A tool is any outside thing it can reach, a folder, a search, or another program. OpenClaw asked before it used one, which is the behaviour I wanted.
I gave it access to one folder and nothing else. A narrow limit is how I keep an early run safe. If the only thing it can touch is a folder of test files, the worst it can do is misread a test file.
Step four, break it on purpose
Once the happy path worked, I pointed it at a file that did not exist. I wanted to see what it did with a task it could not finish.
It did not stop. It reported that the file was missing and then offered its best guess at what the file might have said. The guess read as confident as every correct answer before it. That is the moment I want a beginner to see early, because the only defence against it is checking the output yourself.
What I took from the run
An agent keeps going where a fixed automation would halt. That is useful, and it is the reason I cannot hand OpenClaw a task I am unable to verify yet.
For now I run it on small jobs, inside one folder, and I read the steps rather than only the answer. I give the most attention to the results that look the most certain.