Insights
Tactical playbooks and market analysis for teams using AI browser automation.
Newsletter
Get updates on browser automation
Filter by tag
Clear filterClaude Code is excellent. I still chose OpenCode for the coding agent at Vibe Technologies. Here are the five reasons — open-source forkability, subagent observability, remote control via opencode serve, model flexibility, and where Claude Code still wins.
Every 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.
OpenCode's web UI isn't mobile-friendly. Here's how Claude Code remote control over Tailscale became the interim solution for managing AI coding sessions from a phone.
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.
Practical token-optimization stack at Vibe Technologies for OpenCode coding agents — LST for log compression, RTK (Rust Token Killer) as a CLI proxy, Caveman mode for terse output, and orchestrator + subagent role split that keeps expensive models doing only expensive work.
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.
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.
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.
How Vibe Technologies uses a custom OpenHands build (VibeTeam) to handle incident response, Slack communication, customer triage, and operations — without a human operations team.
How Vibe Technologies structures its AI coding stack: starting with Claude Code, switching to OpenCode for multi-model flexibility, setting up orchestrator and subagent roles, and running parallel agents 24/7.
How I founded Vibe Technologies as a solo founder with AI agents handling engineering, QA, DevOps, and operations — and what 'AI-native' actually means in a real production company.