Insights
Tactical playbooks and market analysis for teams using AI browser automation.
Newsletter
Get updates on browser automation
Filter by tag
Clear filterEvery agent at Vibe Technologies has its own Slack app, bound to a dedicated OpenClaw channel. When one Slack bot @mentions another, OpenClaw routes the message to the target agent's session. AGENTS.md in each workspace is the plain-text contract that tells each agent when to pass work and to whom.
The customer-support pipeline at Vibe Technologies: every escalation from Gmail, Chatwoot, the docs chat, and the VibeBrowser co-pilot becomes a tracked Linear issue owned by Jared Dunn (SupportEngineer), with status flowing back to the customer when Gilfoyle Bertram closes the PR.
Running OpenCode in server mode on a VM and exposing it via Tailscale turns it from a one-person CLI tool into a persistent coding service. The software-engineer agent on OpenClaw can then open sessions, supervise progress, and follow up — acting more like a staff engineer than a solo coder.
How Vibe Technologies evaluates its ten AI agents at two levels: a YAML-based deployment verification suite that runs per-PR, and a Langfuse-backed team evaluation loop where Claw reviews cross-agent traces, checks for stuck sessions, and pushes agents to complete their tasks.
A complete roster of the ten AI agents running on OpenClaw at Vibe Technologies — their names, roles, primary model, and how they divide responsibility for customer support, engineering, product, growth, legal, finance, and operations.
Why Vibe Technologies moved its OpenClaw operations agents off GPT-5.4 high reasoning and onto DeepSeek-V4-Flash with max reasoning — and what the speed and agent behavior delta looks like under real incident load.
Six months after founding, here's the current operational state — agent roster, system diagram, process matrix, model routing — and what changed from the Nov 2025 plan.
We're excited to announce our partnership with Kate to build a new product that helps product companies onboard OpenClaw AI agents.
How Vibe Technologies deploys self-hosted Chatwoot integrated with an AI chatbot for openclaw.vibebrowser.app — the deploy script, the architecture, how the AI bot handles tier-1 chat, and how unresolved conversations escalate to our SupportEngineer agent (Jared Dunn).
How we built a RAG support chat for docs.vibebrowser.app on Azure AI Foundry — markdown knowledge base ingestion, Azure AI Search, GPT-4 grounded responses, and an escalation path that hands unresolved questions to our SupportEngineer agent (Jared Dunn, DeepSeek-V4-Flash) for email follow-up via Gmail.
A practical, engineer-written playbook for running OpenClawBot team profiles across SupportEngineer, GrowthManager, SoftwareEngineer, DevOpsEngineer, MarketingManager, and FinManager.
Quick-start commands for giving OpenClaw browser access with vibebrowser-cli for local signed-in workflows or @vibebrowser/chrome-devtools-mcp for cloud and multi-agent sessions.
A technical look at how OpenClaw manages browsers through its browser CLI and browser tool as of March 25, 2026, plus why VibeBrowser Co-Pilot remains a stronger local-browser control plane for agents.
Telegram proved people want a personal AI assistant they can reach from their phone. Now we're building the real product surface.
VibeBrowser now remembers what you tell it — across sessions, across tasks. Inspired by OpenClaw's dual memory architecture, we built persistent agent memory that works inside a browser extension.
Why Vibe Technologies retired its custom OpenHands-based VibeTeam build and moved operations to vibebrowser.app/agentic-team — OpenClaw-based agents with native Slack integration that proved more productive in real incident response.