Same model, four jobs: why Claude answers differently in chat, Cowork, Code and Slack

Put the same question to Claude in the chat window and in Claude Code, same day, same model. Chat gives you four paragraphs with headings. Claude Code gives you two lines and a list of files it changed. Most people conclude one of them is smarter.

Neither is. It’s the same model both times. What’s different is the app, and which app each team uses for which job is a decision someone has to make and write down.

What the app changes

The model is what you pay for by the seat, and it’s the same in every Claude app. Each app changes three things before you type a word:

• What it’s told. Every app gives Claude standing instructions you never see. Chat’s are written for conversation. Claude Code’s tell it to keep replies short and get on with the change.
• What it can see. Your typing, a folder on your computer, a codebase or a Slack channel, depending on the app.
• What it can do. Chat hands its work back to you. Cowork and Claude Code open files, change them and save them.

Change those three and you change the answer, with the same model and the same question.

I first met this idea in an AI-written comparison of Claude’s apps. It got the idea right, some product details wrong, and called the whole thing “the harness”, which is an engineer’s word. The first version of this lesson kept the word. A colleague read it and asked what point I was making, which was fair. So here it is without the jargon, in the version I would put in front of a leadership team.

App	What it works from	What it is for
Claude chat	What you type, paste or attach, plus any connected systems	Thinking, drafting, working a problem through
Claude Cowork	Files and folders on your own computer, through the Claude desktop app	Document work across many files, without touching code
Claude Code	A codebase and the written rules in it, from the terminal	Building and fixing software, for builders only
Claude Tag	The Slack channel it has been added to, whenever someone tags @Claude	Summarising a discussion, quick answers where the team already is

Ask chat to edit fifteen files on your laptop and it will explain how, at length, and edit none of them. Ask Claude Code for a marketing strategy and you’ll get a terse one. Neither is a failure of the model. Both are the wrong app for the job.

Why this is a leadership decision

Buying seats gets the board’s attention. Deciding which app each team uses rarely does, and it shapes the work just as much. A team given chat alone gets thoughtful answers and copies them out by hand. A team given Slack alone gets short ones, in public. Hand a builder chat and they paste code back and forth all day. Hand a consultant Claude Code and they never open it.

So the question is not which model. It is which app, for whom, for what, and who wrote that down.

The number: five tools, one page

At our firm the tools arrived faster than the guidance on when to use which. Chat, Slackbot, Claude Tag and Claude Code landed close together, the training covered each on its own, and nobody had answered the routing question. The feedback from our sales leadership meeting was blunt: it was causing real confusion.

So on 26 July we posted one wiki page, “What to do where”. Five tools, one rule each:

• Claude chat for real work tied to an account, engagement or deliverable.
• Slackbot, Slack’s own AI assistant, for quick, personal jobs grounded in Slack.
• Claude Tag as the shared team Claude, switched on channel by channel.
• Claude Code for builders only.
• Cowork not in the rollout. Our work lives in the cloud, not in local files.

That fifth line is the one I’d defend hardest. A routing page that only says yes isn’t a routing page. The generic advice puts business operations on Cowork. For a firm whose documents never touch a local disk, the honest answer was no, and writing it down saved more questions than the other four lines together.

One thing to try this week

Write your own version of that page. One line per tool: what it works from, what it’s for, who it’s for. If a tool is switched on and you can’t write its line, that is the confusion your team is living with. If you’ve decided against a tool, say so on the page. Then keep it beside your one-page rules, because it belongs there.

And before you switch on the next tool, read what happened when we took the tool to where people work. Same lesson, from the other side.