openai / openai/codex

Allow launching Custom GPTs inside Codex / Work with preserved instructions and knowledge

Open
#42,827 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What variant of Codex are you using?

Codex App

What feature would you like to see?

Add the ability to launch an existing Custom GPT directly inside Codex and/or ChatGPT Work while preserving its configured instructions, knowledge files, and intended behavior.
Today, specialized Custom GPTs are used mainly in ChatGPT, while Codex and Work provide the tools needed for real project work: repository access, terminal/shell, tests, and agent execution.
As a result, users who already created a highly specialized Custom GPT have to manually recreate its behavior using AGENTS.md, Project Instructions, and additional prompt files. This is duplicative, error-prone, and makes it difficult to keep the behavior consistent.
Ideally, Codex and Work should allow selecting an existing Custom GPT as the active agent/profile for a session, while carrying over its custom instructions, knowledge files, and behavior where compatible.

Additional information

Example use case: a custom application-security / pentesting GPT could retain its security-review methodology while gaining access to the full repository, terminal, tests, git history, and local tooling. This would turn existing Custom GPTs into reusable agent profiles instead of chat-only configurations.

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 by reviewing how Codex App and ChatGPT Work currently load AGENTS.md, Project Instructions, and additional prompt files, then trace the session or agent-profile entry point. Compare that flow with existing Custom GPT instructions and knowledge files. Done means an existing Custom GPT can be selected for a session and its compatible instructions, knowledge, and behavior are preserved alongside repository, terminal, test, and git access.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, devtools
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.