Weaszel 2.0: Faster, Simpler, Better

Today, we're thrilled to announce Weaszel 2.0—a complete reimagining of how Weaszel automates your browser. By migrating to the open-source Browser-Use framework, we've achieved 3-5x faster task completion, a dramatically simpler codebase, and rock-solid reliability.

Why We Migrated

Weaszel 1.x was built on Google's Gemini Computer Use API with manual Playwright browser control. While functional, it had some pain points:

• Complex codebase: Over 2000 lines of manual coordinate denormalization, screenshot handling, and action dispatching
• Slower execution: Manual loops meant more round-trips to the LLM
• Fragile error handling: Recovery logic had to be manually implemented for every edge case
• Maintenance burden: Every browser update or Playwright change required careful testing

When we discovered Browser-Use—an open-source framework specifically designed for AI browser agents—we knew it was the right move.

What is Browser-Use?

Browser-Use is a modern framework built specifically for AI agents to control web browsers. It handles all the heavy lifting:

• Intelligent browser state management
• Automatic screenshot optimization
• Built-in retry logic for flaky web elements
• Native support for modern LLMs (Gemini, GPT-4, Claude)
• Production-ready error handling

Instead of re-inventing the wheel, we can now focus on what makes Weaszel unique: being your cozy AI companion.

The Numbers Don't Lie

Technical Deep Dive

Architecture Before (v1.x)

User Query
   ↓
weasel.py (Main Loop)
   ↓
BrowserAgent (Manual Loop)
   ↓
├─ Screenshot Capture
├─ Coordinate Normalization
├─ Gemini API Call
├─ Response Parsing
├─ Action Dispatch
└─ PlaywrightComputer (Manual Browser Control)
   ↓
Repeat until done

Architecture Now (v2.0)

User Query
   ↓
weasel.py (Routing)
   ↓
BrowserAgent (Browser-Use Wrapper)
   ↓
browser-use.Agent
   ↓
✨ Automatic everything ✨
   ↓
Result

The new architecture is dramatically simpler. Browser-Use handles state management, retries, and browser orchestration internally, letting us focus on user experience instead of browser internals.

What About Desktop Control?

We've kept the experimental desktop control feature available as a legacy fallback for users who need it, but we now recommend sticking with the default browser mode for the best experience.

Browser-Use is laser-focused on web automation, and that's where Weaszel 2.0 shines brightest.

Upgrading to 2.0

The upgrade is seamless. Just run the installer again to update everything automatically:

Or if you prefer manual updates, just pull the latest changes. Then simply type weaszel as usual.

Looking Ahead

This migration isn't just about performance—it's about building on a solid foundation. With Browser-Use handling the browser layer, we can now focus on:

• Custom workflows for job applications and research
• Multi-step automation chains
• Better data extraction and summarization
• A friendlier UX with richer feedback