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.
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.
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. Ask what the workflow must produce:
The name of the old tool is less important than the destination artifact and authority boundary.
Do not simply replace the words ChatGPT agent
with ChatGPT Work
. Rewrite the task contract to name:
This prevents an old prompt from silently carrying browser, credential, payment, or filesystem assumptions into a different execution surface.
Cloud browser, the desktop built-in browser, the Chrome extension, connected apps, local files, and repository tools have different authority.
The complete source-linked transition map, browser boundaries, and operating checklist are available here:
https://tgwise.com/intelligence/chatgpt-agent-transitioned-to-chatgpt-work/