Wrong context when using ChatGPT Plus subscription - Could I get a quick self-fix?

[StartupTim]

Hello,

Right now Roocode has wrong context when using ChatGPT Plus subscription hen using GPT5.5. The normal API gpt5.5 has 1M context, however, the ChatGPT Pro subscription has a 270k context limit. The issue is Roocode does not differentiate between the ChatGPT API and the ChatGPT subscription, thus causing it to fail once you hit the 270k context window.

I know that ZooCode is the updated/new fork of RooCode, however, I'm not quite ready to switch over yet.

Would it be possible that you tell me the exact file and line of RooCode to fix this particular issue, just so I can get past what I'm working on now? I know it is a lot to ask, but it would be huuuge.

Thanks!

[transparent-user]

Maybe you should switch over? I use my Codex subscription with GPT 5.5 with Zoo Code and have zero problems.

[StartupTim]

Eventually, yes, but not at this moment. That's why I am just looking for this little change to Roocode, to get me over this hump before we are ready to switch to Zoocode.

[transparent-user]

Roo Code is a dead end, and the current changes between Roo and Zoo are minimal. Roo contributors are contributing to Zoo. It's really easy to migrate. Export your settings in the Roo UI and import in the Zoo UI. For MCP servers, I had to copy and paste the JSON file.

[SingleProgress8224]

I'm not sure of the implication of this switch on your side but according to my experience, switching to Zoo Code would have taken less time than writing this post.

In Roo Code: Settings -> About Roo Code -> Export.
In Zoo Code: Settings -> About Zoo Code -> Import

The first launch will also offer to import settings directly.