Chat
Use Chat for questions, conversation, brainstorming, quick analysis, search, file review, and tool-assisted work that remains centered in a conversation.
Choose models and place workflows across Chat, Work, Codex, Projects, Skills, Plugins, existing GPTs, Scheduled Tasks, memory, and Library.
Choose between Chat, Work, and Codex, then select the available model and reasoning controls. Place persistent context in Projects, procedures in Skills, connected capabilities in Plugins, and files in Library or the relevant source. Maintain existing GPTs while preparing migration.
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.
Choose Codex when you need developer views, diffs, code review, and technical execution details. Work can also run code and use accessible repositories; Codex can also create research and documents. Choose between them by the required tools and review experience.
Use the API when the workflow must run inside a website, application, backend service, internal system, CI pipeline, or controlled production automation.
Select the model, reasoning effort, and speed separately where supported. GPT-6 Astra appears as GPT-6 Pro in Chat and as Astra in Work and Codex. Available controls depend on the experience, plan, workspace, and rollout.
| Option | Use for | Model |
|---|---|---|
| Instant | Everyday questions and short drafts. | GPT-5.6 Sol on eligible paid plans; GPT-5.6 Luna on Free and Go. |
| Medium | Planning and analysis. | GPT-5.6 Sol. |
| High | Complex, multi-step work. | GPT-5.6 Sol. |
| Extra High | The greatest thinking effort within Sol. | GPT-5.6 Sol on eligible plans. |
| Pro | Demanding tasks and extended reasoning. | GPT-5.6 Sol Pro or GPT-6 Pro, powered by GPT-6 Astra, where available. |
Start with the available Power default. Use Advanced for explicit model, effort, and speed choices. Astra rollout options vary by account; Sol with Medium is not a universal default.
| Control | Type | Meaning | Availability boundary |
|---|---|---|---|
| GPT-6 Astra | Model | Demanding work across research, code, and apps requiring sustained reasoning and multiple tools. | Confirm access on the selected surface. |
| GPT-5.6 Sol | Model | Complex, ambiguous work requiring analysis, judgment, or polish. | A model choice, not a reasoning level. |
| GPT-5.6 Terra | Model | Everyday work with reasoning and tool use. | Choose according to task requirements. |
| GPT-5.6 Luna | Model | Clear, repeatable tasks such as extraction and classification. | Available through Advanced where supported. |
| Reasoning effort | Per-model control | Adjusts reasoning depth within the selected model. | Light (Low in CLI), Medium, High, and Extra High where supported. |
| Max | Reasoning effort | More reasoning time for one difficult task. | May require enabling in app settings. |
| Ultra | Multi-agent mode | Uses subagents for parallel work. | Where supported, enable the desktop picker option in Settings → Configuration. |
| Fast mode | Speed control | Separate speed control; Astra consumes credits at 2.5× the Standard rate where available. | ChatGPT sign-in on desktop, Codex CLI, and IDE. The multiplier does not apply to API billing. |
Plus and Pro include Astra in Work and Codex. Business access and included usage depend on the seat and workspace. Eligible Enterprise and Edu workspaces require model-access permissions; Early Model Access does not automatically enable Astra. A workspace default does not grant access. ChatGPT access does not grant API access or override runtime permissions. Work and Codex share usage.
Retirement notice: OpenAI announced on September 14, 2026 that GPT-5.5 will retire from ChatGPT, Work, and Codex on October 14, 2026. The API is excluded. Review saved settings and scheduled tasks before that date.
On mobile, switch between Chat and Work using the mode control. In Chat, the model picker appears at the top of the conversation. Use the models and effort options available to the selected experience and account. Cloud Work can continue across web and mobile.
Use Work for multi-step tasks and finished deliverables, its supported browser and app tools for online actions, and Scheduled Tasks for future, recurring, or event-triggered work.
| Surface | Primary role | Use it when | Boundary |
|---|---|---|---|
| ChatGPT Work | Research, analysis, and completed deliverables. | The task requires tools, files, iteration, or a finished document, spreadsheet, presentation, report, or Site. | A Project supplies context; Work performs the task. |
| Cloud browser in Work | Supported website tasks. | The task needs web navigation, forms, or access to a supported signed-in website. | Website access, authentication, and consequential actions have separate controls. |
| Scheduled Tasks | Future, recurring, monitoring, or event-triggered work. | The task should run later or respond to a supported app event. | Execution environment, available sources, tools, and permissions determine what can run. |
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.
ChatGPT agent mode is no longer available. Start new multi-step tasks in Work.
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. | Distribution of a reusable workflow package; use supported Skill or Plugin sharing for that purpose. |
| Built-in tools inside Projects | Canvas, images, Study mode, Voice, search, and deep research where available. Work requires a project that supports it. | Production automation requiring application-side permissions, logs, tests, and deployment controls. |
Existing Custom GPTs package instructions, Knowledge, and capabilities as reusable assistants. OpenAI is planning their retirement and migration to Plugins. Keep existing workflows working while preparing and testing their replacements; use Skills and Plugins for new reusable workflows.
| 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 a Skill for a reusable procedure with instructions, examples, resources, or code. Use a Plugin to distribute skills together with connected apps and other supported capabilities.
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, Skill for a repeatable procedure, and Plugin for packaged skills and apps. Maintain existing GPTs during migration. | 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 message in Chat, Work, Codex, or the relevant Project, existing GPT, or Skill workflow. | 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. | Connected apps and Plugins, built-in tools, Work browser tools, or existing GPT actions. 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. | ChatGPT memory and Memory Summary, project memory, and response Sources. Local Codex memory is managed separately. | 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.