Lesson 1050 of 1570
Tasks Where a Plain ChatGPT Beats an Agent Like Claude Code
For one-off questions, a regular chatbot is faster, cheaper, and less risky than firing up an agent.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1The big idea
- 2right tool
- 3agent overuse
- 4efficiency
Concept cluster
Terms to connect while reading
Section 1
The big idea
Agents are exciting and you'll want to use them for everything. Don't. For 'what does this regex mean?' a regular ChatGPT or Claude reply is better — instant, cheap, no permissions. Agents are for multi-step work where you'd otherwise be alt-tabbing for 20 minutes. If a chat answer would do, use chat.
Some examples
- Question: 'Explain this stack trace' — use chat, not Claude Code (no files need editing).
- Question: 'What's a good name for this variable?' — use chat (no tool calls needed).
- Task: 'Refactor my whole module to use hooks' — use Claude Code (multi-file, needs to run tests).
- Task: 'Find every place we hard-coded the API URL' — use an agent (needs to search files).
Try it!
Make a list of three things you did with an agent last week. Honestly, would chat have been faster for any of them?
Key terms in this lesson
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Tasks Where a Plain ChatGPT Beats an Agent Like Claude Code”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Builders · 30 min
The Four Ingredients: Goal, Tools, Loop, Stop
Every agent — fancy or simple, local or cloud — boils down to four parts. Learn the recipe and you can read any agent system like a menu.
Builders · 32 min
Your First Agent: A Walkthrough of What It Does
Follow a real agent run step by step — from prompt to result — and see exactly what happens inside. No code yet, just the anatomy of a successful task.
Builders · 32 min
Tools an Agent Might Have: Filesystem, Browser, Code
Agents are only as useful as their tools. Tour the big three — filesystem, browser, code execution — plus the emerging MCP ecosystem, with examples of what each unlocks.