openai / openai/codex

Desktop: add a project-scoped Skills view for ChatGPT Projects

Open
#45,551 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement skills
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Feature request

Add a way in the ChatGPT desktop app to inspect the Skills that are available to, embedded in, or scoped to the currently selected Project.

Problem

The desktop app currently exposes a global Skills view in Settings, but there is no equivalent Project-level view for skills associated with a ChatGPT Project.

This makes it difficult to answer basic questions such as:

  • Which skills are available inside this Project?
  • Which skills are Project-scoped versus global/personal/plugin/system skills?
  • Where did a particular skill come from?
  • Is a skill actually loaded/available to chats in this Project?
  • Does the Project contain a skill that is hidden from the global Settings → Skills list?

A user can sometimes ask the assistant to describe its available skills, but that is not a substitute for an inspectable UI and does not provide a reliable management surface.

Proposed experience

In Project Settings, add a Skills section that lists skills relevant to that Project.

For each skill, show at least:

  • display name and description;
  • scope/source, e.g. Project, Personal/Global, Plugin, System, Repository/Local;
  • whether it is enabled and currently available to the Project;
  • provenance/location where applicable;
  • any dependencies or unavailable requirements.

Ideally, the same view would distinguish between:

  1. skills embedded directly in the Project;
  2. global/personal skills inherited by the Project;
  3. plugin-provided skills;
  4. local/repository skills when the Project is backed by a local workspace.

A simple read-only inventory would already solve most of the discoverability problem; editing/enable-disable controls could be added later.

Why this matters

Projects are intended to provide durable, scoped context. If skills can also affect behavior within that context, users need to be able to inspect that effective configuration without asking the model to introspect itself.

The current mismatch is especially confusing because global skills are visible in Settings, which creates the expectation that Project-specific skills should be similarly inspectable.

Expected behavior

When viewing a Project in the ChatGPT desktop app, the user should be able to open Project Settings → Skills and see the complete effective skill set for that Project, with each skill's scope/source clearly identified.

Environment
  • ChatGPT desktop app for macOS
  • Version observed: 26.908.40834
  • Apple Silicon
Related issues
  • #43324 requests a broader unified skills view as part of a larger project/navigation/context proposal.
  • #23987 asks for clearer skill source/path visibility when duplicates exist across project and global scopes.
  • #26882 asks for plugin-provided skills to be distinguished/grouped in the Skills UI.
  • #21425 covers separating installed plugins from per-session skill metadata injection and mentions local/project/plugin skill sources.

This request is intentionally narrower: a dedicated Project-scoped Skills inventory in the desktop UI.

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.

Research direction

Start at the desktop app's Project Settings flow and review the existing global Settings → Skills view, then compare the related issues #43324, #23987, #26882, and #21425. Done means Project Settings → Skills presents the complete effective skill set with each skill's name, description, scope/source, availability, provenance, and requirements; no implementation files or tests are identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.