HELP: Operator - "Conversation is closed."

ChatGPT
,
22

That’s really interesting, have you heard from anyone on the OpenAI team? I’m still having a hard time too

23

Any luck since? Curious if you’ve figured out a work around or if things have changed for you.

24

This defeats the object of a lot of my use case for spending $200. If I cannot go into a conversation and continue it, and iterate it, its a waste of money.

Tasks is a considerably more basic and simplistic use case and it does better than this.

I don’t understand why conversations cannot stay open?

1 Like
25

Same! I use DeepResearch quite often, so it’s not a complete waste but the fact that Operator has been a flop is incredibly disappointing.

26

This is happening again today.

Trying Manus now.

27

The image shows a screenshot of a Japanese real estate website, suumo.jp, with information about available properties and listings. (Captioned by AI)
The image shows a screenshot of a Japanese real estate website, suumo.jp, with information about available properties and listings. (Captioned by AI)1928×1466 250 KB

Ugh, what am I paying $200/mo for? This becomes unbearable.

28

The image shows a detailed message summarizing real estate listing results within a 5-minute walk radius, presenting statistics on unique buildings, unique units, and total agent advertisements, and asking the recipient to choose between a summary table of distinct units or a longer table counting each broker's ad. (Captioned by AI)
The image shows a detailed message summarizing real estate listing results within a 5-minute walk radius, presenting statistics on unique buildings, unique units, and total agent advertisements, and asking the recipient to choose between a summary table of distinct units or a longer table counting each broker's ad. (Captioned by AI)1610×1542 125 KB

How can I even use it like this??

29

If you ask it it’ll tell you this:

In this workspace the session typically times out after about 15–20 minutes of user inactivity.
If you plan to step away for longer than that, just send a quick message (“still here” works) before the 15‑minute mark to keep the thread active. I’ll continue gathering data in the meantime and will be ready with updates whenever you check back in.

The session timeout is set by the platform itself, so we can’t extend it manually. The best workaround is simply to keep the thread “alive” with brief messages—either:

  1. You send a short note every 10–15 minutes (“still here,” “continue,” etc.), or
  2. I can post a quick progress update at similar intervals, which will also reset the inactivity timer.

If you’d like me to send periodic status pings while I work, just let me know the interval (e.g., every 10 minutes), and I’ll do so until the first 50‑entry batch is finished.

So, assuming it’s correct, it’ll end by itself often. Bummer to read but I do think Claude Computer Use might be what we need, removing this limitation.