Comparison
Agent vs SWE-bench
Agent and SWE-bench are both common AI/LLM terms but cover different ideas. Here is a quick side-by-side.
When you would reach for Agent
Agent comes up when the question is fundamentally about agents & tools.
Claude Code — coding agent that edits files, runs commands, runs tests.
When you would reach for SWE-bench
SWE-bench comes up when the question is fundamentally about evaluation.
A SWE-agent run patching a Django bug, verified by Django's own test suite.
Frequently asked
What is the difference between Agent and SWE-bench?
Agent: An AI agent is an LLM-driven system that decides which actions to take, executes them via tools, observes the results, and iterates until a goal is met. SWE-bench: SWE-bench is a benchmark of ~2.3K real GitHub issues from popular Python repos. The model must read the codebase, understand the bug, and write a patch that passes the existing tests.
When should I use Agent vs SWE-bench?
Agent is the right concept when you are focused on agents & tools. SWE-bench applies when you are focused on evaluation.
Are Agent and SWE-bench the same thing?
No. Agent is agents & tools; SWE-bench is evaluation. They are related but address different parts of the AI stack.