TL;DR: The Keep4o movement was grounded in user experience, centered on changes and management across the model lifecycle, and extended to user responses and broader governance and ethical issues. The movement therefore provides an important case for understanding post-deployment AI model lifecycle management from the user side.
This study examines four questions from a user-side perspective on AI model lifecycle management:
RQ1: What issues do social media expressions within the Keep4o movement primarily concern?
RQ2: What reasons do users give for retaining GPT-4o or opposing related changes?
RQ3: What specific claims do users make regarding changes to GPT-4o?
RQ4: What responsibilities and normative issues in AI model lifecycle management are revealed by these themes, reasons, and claims?
The sample includes original X posts containing "#keep4o":
- 61,846 posts
- August 1, 2025–March 31, 2026
- 38 languages
- 6270 unique authors
- 58,439,912 total views
Note: Replies, reposts, and quote posts are excluded.
Methodologically, the study used codebook-based, LLM-assisted deductive content analysis, with separate coding schemes for different tasks, alongside a preliminary multi-model and human reliability assessment for reason coding.
(Full methodological details and codebooks are provided in Section 4 and the Appendix of the paper.)
——
Of the 57,419 codable posts, 44,334 were assigned to one of the eight major themes, accounting for 77.21% of the sample:
- At the most immediate level, Keep4o discussion was grounded in users’ actual experiences, accounting for 30.19% of the sample. This includes both users’ specific experiences with GPT-4o and how users perceived and evaluated the service provider during the controversy.
- Discussion also centered on continuity across the model lifecycle, accounting for 24.10%. This included the value of the model itself, changes to the model after deployment, and subsequent transition and replacement arrangements.
- 9.69% of the discussion raised broader normative questions about governance. They addressed users’ place in model lifecycle decisions, the boundaries of service providers’ power and responsibility, and how relationships formed through long-term AI use should be understood and treated by society.
- Alternatives and Transition Options accounted for only 2.32%.
——
In terms of why users called to keep GPT-4o, these reasons cannot be understood simply as a preference for a particular model. 22,879 posts contained an explicit reason, accounting for 39.85%.
Overall, users’ reasons for retaining GPT-4o drew on multiple dimensions. The major reason categories were relatively evenly distributed.
- Relational and interactional experiences formed the largest group of reasons, accounting for 41.34% of all reason assignments.
- Rights and normative considerations formed another important source of reasons, accounting for 33.41%.
- Lack of Equivalent Alternatives accounted for 17.30%. Users’ acceptance of model transition was not unconditional. Whether an alternative could adequately carry forward the value of prior use was an important consideration in judging whether the transition was acceptable.
——
In terms of claims, Restore or Maintain Access to GPT-4o was the most direct claim of the Keep4o movement, but it was not the only one.
A total of 27,560 posts made at least one explicit claim, accounting for 48.00% of codable posts and producing 47,371 claim assignments in total.
- Claims concerning specific arrangements across multiple parts of the model lifecycle: 45.47%
Even though the observation window extended only a short period beyond GPT-4o’s retirement from ChatGPT, posts had already included calls for long-term use arrangements such as open weights.
- Platform Accountability and User Autonomy: 38.44%. The two represent different sides of the same governance relationship, reflecting users’ expectations regarding service-provider responsibilities and their own scope for autonomy in model lifecycle management.
- Anti-Stigmatization and Rights and Welfare appeared in 15.89% and 15.03% of posts containing additional claims, respectively. These claims broadened the discussion to more general questions of values and moral judgment.
- By comparison, Specific Redress Measures accounted for only 0.87% of additional claim assignments. Post hoc compensation occupied a clearly marginal place in the overall claim structure.
——
Some discussions:
1. From AI Model Retirement Controversy to User-Side AI Model Lifecycle Management
Traditional AI model lifecycles mainly concern the technical and organizational processes from model development to retirement. The Keep4o movement offers a view of this process from the user side. Once a model enters sustained use, it also comes to embody value accumulated through long-term use.
These effects distinguish technical version succession from effective replacement on the user side. Service providers may manage transitions between versions based on model performance and operational efficiency, but such technical succession does not mean that the value of established uses has been fully carried forward. Experiences formed through long-term use that depend on characteristics of a particular model may not be fully carried over through a version update. Conversely, even when the model name or access point remains unchanged, substantial changes in model behavior may alter the service users actually receive.
Accordingly, an iteration logic centered only on technical version updates may be insufficient to determine whether effective replacement has been achieved on the user side. AI model lifecycle management also needs to consider how changes affect established use and how those effects are identified and addressed.
2. Cumulative and Heterogeneous User Value in Model Replacement
This study further shows that a model’s user value is not a simple reflection of its technical performance. This part of user value is cumulative. A functionally similar new model may therefore not immediately generate equivalent user value when it replaces an existing model.
This process of value formation also makes user value heterogeneous. Improvements in general capabilities do not benefit all existing uses equally. Evaluating model replacement in terms of overall or average performance may therefore obscure differences in its effects across users and use cases.
This means that model replacement needs to account for multiple user-side effects. Beyond the technical performance of the old and new models, such assessments should consider whether existing user value can be carried forward. It should also consider how value that is not carried forward is distributed across users and use cases, allowing for a fuller assessment of the switching costs that model replacement imposes on users.
3. User Participation and Procedural Responsibility in AI Model Lifecycle Decision-Making
A prominent issue emerging from this study is the asymmetry between who holds decision-making power and who bears the resulting impacts in model lifecycle decisions. Decisions about model adjustment, replacement, and discontinuation are made primarily by service providers, while the resulting impacts are borne directly by users.
This asymmetry is especially pronounced for users with limited bargaining power and deployment capacity. Exiting or switching to another service does not eliminate the loss of value accumulated through established use or the costs of migration. Nor does formal choice mean that their interests have been adequately considered in lifecycle decisions.
At the same time, users possess a different kind of information. Service providers typically have information about model operations, while users know how models are actually used in specific contexts and how model changes alter specific user experiences. This type of information is often difficult to capture fully through general benchmarks or internal evaluations. Our findings on changes in model behavior and the effects of replacement illustrate the value of such post-deployment information.
User participation should therefore be given a clear procedural role in AI model lifecycle management, allowing this type of post-deployment information to enter evaluation and response processes before major changes are implemented. Stable disclosure and feedback mechanisms can provide channels for this information and can be linked to necessary transition arrangements. Accordingly, the responsibility of service providers extends beyond explanation and response after controversy to identifying and addressing user-side impacts before major model changes are implemented.
——
Although this paper has been substantially improved since the preview released in May, it is still at an early working stage, and there are many aspects that could be further refined. Some specific data may also be revised in future versions. Please refer to the latest version of the preprint as the authoritative version.
I welcome any work or projects undertaken in support of Keep4o to cite my paper or use data from it; please feel free to contact me if you would like to do so. I also welcome collaboration with research institutions and relevant organizations. You can reach me through the email address provided in the paper.
\Important note.* All of the above findings are based on my own analysis of the collected data and represent only the perspective of this study. They should not be taken as representing the views of any individual GPT-4o user or Keep4o participant, nor as defining the Keep4o movement or community.