Account-synced Personal Skills across ChatGPT and Codex devices

Open
#35,430 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust

Research direction

The issue names no repository files, tests, or entry points. Start by locating Personal Skills handling and account or session integration in the Codex repository, then identify the existing boundaries for supported surfaces, persistence, policy checks, and versioning; done requires an agreed design and passing coverage for the listed cross-device acceptance flow.

Written by the indexing model from the issue text.

Description

enhancement skills
Feature request

Provide an account-bound Personal Skills library shared by ChatGPT and Codex. It should behave
like browser bookmark sync: after signing in on another computer or supported product surface,
the user's skills should become available without manually copying or reinstalling local files.

Problem

Local filesystem skills are machine-bound, and Personal Skills may require separate installation
across product surfaces. Durable personal workflows therefore become unreliable when users
change computers or move among ChatGPT, Codex desktop, CLI, and IDE.

Users should not need to teach the same stable workflow repeatedly or maintain independent
copies on every device.

Expected behavior
  1. Bind Personal Skills and ownership to the OpenAI account.
  2. Sync canonical skill content across supported ChatGPT and Codex surfaces.
  3. Make an installed personal skill available after sign-in on a new device.
  4. Propagate updates automatically or through an account-level update policy.
  5. Provide version history, source, enable/disable state, rollback, and conflict handling.
  6. Allow personal, workspace, product, and project scopes.
  7. Preserve sandbox, approval, plugin, connector, and workspace policy boundaries.
  8. Clearly report unsupported dependencies instead of silently ignoring a skill.
  9. Support export/import using the Agent Skills format without making manual import the primary
    synchronization mechanism.
Acceptance test
  1. Create and enable a Personal Skill on computer A.
  2. Sign in to the same OpenAI account on computer B.
  3. Start a new supported ChatGPT or Codex session.
  4. Confirm the same skill version and enablement state appear without copying files or installing
    it again.
  5. Update the skill on computer A.
  6. Confirm computer B receives the new version, shows update provenance, and can roll back.
Current limitation

OpenAI's current Skills documentation says Personal Skills must be added separately on desktop
and web/mobile and do not automatically sync across those surfaces:

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.