What Claude can't do, and what that means for your workflow
The limits of a basic conversation, named clearly
After this, you'll be able to name the three things a basic Claude conversation cannot do on its own, recognize when you are about to ask for one of them, and know which feature would lift the limit.
Before you start
Complete Formatting Claude's output: tables, lists, code, and prose first; this lesson builds on shaping what Claude produces by drawing the line around which requests a basic chat structurally cannot fulfill at all, no matter how you format them.
The idea
A basic chat cannot see your private files, act inside your other apps, or run the code it writes, all on its own. It reasons over what it learned in training plus whatever you paste in. It can also search the web when you switch on web search, which is free on every plan, so getting current information is not the boundary.
These limits are not bugs, and each lifts later in this track. Your private files arrive through connectors when your account and that connector support them; some connectors are free, while others have plan, tenant, or organization requirements. Acting inside software is Computer Use, which currently needs a supported paid plan. One aside that saves real confusion: "Claude Code" is a separate developer product, not a setting that makes a normal chat better, so ignore the name for now.
Here is the before and after: Without knowing the limits, you ask "read the invoice in my inbox" or "rename these files on my Mac," get an apology, and feel let down. Knowing them, you recognize both need access you have not granted yet, so you paste the detail in yourself or set up the right Connector when you reach that module.
Now try it ask Claude "what can't you do in this basic conversation without extra setup?" and read its honest list before you assume it can reach something private.
A basic chat reasons over what you give it and can search the web; seeing your private files and acting in other apps are features you add on purpose.
Try it (9 min)
Watch out for
- Assuming Claude cannot get current information, when web search is a free built-in toggle made for exactly that
- Assuming Claude can already see your email or files before you have connected anything
- Thinking 'Claude Code' is a mode that makes normal chats better, when it is a separate developer product
- Believing the limits are permanent, when free directory Connectors and (paid) Computer Use lift them in later modules
Paste this into Claude
Ask Claude this exactly: "I'm new to you. In a plain conversation like this one, with no extra features set up, tell me honestly: can you read the files on my computer, send an email for me, or run a script and show me the result? For each one, say yes or no, and if it's no, tell me in one line what feature I would need. Also: can you search the web for current information, and does that cost extra?" Read its answer, then tell me which one surprised you most.
What good looks like
- Claude answers no to reading your private files, sending email, and running its own code in a basic chat
- Claude confirms it can search the web for current information, and that web search is free
- For each limit, Claude names the feature (such as a Connector) that would lift it
- You can restate the three core limits in your own words
- You can give one example of a request you should NOT make in a plain chat
When this breaks
- Breaks when you ask a basic chat to open your private files or accounts, because a plain conversation only sees its training, what you paste in, and the public web through search, not your private data.
- Breaks when you confuse the product name 'Claude Code' with a quality setting, because it is a separate tool for developers, not a switch that improves an ordinary conversation.
AI can help with this
When you are unsure if a basic chat can do something, just ask: 'Can you do [the thing] in a plain conversation with no extra setup, and if not, what feature would I need?' Claude will tell you where the boundary is.
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that claude answers no to reading your private files, sending email, and running its own code in a basic chat.
- You can verify that claude confirms it can search the web for current information, and that web search is free.
- You can verify that for each limit, Claude names the feature (such as a Connector) that would lift it.
- You can restate the three core limits in your own words.
Key takeaways
A basic chat cannot see your private files, act in other apps, or run its own code on its own, though it can search the web for free. Those are boundaries, not bugs, and each lifts later: directory Connectors are free, Computer Use is paid.
- Remember the three limits of a basic chat: it cannot see your private files, run its own code, or act in outside apps on its own.
- Web search is free and built in, so a basic chat can pull current information without any setup.
- Paste in personal or private information yourself until you set up the Connector that would fetch it.
- Ignore the name 'Claude Code' for now, since it is a separate developer product, not a chat setting.
- Treat the limits as removable: directory Connectors (free for everyone) and Computer Use (paid) lift them in later modules.
Go deeper