Although it might not be related to today’s 4o bug, I have a question: Why do Project chat windows always default to GPT-5?

Understanding Default Model Settings in Project Chat Windows: Insights and User Experiences

In the evolving landscape of AI-powered communication tools, user experience and system behavior nuances often prompt valuable discussions among users. Recently, a user shared an intriguing observation regarding the default model selection in project-specific chat windows within a popular AI application.

The user noted that following an app update to version 252 on iOS, starting from that update, each chat window within projects automatically resets to GPT-5, regardless of the previously selected model. This behavior is particularly noteworthy because, prior to the update, the application preserved the last used model at the per-window level, allowing for a tailored experience within each chat. After the update, however, every time the app is restarted, these windows default to GPT-5, even when the user had chosen different models earlier.

Interestingly, this issue appears to be isolated to the iOS app and specifically affects chat windows within project environments. The web version of the platform and chat windows outside of projects remain unaffected, suggesting a possible regression or intentional modification in the app’s project-specific chat functionality.

Such behavior raises several points for consideration:

• Is this an unintended bug introduced in the latest update?

• Could this be a temporary change pending future enhancements?

• Might it be a strategic decision by the developers to standardize certain models within projects?

For users encountering similar issues, potential workarounds include manually re-selecting preferred models in each chat window or monitoring updates from the development team for official fixes or explanations.

This scenario underscores the importance of thorough testing and user feedback in software development. As applications grow more complex, maintaining intuitive and consistent user experiences remains a key priority.

If you have observed similar behaviors or have insights into this change, engaging with the community or reaching out to support channels can help foster a collaborative approach to resolving such issues.

In conclusion, while the defaulting of chat models to GPT-5 within project windows may seem minor, it reflects broader themes of user customization, system reliability, and development transparency. Staying informed and proactive can ensure a smoother experience as these platforms continue to evolve.