Insights
Tactical playbooks and market analysis for teams using AI browser automation.
Newsletter
Get updates on browser automation
Filter by tag
Clear filterA practical comparison of raw CDP accessibility trees, markdown-style page summaries, Chrome DevTools MCP, Playwriter, and the serialization choices behind VibeBrowser.
How we validate Chrome extension microphone initialization and listening-state transitions with manifest permission auditing, explicit FAIL vs SKIP semantics, and a virtual microphone in CI.
A practical engineering walkthrough of our MCP/CLI architecture: extension-first routing, relay-owned Chrome DevTools fallback, explicit --devtools mode, and upload/snapshot compatibility.
Running opencode in serve mode across 10+ repos daily. We kept hitting the same UX gaps and reliability bugs. At some point we stopped filing issues and started shipping patches.
A deep dive into fixing opencode for production use as a long-running coding agent: MCP memory leaks, tool deadlocks, session recovery, and why Vibe Browser's extension architecture avoids the chrome-devtools-mcp memory trap entirely.
Recent work in our team's custom Codex fork made the local coding stack more flexible with first-class GitHub Copilot login, safer Ollama model discovery, and an experimental reflection loop that can retry incomplete work.
AI coding agents routinely stop before their work is done. Reflection is a plugin that injects structured self-assessment and verification loops after every agent turn, transforming unreliable sessions into bounded, verifiable workflows.
How Vibe tests browser agents in practice: OCR-backed extractor validation, deterministic mock LLM workflows, and real-model integration tests against live sites.