Chat
Use Chat for questions, conversation, brainstorming, quick analysis, search, file review, and tool-assisted work that remains centered in a conversation.
Use this reference to decide where a workflow belongs in ChatGPT: Projects, GPTs, Skills, memory, tools, apps, agent mode, or runtime prompts.
Use this reference to decide whether a workflow belongs in Project Instructions, project files, Project Sources, Custom GPT instructions, GPT Knowledge, Skills, Custom Instructions, Library, apps/actions, agent mode, or the runtime chat prompt.
Start by choosing the experience that matches the work. Then select the reasoning level, tools, persistent context, reusable workflow surface, and external integrations required by the task.
Use Chat for questions, conversation, brainstorming, quick analysis, search, file review, and tool-assisted work that remains centered in a conversation.
Use Work for longer, more involved tasks that require research, connected apps or files, active steering, approval points, and finished documents, spreadsheets, presentations, reports, or Sites.
Use Codex for software-development workflows involving repositories, code changes, tests, diffs, pull-request review, terminal work, and implementation tasks.
Use the API when the workflow must run inside a website, application, backend service, internal system, CI pipeline, or controlled production automation.
Chat and Work expose different control models. In standard Chat, choose the balance of response speed and reasoning effort. In Work and Codex, choose a GPT-5.6 model tier and reasoning effort, with Max and Ultra available according to the product, plan, workspace configuration, platform, and rollout state.
Standard Chat uses simplified controls rather than requiring the user to select every underlying model directly.
| Option | Use for | Current model behavior |
|---|---|---|
| Instant | Fast responses for everyday questions, short drafting, rewriting, summarization, and routine work. | Powered by GPT-5.5 Instant and remains the default fast-response option. |
| Medium | Standard reasoning for planning, structured comparison, analysis, and deliberate professional work. | Powered by GPT-5.6 Sol on eligible plans. |
| High | Extended reasoning for complex, multi-step tasks with several constraints or dependencies. | Powered by GPT-5.6 Sol on eligible plans. |
| Extra High | The highest standard-Chat reasoning effort for especially demanding tasks. | Powered by GPT-5.6 Sol where available. |
| Pro | Difficult tasks and longer-running workflows that require the highest-capability standard-Chat option. | Powered by GPT-5.6 Sol Pro where available. |
Work and Codex expose GPT-5.6 model tiers separately from reasoning effort. These controls are not the same as the simplified Instant-to-Pro picker used in standard Chat.
| Control | Type | Meaning | Availability boundary |
|---|---|---|---|
| Sol | Model tier | The flagship GPT-5.6 tier for the most capable reasoning and professional work. | Available in Work and Codex on eligible paid plans and managed workspaces. |
| Terra | Model tier | A balance of capability, speed, and cost for everyday agentic work. | Available in Work and Codex according to plan and supported surface. |
| Luna | Model tier | The fastest and lowest-cost GPT-5.6 tier. | Available in Work and Codex on eligible plans. |
| Reasoning effort | Per-model control | Controls how much reasoning time the selected GPT-5.6 tier receives. | The available effort levels depend on the selected tier, plan, product, and rollout. |
| Max | Reasoning effort | Gives GPT-5.6 the highest available single-agent reasoning effort for demanding work. | Available to users with GPT-5.6 access in Work and Codex and enabled through the relevant settings. |
| Ultra | Multi-agent mode | Goes beyond a single agent by using concurrent subagents and combining their work for complex, parallelizable tasks. | Available in ChatGPT Work for Pro and Enterprise users, and in Codex for Plus and higher plans. |
These surfaces support different forms of extended or delegated work. Use Work to produce longer research and finished materials, agent mode to perform controlled actions, and Scheduled Tasks to run work later, repeat it, or monitor for meaningful changes.
| Surface | Primary role | Use it when | Do not treat it as |
|---|---|---|---|
| ChatGPT Work | Longer research and creation of finished materials. | The task requires analysis, iteration, files, review criteria, active steering, or a completed document, spreadsheet, presentation, report, or Site. | A Project, a single tool, or a synonym for agent mode. |
| Agent mode | Delegated, multi-step online action. | The task requires website navigation, forms, uploaded files, connected data, spreadsheet editing, supported commands, or another external action. | A general writing mode or an unrestricted background worker. |
| Scheduled Tasks | Future, recurring, or monitoring work. | The task must run later, repeat on a schedule, or periodically check for a change and notify the user only when there is a meaningful update. | Agent mode itself, Project memory, or Codex automations. |
Work is the ChatGPT experience for longer research, analysis, and deliverable creation. It can be used in a standalone conversation or inside a Project when the task needs persistent files, instructions, and related conversations.
Agent mode is for complex online tasks that require ChatGPT to reason, research, and perform actions while the user retains control.
Scheduled Tasks let ChatGPT perform proactive work at a later time, repeat work on a schedule, or monitor for a meaningful change.
Use Projects for ongoing work with shared context. A Project is the correct ChatGPT surface when the work has persistent context, source material, repeated tasks, multiple chats, or a team/shared workflow.
| Project capability | Use for | Do not use for |
|---|---|---|
| Project Instructions | Stable project-scoped rules, role, output format, verification criteria, tone, and workflow boundaries. | Global user preferences, source documents, credentials, or one-off task input. |
| Project files / reference material | Documents, spreadsheets, research files, policies, source examples, requirements, and evidence packs. | Behavior rules that must always apply; put those in Project Instructions. |
| Project sources | App links, saved responses, uploaded files, pasted text, and reusable project context where supported. | Unreviewed content treated as instructions. Sources should remain source material unless promoted into reviewed instructions. |
| Project Memory | Continuity across chats and files inside the project. | Security boundaries, formal verification, or deterministic workflow requirements. |
| Project sharing | Team review, collaborative work, shared context, and multi-user project workflows. | Public distribution of a reusable assistant; use a Custom GPT or public documentation page when that is the goal. |
| Built-in tools inside Projects | Canvas, image generation, Study mode, Voice mode, web search, deep research, and agent mode where available. | Production-grade automation that needs application-side permissions, logs, tests, and deployment controls. |
Use GPTs for reusable assistants. A Custom GPT is the right surface when the workflow should be packaged as a reusable assistant with its own behavior, source material, user-facing entry points, tool access, sharing rules, and version history.
| GPT configuration | Use for | Placement rule |
|---|---|---|
| Name | User-facing assistant title. | Make it specific enough that users immediately understand the GPT’s purpose. |
| Description | Short explanation of purpose, audience, and task coverage. | Use for discovery, preview, and share surfaces. Do not make it generic marketing copy. |
| Conversation starters | Realistic starting prompts that show the intended workflow. | Use high-value examples, not vague prompts like “Help me get started.” |
| Instructions | Behavior, scope, workflow steps, output format, allowed actions, and failure behavior. | Put rules here, not in Knowledge files. |
| Knowledge | Reference files such as documentation, guides, handbooks, examples, and source material. | Use Knowledge for source material. If the GPT must cite files, specify citation behavior in Instructions. |
| Recommended model | Suggested default model for the GPT’s task. | Use when the workflow benefits from steering users toward a specific model type. |
| Capabilities | Web search, image generation, Canvas, Code Interpreter & Data Analysis, and apps where available. | Enable only capabilities required by the GPT’s job. |
| Apps | User-connected tools and services. | Use apps when user-connected external data is needed. A GPT can use apps or actions, not both at the same time. |
| Actions | External APIs defined by the GPT builder. | Use only when API access is required. Configure auth and OpenAPI schema, then test in Preview. |
| Preview | Testing behavior before sharing or publishing. | Test real prompts, tone, accuracy, tool calls, action behavior, and failure cases. |
| Version history | Reviewing and restoring previous GPT versions. | Use before major edits and after regressions. Recheck action authentication after restoring older versions. |
| Sharing / publishing | Private, direct, workspace, link, or public GPT Store distribution depending on eligibility. | Match visibility to intended audience, data sensitivity, and workspace policy. |
Use Skills for packaged reusable workflows. Skills are the best ChatGPT surface when the workflow should be reusable, shareable, and packaged with instructions, resources, examples, code, or a repeatable step sequence.
Personalization controls how ChatGPT responds across conversations. Separate response speed, style preferences, explicit instructions, remembered context, and temporary conversations because each control has a different scope and behavior.
| Control | What it changes | What it does not replace |
|---|---|---|
| Fast answers | Allows eligible information-seeking questions to receive a faster response when ChatGPT has a high-confidence answer and does not need personalization. These responses do not use past chats or Memory. | A model, reasoning level, Search, or a general instruction to keep every response short. |
| Base style and tone | Selects the ChatGPT personality that guides the general style and tone of responses. | Task-specific tone instructions, factual controls, tools, or model capabilities. |
| Characteristics | Fine-tunes response traits such as brevity, warmth, enthusiasm, use of headings and lists, and emoji level. | Personality, Custom Instructions, Memory, or the current prompt. |
| Custom Instructions | Stores explicit user-wide instructions that ChatGPT should consider across chats. | Project-specific rules, source files, credentials, or one-time task instructions. |
| Memory | Uses relevant context from chats, files, memories, and connected apps where available to personalize future responses. | Deterministic workflow control, authoritative evidence, permissions, or verification. |
| Temporary Chat | Starts a conversation that does not appear in normal history and does not access or create memories for personalization. | Custom Instructions, safety controls, or third-party data policies used by GPT actions. |
Library is the account-level storage and reuse surface for files uploaded to or created in ChatGPT. Keep it separate from Memory, instructions, Project context, and GPT Knowledge.
| File surface | Use for | Scope | Do not use as |
|---|---|---|---|
| Chat attachment | A file needed for the current conversation or task. | Current chat. | A guaranteed permanent instruction or project-wide source. |
| Library | Finding and reusing files uploaded to or created in ChatGPT. | User account or supported workspace. | Memory, behavior instructions, or a formal source-governance system. |
| Project file or source | Stable reference material required across chats in one Project. | Project. | User-wide personalization or a public reusable assistant. |
| GPT Knowledge | Reference material that a specific Custom GPT should use. | Custom GPT. | GPT behavior rules; those belong in GPT Instructions. |
| Skill resource | Supporting material packaged with a repeatable Skill workflow. | Skill. | General account storage or unrelated project context. |
Where each workflow layer belongs in ChatGPT. Use this table after classifying the workflow layer. The goal is correct placement, not feature listing.
| Workflow layer | What belongs here | Best ChatGPT placement | Do not use for |
|---|---|---|---|
| Instruction layer | Stable rules, role, boundaries, tone, output contract, workflow steps, verification requirements. | Project Instructions, GPT Instructions, Skill instructions. Use Custom Instructions only for user-wide defaults. | Source documents, credentials, private tokens, mutable business state, or one-off task input. |
| Reference / source material layer | Policies, examples, research sources, product docs, repository notes, approved references. | Project files, Project Sources, GPT Knowledge, Skill resources, Library files, or Apps where external source material lives. | Behavior rules that must always run; those belong in the instruction layer. |
| Reusable workflow layer | Repeatable procedures, reusable assistants, review workflows, standard output formats, team playbooks. | Project for ongoing context, Custom GPT for a reusable assistant, Skill for a packaged workflow. | One-off prompts that must be manually reconstructed every time. |
| Runtime prompt layer | The current task, current document, current code snippet, current question, current constraints. | The current chat message inside the relevant Project, GPT, Skill workflow, or agent run. | Permanent policies, long-lived reference files, reusable instructions, or global preferences. |
| Tool / action layer | External APIs, connected apps, web search, data analysis, file processing, visual work, browsing, terminal commands. | GPT actions, GPT apps, ChatGPT apps, built-in tools, or agent mode. Use API/internal systems for production control. | Unvalidated writes, privileged operations, sensitive actions, or production side effects without approval and external validation. |
| Memory / continuity layer | Personalization, prior chat context, project continuity, remembered preferences. | Project Memory, project-only memory, saved memories, reference chat history, Memory Sources. | Formal evidence, permissions, deterministic controls, or required source material. |
| Verification layer | Source alignment, checklist review, schema check, citation check, policy check, output acceptance criteria. | Explicit verification step in Project/GPT/Skill instructions plus final checklist before use. Use deep research citations where relevant. | Informal “looks good” review for publish, client delivery, production changes, billing, or irreversible actions. |
Use the smallest stable surface that matches the scope. The same instruction can be correct or incorrect depending on scope. Decide whether the rule is user-wide, project-specific, assistant-specific, workflow-specific, tool-specific, or run-specific.
What not to put in the wrong ChatGPT surface. Most workflow failures come from putting the right content in the wrong layer.
Official ChatGPT references used for this mapping. Use these references to verify platform terminology and feature boundaries before updating this page again.