Claude vs ChatGPT for work: the difference a non-coder feels

I would not choose a winner for your work from a product name alone. A chat and a project folder ask the AI to work in different places. The useful first question is smaller: do you need an answer from a file you supply, or do you need help inside a folder where several files and a draft belong together?

ChatGPT and Claude both document a way to attach supported files to a chat. That is a clear route when you want a report explained, a spreadsheet checked, or a document searched for an answer. The file enters the chat you chose. You still open the source page, row, or figure before you rely on the answer.

Some work starts with a folder instead. A price list, job notes, and a draft may need to stay together while the tool reads them and writes a new file. Claude Code and Codex are documented tools that work in a terminal, a text window also called the command line where you type instructions for the computer to run. Their controls matter because a tool that can read or change files needs a boundary you can inspect before it begins.

The pages and dated local folder example below describe routes, controls, and review steps. Your job, file permission, and approval step determine whether a route fits.

Codex has a similar documented project route in a terminal. Its documentation says it can inspect files, modify files, run commands, and show permission boundaries. I include it in the dated local-folder example below. The job, file permission, and approval step determine whether a surface fits.

On 22 September 2026, I ran Claude Code CLI and Codex CLI on the same local folder. The folder contained 11 fictional plumbing-and-heating job notes, a price list, an hours sheet, and one instruction. Each tool had to create an invoice-run.md file, identify missing price information, and flag issues.

Claude Code priced 6 jobs, put 5 jobs under ASK ME, and recorded 6 further concerns. Codex priced 9 jobs, put 2 jobs under ASK ME, and recorded 3 confirmation items. Both saved outputs identified missing price policy or incomplete job information. Both wrote their result inside their own local workspace.

The important disagreement was plain enough for a manager to see. The files did not say whether a fixed-price job outside normal hours also carried an hourly charge. Claude Code left more jobs for a decision. Codex applied one reading to more jobs and still marked items for confirmation. Neither saved file settles the policy. A person who knows the business has to settle it before an invoice reaches a customer.

The two runs used different tools and different configurations. Their totals do not rank the tools for speed, quality, cost, or office work. Keep a saved output and a review list before you trust an answer on screen.

If you have a single approved report or spreadsheet and need an answer from it, start with the documented chat-upload route you already have access to. Keep the source open while you read the answer.

If you have an approved folder that contains several related files and needs a draft saved beside them, look at a documented project or connected-folder route. Claude Code, Codex, and Cowork each document a route for that kind of work. Read the permissions or connected-folder boundary before you begin.

If the result could change a customer message, a price, a contract, or a staff record, do not start by asking which brand wins. Start by deciding what a correct answer looks like, which blank requires a person, and who can approve the final result.

You do not need to upload a file to any external product to understand this comparison. The choice above tells you whether an approved trial would involve a chat attachment or a chosen folder. Only use either route when the file, destination, and permission all make sense for your work.

Do not buy a course, subscription, or consultant's promise because somebody says Claude or ChatGPT will handle all of your office work. Ask them to name the work surface, the files it can touch, the approval step, and the evidence they kept from a comparable job. A real answer can still be "I do not know until I see an approved sample."

That answer protects you from a polished demo that never has to meet the source files you use every day. It also gives a careful seller room to say where their tool helps and where a person must take over.