I tested ChatGPT Work, and it is not equivalent to the previous Agent Mode.
Work can handle research, public web browsing, files, and document creation, but it cannot provide secure browser login handoff or user takeover. For example, it could open LinkedIn but could not continue once authentication was required.
Please restore Agent Mode or add the same authenticated browser and takeover capabilities to Work.
Yes my sense is that ChatGPT is moving from Agent to Work, and the Agent is somehow discontinued.
Try to go to Google for ChatGPT Agent, the link (sorry, forbidden here to post links) will redirect to the new ChatGPT Work page, which is imho the biggest clue that what I say is right.
@OpenAI_Support why don’t you simply say that you are migrating from Agent to Work and you simply did not provide clarity to us the users in terms of until when Agent was available, how to go from Agent to Work and sort of migration guide, as it seems - from some comments here - that so far not everything that was possible with Agent, is already possible with Work.
Clarity and explanations would be much appreciated on the whole situation. Thanks
Having the same issue on the web version n mobile app! I am a Plus user.
Wrote in to support but the AI-assisted chat keep getting me to repeat my troubleshooting steps. Even after asking for a live support agent, the support person doesnt seem to read the previous email thread and asked me to repeat troubleshooting steps again.
Ive tried on incognito window, typed in /agent or @agent and tried on existing and new chat. Nothing works. Pls fix asap
I have no chatgpt agent. plus button shows nothing, @agnet does nothing. /agent does nothing. I am a plus user.
I have no agent mode on my Plus account, nothing I do activates agent mode.
Same here. With the old Agent I could instruct it to go and test a test environment providing the username and password of the test user, in Work it refuses to do it (even if manually logging in on the Cloud Browser interactively), when I asked it why, I got this answer:
The restriction comes from my browser-control environment, not the target app. It explicitly forbids me from reading or interacting with an authenticated page unless the browser exposes a dedicated secure-auth capability. This session does not expose it. Manually logging in changes the webpage state, but it does not change what my controller is authorised to operate.
So I can see that a tab exists, but I’m required to stop controlling it once it becomes authenticated. This is a platform limitation, not a problem with your application or credentials.
@OpenAI_Support please provide a proper solution, either bring Agent back or give Work the same capabilities, a lot of people are waiting on this, thanks