I would like to build a privacy-preserving global Codex skill that synchronizes a user’s saved projects and sanitized project/chat context across their computers.
The current tool surface can list existing projects and create tasks inside an existing project, but it does not expose supported operations for creating a saved local project or managing its directories and repositories.
Requested project-management capabilities:
- create_project(title, description, roots, idempotency_key)
- update_project(project_id, title, description)
- list, add, and remove project directories or repositories
- return stable project metadata suitable for cross-device reconciliation
- support lookup-before-create or an idempotency key to prevent duplicates
- provide paginated project-task discovery
Use case:
A user runs “Sync my projects” on computer A. The skill stores an approved, sanitized project catalog and chat continuation checkpoints in the user’s private Google Drive folder. On computer B, the same command matches existing projects, creates missing saved projects, and restores their sanitized chat streams. Projects found only on computer B are added to the shared catalog for the next synchronization on computer A.
The workflow would not copy source code, Git diffs, credentials, raw transcripts, or private repository URLs. Repository cloning and source synchronization would remain separate, explicitly authorized operations.
Without a project-creation API, remote project metadata can be discovered on another computer, but the project still has to be added to Codex manually.
Would the Codex team consider exposing supported project creation and project-root management tools?