agent▌

Fast, persistent browser automation with session continuity across sequential agent commands. \n \n Supports three browser modes: headless Chromium, real Chrome with profile support, and cloud-hosted remote browsers with proxy configuration \n Includes 15+ command categories covering navigation, page inspection, interactions, data extraction, cookie management, and JavaScript execution \n Offers cloud session management, local server tunneling via Cloudflare, and parallel subagent execution thro

Multi-platform web search and content reading across 16+ social and web sources. \n \n Supports 16 platforms including Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu, Douyin, Weibo, WeChat articles, LinkedIn, Instagram, V2EX, RSS, and general web search via Exa \n Zero configuration required for 8 channels; others need cookies or API keys (Groq for podcast transcription, Exa for web search) \n Provides command-line tools and Python APIs for searching, reading threads, extracting trans

Terminal-based RSS/Atom feed reader with discovery, search, and OPML import/export. \n \n Discover feeds from any website, subscribe to feeds with optional timeout configuration, and read articles from single or multiple feeds with caching and parallel fetching \n Search across all subscribed feeds locally or discover new feeds via web search (agent-built-in or Exa API) with auto-subscribe and read options \n Clean up broken and duplicate feeds, import/export subscriptions via OPML, and manage f

Create new agent skills with proper structure, progressive disclosure, and bundled resources.

Multi-agent architectures distribute work across multiple language model instances, each with its own context window. When designed well, this distribution enables capabilities beyond single-agent limits. When designed poorly, it introduces coordination overhead that negates benefits. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division.

Trust system reminders as agent progress notifications. Don't poll.

When the user asks to implement something, use implementation agents to preserve main context.

Multi-agent architectures distribute work across multiple agent invocations, each with its own focused context. When designed well, this distribution enables capabilities beyond single-agent limits. When designed poorly, it introduces coordination overhead that negates benefits. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division.

Playwright-based browser automation with element refs and session persistence for AI agents. \n \n Provides 6 core functions: open (navigate + configure), snapshot (refresh element refs), interact (click/fill/drag/upload/scroll), screenshot, execute (JavaScript), and close \n Uses @e ref system for element targeting; refs invalidate after navigation and require re-snapshot to refresh \n Supports video recording with optional cursor indicator, proxy routing, file uploads, and drag-and-drop intera

When working on the Agents workbench layout, always follow these guidelines: