Claude is the same underlying model in all three modes. What changes is what it can do, who it is for, and how much of your usage allowance it consumes. Chat is a conversation, Cowork is a delegation, and Code is a development environment.
| Chat | Cowork | Code | |
|---|---|---|---|
| Where | Web, mobile, or desktop | Desktop app only | Terminal / VS Code |
| Who | Everyone | Non-technical knowledge workers | Developers only |
| What it does | Responds to you | Executes tasks for you | Builds software for you |
| File access | Upload only | Read, edit, create in a designated folder | Full codebase access |
| Autonomy | None | High — completes multi-step tasks | High — full dev workflows |
| Token usage | Low to moderate | High | Very high |
| Setup | None | Minimal (designate a folder) | Technical (install, configure) |
| Available on | All plans | Pro and Max | Pro and Max |
Tokens are the unit Claude uses to read and write. Every word you send, every file Claude reads, and every response it generates all use tokens. Each plan has a usage limit — understanding which mode uses more helps your team stay efficient and avoid hitting limits mid-task.
Chat is low to moderate. Normal conversations are very manageable. Uploading large documents increases usage but stays reasonable for daily work.
Cowork is significantly higher. Because Cowork reads files, plans a sequence of actions, executes each one, and checks its work, a single session can use several times more tokens than an equivalent Chat conversation. Use it intentionally.
Code is very high. Claude Code reads entire codebases upfront for context. Not relevant for most FOA knowledge work.
The practical rule: Use Chat as your default. Move to Cowork only when you have a multi-step task that involves real files and would take meaningful time to do manually.
Best when: You need to think something through, get a draft, ask a question, analyse content, or do back-and-forth work where you are steering the direction.
Chat is the mode your team will use most often. You type a message, Claude responds. You can upload files and ask Claude to work with them, but Claude does not take action on your systems — it advises, drafts, and analyses. You carry out the steps yourself. You can change direction at any point, ask follow-ups, and refine outputs in real time.
Use Chat for
Do not use Chat for
Best when: You have a concrete task involving real files or connected apps that would take you meaningful time to do manually, and you can hand it off with clear instructions.
Cowork lives inside the Claude desktop app. You designate a folder Claude is allowed to work in and give it a task in plain language. Claude reads files, creates documents, edits content, and connects to services like Outlook and Slack — without you managing each step. You come back to a finished output.
Use Cowork for
Do not use Cowork for
Best when: You are a developer working inside a software codebase.
Claude Code is a command-line tool installed locally. It reads your entire codebase for context, then writes code, runs tests, fixes bugs, and manages Git workflows. It is built for technical users building or maintaining software.
This is not a tool most of the FOA team will need for day-to-day knowledge work. It becomes relevant if FOA builds API integrations, automations, or technical infrastructure.
Use Code for
Not for
Still unsure? Default to Chat. It handles more than most people expect, and it is the most efficient use of your usage allowance.
The quality of Claude's output is directly related to the quality of your instructions. A few habits that apply across all three modes:
Get started today before this once in a lifetime opportunity expires.
