I recently wanted to answer a fairly basic question:
What projects do I actually have, what is still active, and what has been sitting untouched for months?
I had around 30 ChatGPT Projects, ranging from current work to old research, writing projects, reference collections, experiments and a few containers that were probably ready to be deleted.
At first, the obvious approach seemed to be opening every Project separately and creating some kind of inventory.
Then we found a much simpler workflow:
Create one audit chat and move that same chat from Project to Project.
The process was:
- Start a normal chat dedicated to the project inventory.
- Move that chat into the first Project.
- Let ChatGPT inspect the Project context and available Project files.
- Record a short audit in the same chat: purpose, current state, last meaningful work, open items, and a simple recommendation such as active / paused / keep / merge / delete.
- Move the same chat into the next Project.
- Repeat.
Because the audit itself stays in the same conversation, the result is one continuous master inventory instead of 30 separate summaries.
After going through all of my Projects, that single chat contained a table of all 30 Projects with their status and next action. I can now pin the chat and use it as a living project index: add new Projects when they appear, update statuses, and remove entries when Projects are deleted.
There was one important limitation:
Moving the audit chat into a Project gave it access to the Project context and files, but not reliably to the contents of all older chats inside that Project.
That turned out not to be much of a problem.
For well-documented Projects, the Project files were actually a better source than dozens of old conversations.
For older chat-only Projects, I opened the relevant old chat and asked:
“Summarize this entire chat for a project inventory in no more than three sentences: purpose, main results, last state, open items. No new research.”
I then pasted that summary into the audit chat and continued.
The interesting part is that this required no special project-management feature at all. It just used the fact that a conversation can be moved between Projects while retaining its own growing audit history.
For me, this was much more efficient than trying to build a project overview from the sidebar alone.
In short:
One movable chat = one cross-project audit log.
It may be useful for anyone who has accumulated enough Projects that the Projects list itself has become something that needs managing.