{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihvsb7n6kfvnytcmfryvnf3fvnz255govfo7e34bfdojf7pa4hxti",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mppdgum6lpv2"
  },
  "path": "/t/feature-suggestion-advanced-project-file-organization-for-long-term-work/1385600#post_1",
  "publishedAt": "2026-07-03T00:44:06.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@schemas"
  ],
  "textContent": "Advanced Project & File Organization for Long-Term Work\n\nOne-Sentence Summary\n\nChatGPT Projects would become more useful for serious long-term work if users had stronger tools to organize project files, track versions, label file status, reference files across threads, and safely review file changes before applying them.\n\n* * *\n\nCommunity Problem\n\nChatGPT is increasingly used for long-term projects that produce many files.\n\nA user may work with:\n\n  * Drafts\n\n  * Final versions\n\n  * Research notes\n\n  * Uploaded sources\n\n  * Code files\n\n  * Schemas\n\n  * Images\n\n  * Reports\n\n  * Meeting notes\n\n  * Style guides\n\n  * Project rules\n\n  * Feedback packages\n\n  * Archived decisions\n\n  * Deprecated versions\n\n  * Reference documents\n\n\n\n\nChatGPT Projects and file reuse are important foundations, but long-term work often needs more than a flat list of files.\n\nAs projects grow, users need to know:\n\n  * Which file is current?\n\n  * Which file is outdated?\n\n  * Which version did ChatGPT use?\n\n  * Which chat created or modified this file?\n\n  * Which files are approved sources?\n\n  * Which files should only be used for historical reference?\n\n  * Which file replaced an older one?\n\n  * Can I safely review changes before they are applied?\n\n\n\n\nWithout deeper organization, users may lose track of what is active, what is draft, what is deprecated, and what should be treated as the source of truth.\n\nThe problem is not only file storage.\n\nThe problem is workspace structure.\n\n* * *\n\nSuggested Improvement\n\nIntroduce Advanced Project & File Organization inside ChatGPT Projects.\n\nThis feature would give users a stronger project file environment with:\n\n  * Nested folders\n\n  * Project-wide file references\n\n  * File status labels\n\n  * Version history\n\n  * Diff review before applying edits\n\n  * User-confirmed write-back\n\n  * Archive and restore options\n\n  * Project-wide file search\n\n  * Source and usage history\n\n  * File relationship mapping\n\n\n\n\nUsers should be able to organize project files in ways that match real long-term work.\n\nExample folder structure:\n\n/docs\n\n/research\n\n/drafts\n\n/final\n\n/assets\n\n/archive\n\n/schemas\n\n/feedback\n\n/rules\n\nFiles could have statuses such as:\n\nDraft\n\nActive\n\nApproved\n\nDeprecated\n\nArchived\n\nReference\n\nNeeds Review\n\nSuperseded\n\nThe key principle should be:\n\nThe project should have a file system, but the user should approve every meaningful file change.\n\n* * *\n\nExample Use Case\n\nA writer creates a ChatGPT Project called Sci-Fi Novel.\n\nThey organize files into folders:\n\n/Worldbuilding\n\n/Drafts\n\n/Final\n\n/Archive\n\nThey add files:\n\n/Worldbuilding/ship_manifest.json\n\n/Worldbuilding/timeline.md\n\n/Drafts/Chapter_01.md\n\n/Drafts/Chapter_02.md\n\nIn a new thread, they ask:\n\nReview @ DraftsDrafts/Chapter_02.md and make sure the ship details @ Worldbuildingatch @ Worldbuilding/ship_manifest.json.\n\nChatGPT reviews the referenced files and responds:\n\nI found three continuity issues.\n\nI can propose edits and show a diff before applying them.\n\nThe user selects:\n\nShow diff.\n\nChatGPT displays a summary of proposed changes:\n\nProposed changes to Chapter_02.md:\n\n- Corrected ship class from “Orion Runner” to “Orion Hauler”\n\n- Removed an early reveal of the captain’s backstory\n\n- Updated the engine description to match ship_manifest.json\n\nView full diff\n\nApply changes\n\nSave as new version\n\nCancel\n\nThe user chooses:\n\nApply changes as v1.2.\n\nThe file history updates:\n\nChapter_02.md\n\nv1.0 — Initial draft\n\nv1.1 — Dialogue pass\n\nv1.2 — Continuity corrections from ship_manifest.json\n\nThe older version remains restorable.\n\nThis gives the user the benefit of ChatGPT-assisted file editing without losing control over their work.\n\n* * *\n\nDeveloper Use Case\n\nA developer creates a ChatGPT Project called App Redesign.\n\nThey organize files into folders:\n\n/src\n\n/docs\n\n/tests\n\n/schemas\n\n/archive\n\nThey mark files:\n\n/schemas/api_v1.json — Deprecated\n\n/schemas/api_v2.json — Active\n\n/docs/style_guide.md — Approved\n\nIn a frontend thread, the user asks:\n\nGenerate the chec@schemasout request using @schemas/api_@schemas1.json.\n\nChatGPT warns:\n\n@ schemas/api_v1.json is marked Deprecated.\n\nThe active schema appears to be @ schemas/api_v2.json.\n\nWould you like to use the active schema instead?\n\nThis prevents outdated files from accidentally driving new work.\n\n* * *\n\nWhy This Helps Users\n\nDevelopers\n\nDevelopers could organize code, schemas, tests, documentation, environment files, deprecated files, migration notes, and release materials.\n\nWriters and Creators\n\nWriters could organize drafts, chapters, canon files, worldbuilding notes, revision passes, final copies, and archived ideas.\n\nResearchers\n\nResearchers could organize sources, summaries, datasets, notes, methodology files, discarded leads, and final reports.\n\nStudents and Educators\n\nStudents could organize assignments, rubrics, drafts, citations, feedback, and final submissions.\n\nBusinesses and Teams\n\nTeams could organize brand guides, policies, templates, meeting notes, reports, approved sources, and archived materials.\n\nAccessibility and Cognitive Load\n\nUsers managing large, interrupted, or memory-heavy work would gain visible structure that reduces the burden of remembering what file is current and where everything belongs.\n\nThis would help ChatGPT feel more like a serious workspace, not just a place where files are temporarily attached to conversations.\n\n* * *\n\nPrivacy, Safety, and User Control\n\nAdvanced file organization should be built around user approval and reversibility.\n\nRecommended guardrails:\n\n  * ChatGPT should not overwrite files without confirmation.\n\n  * Users should be able to preview diffs before applying changes.\n\n  * Version history should support rollback.\n\n  * Deprecated files should remain accessible unless the user deletes them.\n\n  * File status should guide retrieval but not permanently hide files.\n\n  * Shared projects should show who changed what.\n\n  * Sensitive files should have clear access and sharing controls.\n\n  * Files added from Library should show whether they are linked, copied, or project-local.\n\n  * Users should be able to remove a file from a project without deleting it from Library, when applicable.\n\n  * Temporary chats should not automatically add files to durable Projects.\n\n  * File changes should not be submitted externally unless the user explicitly chooses to do so.\n\n  * Users should be able to see which files were used in a response.\n\n\n\n\nThe goal should be organization and safe collaboration, not hidden file mutation.\n\n* * *\n\nSmall MVP Version\n\nA useful first version could include:\n\n  1. Project folders\n\n  2. File status labels\n\n  3. File mentions across project threads\n\n  4. Project-wide file search\n\n  5. Version history\n\n  6. Diff preview for proposed edits\n\n  7. User-confirmed save as new version\n\n  8. Archive and deprecated status\n\n\n\n\nThis MVP would significantly improve long-term project work without requiring full autonomous file management.\n\n* * *\n\nRelationship 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* * *\n\nClosing Line\n\nAdvanced Project & File Organization is not only a file-management feature.\n\nIt is a workspace structure feature.\n\nFor ChatGPT to support serious long-term work, users need more than uploaded files.\n\nThey need organized, versioned, source-aware project files they can trust.",
  "title": "Feature Suggestion: Advanced Project & File Organization for Long-Term Work"
}