Thanks for again for the interest in my previous experiment “Debugging automation by playwright MCP”

I tried something different this time, and wanted to share the results with u

What’s different from my last demo

The previous one, I used Claude Code built-in Playwight MCP. This time, I downloaded playwright by myself by docker.(mcr.microsoft.com/playwright:v1.49.0-jammy)

And tried a Playwright based automation engine, which is I extended by myself, running with “no LLM”

It looks same browser, but completely different model with previous one.

2. Test Conditions

Intenationally strictly made conditions;

No LLM(no API, no interdace engine)

No internet

even though those restrictions test result showed pass

3. About Video Quality

I orignally wanted to use professional, and PC embedded recordings, but for some reasons it didnt work well with recording Window Web UI.

Sorry for the low quality..(But the run is real)

4. Implementation is simple

Core Ideas are as below;

Read the DOM → classify the current page (Login / Form / Dashboard / Error)

Use rule-based logic to decide the next action

Let Playwright execute actions in the browser

So the architecture is:

Judgment = local rule engine Execution = Playwright

5. Next experiment

What will happen when an LLM starts using this rule-based offline engine as part of its own workflow

6. Feedback welcome


QTo be clear, this is not about replacing LLMs. It’s about reducing unnecessary LLM usage and improving reliability.

It works offline because the agent directly reads the DOM, classifies page states deterministically, and selects actions through a rule-based judgment engine — no LLM in the loop.

I built a brower automation agent that runs with NO LLM and NO Internet. Here is the domo