Suggestions for Improving ChatGPT
I would like to share a few suggestions for improving ChatGPT based on my personal experience using the platform.
These ideas are not demands, nor do they imply that OpenAI is obligated to implement them. They are simply suggestions that I believe could improve the user experience for both free and paid users.
I understand that introducing new features involves technical, financial, and organizational considerations. My intention is simply to contribute some ideas that might be worth considering for future updates.
-–
1. Improvements to Context Windows and Performance
One of the difficulties I have encountered is the limitation on long conversations.
Although automatic summarization and conversation continuation features help address this issue, I believe there is still room for improvement.
I would like to suggest:
- Free plan: Increasing the maximum conversation capacity, for example, by offering approximately half the maximum number of messages that conversations used to support before displaying the message “You’ve reached the conversation limit” and the option “Start a new chat”.
- Paid plans: Offering a capacity similar to or greater than the previous limits, while allowing users to adjust the context size according to their needs.
- Performance: Separating the amount of information the AI can use as context from the amount of conversation history the application needs to display and load on the user’s device.
This last distinction is particularly important. A conversation may require a large amount of context without forcing a mobile device to load and render its entire history constantly.
The goal would be to support longer conversations without negatively affecting application performance.
2. A More Advanced Organization System for Projects
Projects can already contain multiple conversations and files, but I believe they could benefit from a more specialized conversation management system.
I propose introducing different conversation categories:
- Reference chats: Conversations containing essential project information, such as rules, characters, data, timelines, mechanics, and important decisions. The AI should be able to consult these conversations and prioritize them whenever relevant.
- Development history: Previous conversations that have been completed. These could be automatically archived when they reach their limits or are replaced by a continuation.
- Current working chat: The main conversation where the project is actively being developed.
- Secondary chats: Parallel conversations dedicated to different tasks, such as character development, research, or working on specific parts of a project.
Users should be able to organize these categories themselves, with the exception of development history, which could be managed automatically.
Continuity Between Conversations
When a conversation reaches its limit, the system could:
1. Automatically generate a summary of the conversation.
2. Create a new continuation chat.
3. Preserve the context of the last message in addition to the summary, preventing recent corrections or information from being lost.
4. Allow the AI to consult summaries and selected relevant sections of previous conversations whenever necessary.
Customizable Summaries
I would also suggest allowing users to specify which information they consider most important before a summary is generated.
For example:
- Definitive decisions.
- Characters and their characteristics.
- Event timelines.
- Corrections made during the conversation.
- Discarded or modified ideas.
- Contextual information that might still be useful.
The level of detail could also be configurable.
Additionally, it would be important to distinguish between definitive information, historical information, and provisional ideas. The AI should not automatically modify a project’s reference information. Users should decide which details become definitive.
Automatic and Manual Archiving of Project Conversations
I propose that completed conversations be automatically moved to a category called “Completed”, rather than remaining mixed with active conversations.
It would also be useful to have a manual archiving option, without having to wait until a conversation reaches its limit.
For example, users could archive their working chat at the end of the day and start a new one the following day, while keeping the previous conversation available for reference.
Archived conversations should remain accessible, searchable, and available as information sources whenever necessary.
The goal would be to keep projects organized, reduce conversation clutter, and make active conversation management easier.
3. Archiving and Context Retrieval for Regular Chats
This idea could also be applied outside Projects, to regular ChatGPT conversations.
ChatGPT already allows users to archive conversations manually, but I believe this feature could be improved so that archiving a conversation does not mean losing the ability to retrieve and use its information and context.
I propose:
- A dedicated category for archived conversations.
- The ability to archive conversations manually.
- Options to automatically archive old or completed conversations.
- The ability to search and retrieve archived conversations.
- Keeping archived conversation information available for ChatGPT to consult when the user allows it or when it becomes relevant.
In this way, archiving would primarily serve to organize the conversation list without making the archived information inaccessible.
It could also help reduce the number of active chats displayed in the interface and make navigation easier, especially for users who maintain many conversations.
4. Independent Usage Limits for Messages, Files, and Images
One difficulty I have noticed in the free plan concerns temporary usage limits.
Based on my experience, when files or other multimedia features are used, there may come a point when the ability to continue writing in a conversation is temporarily restricted. There can also be situations where the ability to upload files runs out while sending regular messages is still possible.
My suggestion is to make these limits independent of one another.
For example:
- If the image limit is reached, users should temporarily be unable to send more images, but should still be able to write messages.
- If the file upload limit is reached, users should temporarily be unable to attach more files, but should still be able to continue chatting.
- If the message limit is reached, the corresponding message restriction would apply.
Paid subscriptions could offer higher usage limits, but I believe separating these restrictions would also benefit free users.
The goal would be to prevent reaching the limit of one specific feature from interrupting other features that are still available.
5. A “Superchat” as an Independent Advanced Mode
Finally, I would like to suggest an advanced conversation mode that could be called “Superchat”.
Unlike a regular conversation with increased limits, this would be an independent mode designed to provide a much more complete working experience.
It could include:
- A considerably larger context window.
- Advanced options for configuring context size.
- Exclusive tools unavailable in regular chats.
- Greater capabilities for working with extensive and complex projects.
- Automatic summaries to facilitate continuity.
- Advanced conversation history and information management.
I also believe it is important for this mode to distinguish between context and conversation history visualization. Even if Superchat can work with an enormous amount of information, it should not force the user’s device to load all that content simultaneously.
The idea is to offer more than just a longer conversation: an advanced workspace with its own tools and capabilities.
This mode could be included in a paid subscription, providing additional benefits without unnecessarily worsening the experience of users on the free plan.
-–
These are the suggestions I would like to share.
They all come from the same idea: improving the ChatGPT user experience, making complex projects easier to manage, and offering more flexible tools for different needs.
I do not expect every suggestion to be implemented, nor do I intend to dictate what the development team should prioritize. I simply believe these ideas could be worth considering for the future of the platform.
Thank you for taking the time to read these suggestions and consider user feedback.