Cowork or Code: which More AI workspace should you use?

New More AI conversations use Cowork for questions, research and files; Code remains a separate workspace for repositories. Here is the current model, including what happens to legacy Chat conversations.

The More AI team · Updated September 14, 2026

The current model: Cowork plus Code

More AI now has one default place for conversations: Cowork. A new conversation gets a workspace from the start, whether you ask a quick question or attach a folder and ask for a finished deliverable. Code stays separate because a software repository needs git-aware tools, commands, tests and a different permission boundary.

This is a simpler choice than the old Chat/Cowork/Code split: choose Cowork for knowledge work and Code for a codebase. Both can use the providers and models you configure, but each exposes tools suited to its job.

Cowork and Code workspaces in the More AI desktop app

Cowork — the default for every new conversation

Use Cowork to ask a question, think through an idea, research a topic or work with files. You do not have to attach a folder: a lightweight question and a multi-file project begin in the same place, and the workspace can grow only when the task needs it.

When files are involved, Cowork can inspect the workspace, propose steps and produce real deliverables. Keep each ongoing body of work in its own project when it needs persistent instructions and context; use a project-less Cowork conversation for a one-off task.

A Cowork workspace editing a document with a visible diff

What happened to plain Chat?

Plain Chat is a legacy conversation type, not a deleted archive. Existing chats remain readable and can continue through their original runtime, so old links and history still work.

New conversations receive a Cowork workspace instead. That avoids a dead end where a quick question later needs a file: you can add context without moving the conversation into another mode first.

Code — build in your repository

Code is a planning coding agent for your repositories. It explores the codebase, proposes a plan, makes the changes across files, runs your commands and tests, and shows every edit as a diff — with real git branches, a built-in terminal and a browser to preview the result.

A permission ladder decides how much it may do on its own, while gated commands can pause for approval. Choose Code when the desired result is a reviewed change to a codebase, not merely an explanation of code pasted into a conversation.

Code mode showing a plan, file diffs and a test run

A practical decision rule

Choose by the object being changed. If the output is an answer, report, spreadsheet, presentation, research note or a set of ordinary files, start in Cowork. If the output is a commit-sized change to a repository and should be checked with commands or tests, start in Code.

If a Cowork discussion reveals a software task, open a Code workspace for the repository and carry over the goal and relevant context. Keeping the execution boundaries explicit makes permissions and review easier to understand.

  • Question, draft or research task → Cowork
  • Documents, spreadsheets, slides or a general folder → Cowork
  • Repository changes, commands, tests and git history → Code
  • Old plain conversation → keep reading or continuing it as a legacy Chat

Local work and cloud continuity

Choose the output first: everyday research and documents belong in the main workspace; repository changes belong in Code. Then choose execution: a local computer, an available cloud workspace, or a separately paired computer.

Cloud tasks and routines can continue when the laptop is closed. A task remotely running on your computer still needs that computer online. An account is required for cloud and cross-device access; available cloud features are temporarily free during beta, while your provider charges for usage on your own key.

Frequently asked questions

Is Chat still a mode for new conversations?

No. New conversations now receive a Cowork workspace. Existing plain Chat conversations remain readable and can continue through their legacy runtime.

When should I use Code instead of Cowork?

Use Code when the result should be a change to a repository and the agent needs branches, commands, tests or diffs. Use Cowork for questions, research, documents and general file-based work.

Do I need a folder to start Cowork?

No. A quick question can begin in a project-less Cowork workspace. Attach files or use a project when the task needs persistent context or a deliverable.

Can Cowork change source code?

Cowork can work with ordinary files, but Code is the intended workspace for repository changes because it adds git-aware review, commands, tests and a dedicated permission boundary.

Which workspace can continue in the cloud?

Cloud Cowork tasks and routines are available in beta. Synced, paired and cloud Code paths are also under active beta development, so availability can vary by account and environment.

All guides