openai / openai/codex

[macOS][Computer History] Retire or dismiss “Suggested skill” cards after the Skill is created

Open
#41,225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What variant of Codex are you using?\n\nCodex App in the ChatGPT desktop app on macOS.\n\n### What feature would you like to see?\n\nComputer History “Suggested skill” cards should have a lifecycle independent of the underlying history entry.\n\nWhen the suggestion’s Codex task successfully creates the Skill—or verifies that the exact Skill already exists—the suggestion should be marked fulfilled and its Create action retired. Users should also have a separate Dismiss or Mark completed control that preserves the timeline summary and memory.\n\n### Additional information\n\nObserved on ChatGPT desktop 26.820.80927 (build 7271), macOS 26.6.2, Apple Silicon.\n\nThe suggestion remained in two separate cases after the corresponding Skill workflow completed. The only available cleanup was deleting the entire Computer History item, which also deleted the associated memory.\n\nOpenAI Feedback ID: no-active-thread-01a045a3-4954-7a21-90f7-4d181fdaf721\n\nSuggested acceptance criteria:\n- Creating the suggested Skill marks the suggestion fulfilled.\n- Detecting that the exact Skill already exists also marks it fulfilled.\n- The Create action is retired or replaced with a completed state.\n- A suggestion can be dismissed without deleting its history item or memory.\n- The fulfilled/dismissed state survives refresh and restart.\n- No installed Skill or history item is automatically deleted.\n\nNo raw Computer History events, private activity, screenshots, or diagnostics are attached.

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

No files, tests, or entry points are named. Start by locating the Computer History Suggested skill implementation and its persistence path, then trace creation, exact-existing detection, dismissal, and refresh/restart behavior. Done means the acceptance criteria hold without deleting the history item, memory, or installed Skill.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.