Pick by the question that matches your situation. The answer column is the framework; the why column is the reason — read both before committing.
"I need it on Slack + Discord + WhatsApp"
→ OpenClaw
50+ messaging integrations are first-class. ClawHub has community channel adapters for almost everything. Hermes is single-agent focused.
"I want it to remember what we did last week"
→ Hermes Agent
FTS5-over-SQLite session search is the headline feature. OpenClaw expects you to bring your own persistence; Hermes ships with deep memory built in.
"I'm running it inside a regulated environment"
→ Hermes Agent
Container hardening, read-only roots, and pre-execution scanning matter most in regulated environments. Verify current advisories, registry trust, and sandbox configuration before production use.
"I want raw coding speed, like Claude Code but open"
→ Claw Code
Rust runtime under a Python orchestration layer. Built specifically as a clean-room rewrite of the Claude Code harness — same shape, fully transparent.
"I'm fine-tuning small models for tool use"
→ Hermes Agent
Atropos RL integration generates thousands of parallel tool-calling trajectories — research-grade pipeline you'd otherwise build from scratch.
"I want the largest ecosystem and community"
→ OpenClaw
15× the GitHub stars of Hermes (~345k vs ~22k). More plugins, more skill authors, more Stack Overflow answers when you hit a wall.
"I just want to wrap my Claude Code subscription"
→ Enderfga/openclaw-claude-code or 13rac1's plugin
Both are thin OpenClaw plugins specifically for Claude Code — the first adds multi-engine routing and a council workflow; the second sandboxes Claude Code in Podman/Docker.
"I want to migrate from OpenClaw to Hermes"
→ Use the official migration tool
A dedicated converter exists for moving OpenClaw configs (agents, skills, bindings) into Hermes profile format. Don't rewrite by hand.
"I want a terminal-native AI pair programmer"
→ Aider
Git-native edits, auto-commits each change with a descriptive message. No IDE lock-in. Most popular terminal pair-programming tool.
"I want VS Code with an autonomous agent inside"
→ Cline (cautious) or Roo Code (multi-mode)
Cline gates every step with human approval — safer for new users. Roo Code adds Architect/Code/Debug personas for switching mindset mid-session.
"I want a Cursor-like editor but fully open source"
→ Void or PearAI
Both are open VS Code forks with batteries included. Void leans pure-OSS BYO-model; PearAI ships more pre-configured.
"I want Devin's autonomous loop but open"
→ OpenHands
~71k stars, by far the largest OSS Devin-style platform. Sandboxed execution, browses the web, runs shells. SDK + CLI + GUI all included.
"I want to auto-fix GitHub issues"
→ SWE-agent
Princeton's reference for SWE-bench. Specifically built around the issue-to-patch loop with a research-grade Agent-Computer Interface.
"I want to chain LLMs + tools + retrieval generally"
→ LangChain (broad) or LangGraph (control)
LangChain is the default toolbox — biggest integration surface. LangGraph trades convenience for explicit graph control and durable execution.
"I want type-safe agents with structured outputs"
→ Pydantic AI
FastAPI ergonomics for agents. Pydantic-validated I/O end-to-end, dependency injection, model-agnostic. Production-grade typing.
"I want role-based teams of agents"
→ CrewAI or Agency Swarm
CrewAI is independent of LangChain with role/goal/process abstractions popular for business workflows. Agency Swarm sits on the OpenAI Agents SDK if you're committed to that stack.
"I want agents whose memory persists for years"
→ Letta (formerly MemGPT)
Memory is the product. Agents are addressable services with durable state and self-editing context, not ephemeral chains.
"I want agents that read documents (RAG-heavy)"
→ LlamaIndex
Strongest story for OCR / document-heavy RAG. Workflows API gives event-driven orchestration over indexed data.
"I want agents that write Python code instead of JSON"
→ smolagents (HuggingFace)
Code-action model: agents emit Python instead of JSON tool calls. Tiny core (~1k LOC), Hub-native tool sharing.
"I want to stop hand-tuning prompts"
→ DSPy (Stanford)
Compiler approach: write modules, run optimizers (MIPRO, BootstrapFewShot), let the framework auto-tune prompts and weights.
"I need an agent for customer-facing chat with guardrails"
→ Parlant
Behavioral "guidelines" as first-class objects, not prompt magic. Built specifically for regulated/customer-support deployments.
"I want to drive a browser with AI"
→ browser-use or Stagehand
browser-use (Python, vision+DOM hybrid) is the fastest-growing repo. Stagehand (TypeScript, Playwright-augmented) has deterministic fallback for production.
"I need self-healing browser workflows (auth, 2FA, CAPTCHAs)"
→ Skyvern
YC-backed, vision-first, specifically engineered to handle the messy stuff that breaks naive Playwright scripts.
"I want an AI agent with its own sandboxed desktop"
→ Bytebot
Full virtual Linux desktop in Docker. The agent has its own OS, files, browser — none of yours. Best for untrusted task execution.
"I need to control Windows VMs with an agent"
→ Pig.dev
Most browser-use frameworks target Linux/web. Pig.dev is the rare Windows-first option for legacy enterprise apps.
"I want the official OpenAI primitives"
→ OpenAI Agents SDK
Production successor to Swarm. Handoffs, guardrails, tracing — the base layer many other libs now extend.
"I want AWS-backed multi-agent in Python"
→ Strands Agents
AWS open-sourced what they use internally for Bedrock services. v1.0 added A2A protocol; ~14M downloads by early 2026.