When to Stay in the Browser

What You'll Need

⏱ Time: 10 minutes  |  📋 Tasks:

• Your chatbot of choice (ChatGPT, Claude, Gemini) open in a tab
• Your agent harness installed and configured from Lesson 4
• A few real tasks you're considering delegating

Agents Are a Tool, Not a Lifestyle

After five lessons of learning what agents are and how to use them, it's tempting to think you should use an agent for everything. You shouldn't.

Agents add overhead. They cost money per call. They need configuration. They can make mistakes that are harder to catch than a single chatbot response. The best agent users are the ones who know when not to use one.

The Autonomy Continuum

Think of autonomy as a spectrum, not a binary. Every task falls somewhere on this line:

Your job is to match the task to the right autonomy level. Using Level 4 for a Level 1 task wastes money and complexity. Using Level 1 for a Level 4 task wastes your time.

When Chat Is Better

Stay in the browser when:

• The task is a question, not an action. "Explain this concept," "Summarize this article," "What's the difference between X and Y?" — a chatbot handles these perfectly.
• The output is text you'll use elsewhere. Drafting an email, outlining a document, brainstorming ideas. You're going to copy the result into another tool anyway.
• You need creative exploration. Agents are goal-oriented. Chatbots are open-ended. If you don't know what you want yet, a conversation is better than a task.
• The cost doesn't justify the complexity. A 30-second chatbot query costs fractions of a cent. Setting up an agent session for the same question adds minutes and pennies for no benefit.
• You're learning. When you're still figuring out the domain, a back-and-forth conversation teaches you faster than delegating to an agent.

When an Agent Is Worth It

Reach for an agent when:

• The task involves files. Reading, writing, renaming, searching through multiple files. An agent can do in seconds what takes you minutes of clicking and scrolling.
• The task requires iteration. "Try this, check the result, fix that, try again." An agent can loop through 10 attempts while you grab coffee.
• The task spans multiple steps. Research a topic, compile findings into a document, format it, save it to a specific folder. Each step is simple; chaining them is where the agent shines.
• The task runs on a schedule. Weekly reports, daily data checks, monitoring dashboards. Set the agent once, let it run. (This is heading into autonomous territory, covered in the Agents Working for You track.)
• The task needs tool access. If the work requires running code, querying a database, or calling an API, you need an agent — a chatbot can't do these.

The Two-Question Test

Before every task, ask yourself two questions:

You'll develop a feel for this over time. When you're starting out, the rule of thumb is: if you can do it in the chat window in under 2 minutes, don't open the agent.

Walkthrough: Three Decisions

Task 1: "Write a thank-you email to a client"

Decision: Chatbot. This is a text-generation task. You'll copy the result into your email client anyway. An agent adds nothing.

Task 2: "Read my last 20 invoices and find any that are unpaid"

Decision: Agent. The chatbot can suggest how to do it, but only an agent can open the invoice files, extract amounts, cross-reference with payment records, and compile the list.

Task 3: "Research competitors and write a market analysis"

Decision: Start in a chatbot to explore and figure out what you need. Then use an agent to do the systematic research and compile the document. The chatbot handles the creative scoping; the agent handles the execution.

Your Takeaway — The One-Sentence Rule

Chatbots for generating ideas. Agents for executing them. Keep that in your head and you'll make the right call 90% of the time.