ChatGPT agent is no longer available. Reinstalling the desktop app will not restore the old surface. OpenAI now separates longer non-code work, repository work, and browser authority across different tools.
The short answer
Use ChatGPT Work for research, analysis, documents, spreadsheets, presentations, reports, and Sites.
Use Codex for repository edits, tests, commands, code review, and software-development workflows.
Use the desktop built-in browser when the user can sign in and authorize specific tabs. Use the Codex Chrome extension when the task needs an existing Chrome profile, cookies, sessions, or extensions. The cloud browser is for supported public pages and should stop at sign-in or payment.
Why ChatGPT agent disappeared
This is a product transition, not a local installation failure. OpenAI's current guidance directs longer multi-step work and finished deliverables to ChatGPT Work while keeping Codex as the software-development surface.
If Work is missing, check plan eligibility, staged rollout, workspace role, model availability, and organizational policy before reinstalling anything.
Choose by final artifact
Ask what the workflow must produce:
- A research packet, spreadsheet, presentation, report, or Site: choose ChatGPT Work.
- A code change, test result, patch, command log, or repository review: choose Codex.
- A task that must inspect an authenticated website: use a human-controlled signed-in browser surface.
- A public-page lookup without authentication: cloud browser may be sufficient.
The name of the old tool is less important than the destination artifact and authority boundary.
Rewrite old agent prompts
Do not simply replace the words ChatGPT agent with ChatGPT Work. Rewrite the task contract to name:
- The approved source set.
- The final artifact and format.
- The local files, connected apps, or browser tabs allowed.
- Actions that require confirmation.
- Review criteria, retry limit, and stop condition.
- Evidence that proves the result outside the completion message.
This prevents an old prompt from silently carrying browser, credential, payment, or filesystem assumptions into a different execution surface.
Keep browser boundaries explicit
Cloud browser, the desktop built-in browser, the Chrome extension, connected apps, local files, and repository tools have different authority.
- Do not paste passwords or payment details into a Work task.
- Sign in yourself on the human-controlled browser surface.
- Open only the minimum folder, app, or tab required.
- Review consequential confirmations before they run.
- Verify the final file and external state independently.
Migration checklist
- Classify the old task by its final artifact.
- Choose Work, Codex, or the appropriate browser surface.
- Remove obsolete assumptions about the former agent interface.
- Re-check plan and workspace eligibility.
- Name protected actions and approval gates.
- Run one bounded known-answer task before migrating scheduled work.
The complete source-linked transition map, browser boundaries, and operating checklist are available here:
https://tgwise.com/intelligence/chatgpt-agent-transitioned-to-chatgpt-work/
Top comments (0)