{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifpdzyas766mhsexam3h4eik43ls23qbzu4rx6jlqw3zhvd6nzw3a",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mpmsu26j7rm2"
  },
  "path": "/t/feature-suggestion-transparent-project-memory-multi-thread-search/1385504#post_1",
  "publishedAt": "2026-07-01T23:37:28.000Z",
  "site": "https://community.openai.com",
  "textContent": "**Transparent Project Memory & Multi-Thread Search**\n\n**One-Sentence Summary**\n\nChatGPT Projects would become more trustworthy for long-term work if users could see, search, edit, source-check, and control the project memory that informs responses across related threads.\n\n* * *\n\n**Community Problem**\n\nMany users now rely on ChatGPT for serious long-term work: software development, writing, research, education, planning, business documentation, creative projects, and complex personal organization. These workflows often do not fit neatly inside one conversation.\n\nA user may create separate threads for backend code, frontend code, documentation, bug fixes, strategy, research, drafting, editing, and final review. Even when all of those conversations belong to the same broader project, the user still has to worry about whether ChatGPT has the right context at the right time.\n\nThe problem is not only whether ChatGPT can remember something. The deeper issue is that users often cannot clearly see:\n\n  * What project information ChatGPT is using\n\n  * Where that information came from\n\n  * Whether the information is current or outdated\n\n  * Whether a remembered detail was user-confirmed or inferred\n\n  * How to correct project memory without repeating themselves across many threads\n\n  * How to prevent old decisions from silently influencing new work\n\n\n\n\nThis creates friction for power users and everyday users alike. People end up repeating the same instructions, re-uploading the same context, summarizing previous threads by hand, and manually watching for drift.\n\nFor long-term work, invisible memory can become both powerful and stressful. Users need memory they can trust, and trust requires transparency.\n\n* * *\n\n**Suggested Improvement**\n\nIntroduce **Transparent Project Memory & Multi-Thread Search** as a visible, user-controlled memory layer inside ChatGPT Projects.\n\nThis feature would provide a project-level memory dashboard where users can review and manage the important facts, rules, decisions, files, and summaries that ChatGPT uses inside a project.\n\nThe system could include:\n\n  * A **Project Memory Dashboard**\n\n  * Search across related project threads\n\n  * Source-linked memory entries\n\n  * User approval for suggested memory\n\n  * Edit, delete, lock, deprecate, and restore controls\n\n  * Status labels such as Active, Suggested, Locked, Deprecated, Conflicting, or Needs Review\n\n  * Optional project-to-project memory linking with explicit user permission\n\n  * A “show sources used” option when project memory affects a response\n\n\n\n\nThe key principle should be:\n\nThe user owns the project truth. ChatGPT may suggest memory, but the user should be able to inspect, correct, lock, or delete it.\n\n* * *\n\n**Example Use Case**\n\nA developer creates a ChatGPT Project called **E-Commerce App Redesign**.\n\nInside that project, they open several threads:\n\n  * Backend API\n\n  * Database Schema\n\n  * Frontend UI\n\n  * Checkout Flow\n\n  * QA Testing\n\n  * Documentation\n\n\n\n\nIn the Backend API thread, the user finalizes several important decisions:\n\n  * The database uses PostgreSQL\n\n  * Primary IDs use UUIDs\n\n  * Checkout uses a specific payment provider\n\n  * The frontend should call /api/checkout/session\n\n  * Deprecated v1 routes should not be used\n\n\n\n\nChatGPT suggests adding these to the Project Memory Dashboard.\n\nThe user reviews the suggestions and approves them as active project memory.\n\nLater, in the Frontend UI thread, the user asks:\n\nWrite the fetch request for the checkout button.\n\nInstead of requiring the user to paste the backend schema again, ChatGPT can search the project’s approved memory and related thread context. It uses the correct route and payload structure, then shows a small note:\n\nUsed project context: Checkout API route from Backend API thread.\n\nIf the backend later changes, the user can open the Project Memory Dashboard, mark the old checkout route as deprecated, and approve the new one. Future threads then rely on the updated project truth.\n\n* * *\n\n**Why This Helps Users**\n\nTransparent Project Memory would help a wide range of ChatGPT users.\n\n**Developers**\n\nDevelopers could preserve architecture decisions, API routes, dependency choices, package rules, deployment constraints, and coding standards across many threads.\n\n**Writers and Creators**\n\nWriters could preserve canon, character rules, timelines, worldbuilding decisions, tone guides, and continuity notes across long creative projects.\n\n**Researchers**\n\nResearchers could manage source summaries, confirmed findings, open questions, methodology notes, and report decisions without losing track of what has been verified.\n\n**Students and Educators**\n\nStudents could preserve assignment requirements, rubric details, citation rules, teacher feedback, and project-specific writing constraints.\n\n**Businesses and Teams**\n\nTeams could maintain shared standards, brand voice, policy references, project assumptions, and approved source material across collaborative workspaces.\n\n**Accessibility and Cognitive Load**\n\nUsers managing complex work, interrupted workflows, caregiving responsibilities, neurodivergent organization needs, or memory-heavy projects would benefit from not having to manually rebuild context in every thread.\n\nThis would reduce repeated prompting, reduce accidental drift, and make ChatGPT feel more dependable for ongoing work.\n\n* * *\n\n**Privacy, Safety, and User Control**\n\nTransparent memory should be built around consent and user ownership.\n\nRecommended guardrails:\n\n  * Project memory should be visible and editable.\n\n  * Users should be able to delete, deprecate, or lock individual entries.\n\n  * ChatGPT should clearly distinguish user-confirmed memory from model-suggested memory.\n\n  * Sensitive information should not be promoted into durable memory without clear user awareness.\n\n  * Project-to-project memory linking should be opt-in only.\n\n  * Users should be able to disable memory use for a specific chat or response.\n\n  * Shared projects should show who created or changed a memory entry.\n\n  * Temporary chats should remain separate from durable project memory unless the user explicitly saves something.\n\n  * Memory entries should show source references when possible.\n\n  * Users should be able to ask, “What project context did you use for that answer?”\n\n\n\n\nThe system should not simply remember more. It should remember more transparently.\n\n* * *\n\n**Small MVP Version**\n\nA useful first version could include:\n\n  1. A **Project Memory** tab or sidebar\n\n  2. Searchable memory entries\n\n  3. Source links back to the originating chat or file\n\n  4. User-approved memory suggestions\n\n  5. Edit and delete controls\n\n  6. Active / Deprecated / Locked status labels\n\n  7. A “show sources used” option when project memory influences a response\n\n\n\n\nThis MVP would immediately improve trust and reduce repeated prompting, even before more advanced cross-thread or cross-project linking features are added.\n\n* * *\n\n**Relationship to Broader Workspace Improvements**\n\nThis proposal is designed to stand on its own. However, it also fits naturally within a broader set of improvements around project memory, continuity, navigation, user-controlled rules and canon, constructive feedback, drift prevention, and long-term workspace organization. Each feature would provide value independently, while together they would make ChatGPT a more trustworthy long-term workspace.\n\n**Closing Line**\n\nTransparent Project Memory is not only a memory feature.\n\nIt is a trust feature.\n\nFor ChatGPT to become a dependable long-term workspace, users need to see and control the project knowledge ChatGPT relies on.",
  "title": "Feature Suggestion — Transparent Project Memory & Multi-Thread Search"
}