Trigger: they're doing real work — files, code, emails, documents, data — and the chat window is the bottleneck. They're copying things in and out, or describing what's on their screen instead of showing it. Or they've outgrown basic chat and don't know what's next.
Establish context
Ask: what does your typical session look like? Are you mostly in a chat window, or are you working with files and tools alongside it?
If they're entirely in a chat app, ask: what do you end up doing after the AI gives you an answer? If the answer is "I copy it into [somewhere else]" — that's the signal.
What changes
The chat window — the thing most people think of as "AI" — is one way to interact with a model. There are others, and they're designed for different kinds of work.
The chat app (ChatGPT app, Claude.ai, Gemini): best for thinking, asking questions, having a conversation, drafting text. The model lives in a browser tab or phone app. You type, it replies. Good for: exploring ideas, getting perspective, writing drafts, quick questions. Limited for: anything involving files on your computer, anything that needs to run code, anything that touches multiple systems.
Desktop and computer-use tools (ChatGPT desktop, Claude desktop): the chat but with access to what's on your screen or in your files. Can see documents, read spreadsheets, sometimes interact with other apps. The step between chat-only and real tool use.
Code-level AI (Claude Code, Codex, Cursor, GitHub Copilot): the AI runs in a terminal or editor. It can read and write files, run commands, interact with databases, call APIs, build things. This is where AI stops being a conversation partner and becomes a worker. Not just for programmers — anyone whose work involves structured data, documents, or systems eventually needs this level.
When to move beyond chat:
- They're copy-pasting between the AI and another tool more than twice per session
- They want the AI to actually do something rather than tell them how
- They're working with files, spreadsheets, codebases, or systems
- A skill they've built in chat would be better as something that runs automatically
The honest gap: code-level tools require some technical comfort. Not programming ability — but comfort with a terminal, with files and folders, with instructions that look like code even when they're just text. That's a learnable thing, and the AI itself can help bridge it, but it's real and pretending it's not is how people bounce off.
What to do:
- If they're in a chat app and it's working: stay there. Don't move for the sake of moving.
- If they're hitting the limits above: try the desktop version of whatever they're using, which usually adds file access.
- If they're ready for more: Claude Code is a terminal application where the AI reads files, writes files, runs things, and builds things — it's the full version of what the chat app previews. It requires a subscription and comfort with a command line.
The principle: the chat window is training wheels that happen to also be a real tool. When the work outgrows it, there's a next level — but only move when the current surface is the thing holding them back, not before.