This is a feature request for the OpenAI Codex App to handle project folder relocations gracefully. Currently, moving a project breaks all associated conversation threads because they are hardcoded to absolute file paths. The request proposes either automatic detection and migration of thread references or a manual dialog to update paths, acknowledging this is a common user workflow.
A starter prompt for Claude Code, what you'll need, and how to reach them.
You are an expert software engineer. Your task is to implement a solution for issue #11022 in the openai/codex GitHub repository. This issue requests the ability to update/migrate thread references when projects are moved to new locations, as current absolute file paths break threads. Fork the existing repository. Focus on a minimal viable solution: implement a manual 'Project Path Changed' dialog that appears when a previously indexed project's path is broken. This dialog should allow the user to browse to the new location and trigger an update of all affected thread references in the internal database. Assume the internal database is accessible via a well-defined API or ORM. Provide the necessary code changes, focusing on the detection logic, the UI component for the dialog (use React where applicable), and the database update function. Use the existing project's language and framework (likely TypeScript/JavaScript, Electron, and React for UI, with an unknown internal database). Detail how to detect a moved project and the database query/update logic. Provide test cases for a project moved to a new parent folder and a project renamed in place. Outline the steps to integrate this into the existing application's lifecycle, specifically when a project is loaded or attempted to be accessed. Ship an MVP that simply logs the old and new paths and the number of threads that *would* be updated, before actually committing to database changes. Verify by manually moving a test project and observing the dialog's appearance and the console logs.
Reach out to the OpenAI Codex App's developer community and users to highlight how improved project management and migration (similar to what Forge Kit offers for build loops or Repo Gardener for repo health) enhances their development workflow.
### What variant of Codex are you using? Codex App ### What feature would you like to see? ## Problem Currently, when a project folder is moved to a new location, all existing conversation threads associated with that project become inaccessible. The Codex App displays the error message "This project folder was deleted or moved" because the thread references are hardcoded to the original file path. This is a common workflow - users frequently reorganize their project folders. As noted by the Codex team (issue #11019), threads are stored in an internal database with absolute file path references, making them vulnerable to breakage on relocation. ## Proposed Solution Add a feature that allows users to **update or migrate thread references when a project has been moved**. Some possible implementations: ### Option 1: Automatic Detection & Migration When opening Codex App, detect if a previously-indexed project has been moved and automatically offer to update the thread references to the new location. ### Option 2: Manual Path Update Dialog Add a "Project Path Changed" dialog that appears when a broken project is accessed, allowing users to: - Browse to the project's new location - Co
Standard version control for open source contributions.
Standard for JavaScript/TypeScript projects, especially Electron/React.
Necessary to build and run the existing application.
New: May need to learn specifics of Electron's IPC and React component structure within the Codex app - ~2-3 days.
Learn it: React docs ↗
New: Understanding the internal database (likely SQLite or similar) and its API - ~1 day.
Learn it: Postgres tutorial ↗
Get set up: Provision a managed DB (Neon / Vercel Postgres) → set `DATABASE_URL` → connect with the driver.
Comment on the GitHub issue #11022 at https://github.com/openai/codex/issues/11022, then open a draft pull request.
“I've started working on a solution for issue #11022 regarding project relocation in Codex App. I have a working prototype for a manual path update dialog and am preparing a draft PR. Happy to collaborate and contribute this feature to improve user experience.”
Open the original ↗