openai / openai/codex

Passwords in the project folder

Open
#45,803 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What variant of Codex are you using?

Astra and sun

What feature would you like to see?

Hi OpenAI team,

I'm a ChatGPT beta tester and I'd like to suggest a privacy feature for Projects.

It would be very useful to have the option to lock individual ChatGPT Projects using a PIN, password, or biometric authentication, instead of having to protect the entire ChatGPT app.

For example, a user could keep regular Projects accessible while requiring authentication to open Projects containing personal, academic, professional, or otherwise private conversations and files.

Some useful options could include:
• PIN/password protection for individual Projects;
• fingerprint or biometric authentication;
• automatic locking after a period of inactivity;
• hiding conversation titles and previews while a Project is locked;
• keeping unlocked Projects accessible normally.

I think this would add an important extra layer of privacy for users who use ChatGPT for different areas of their lives.

Thank you for considering this feature and for continuing to improve the beta experience.

Additional information

No response

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

The request describes locking individual ChatGPT Projects with PIN, password, biometric authentication, inactivity locking, and hidden previews, but it does not identify any Codex files, tests, or entry points. First clarify whether this belongs in the Codex repository and identify the relevant subsystem. Done would require an agreed scope and an implemented, tested project-locking feature.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.