openai / openai/codex

Secure password manager integration for ChatGPT’s built-in browser and Work / Codex

Open
#43,916 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What variant of Codex are you using?

App

What feature would you like to see?

I use the ChatGPT desktop app on macOS with its built-in browser, and Bitwarden as my password manager. In my current setup, the usual password manager integration is unavailable, which makes signing in to websites and creating new accounts more cumbersome.
I would like to suggest adding password manager support at two levels: standard autofill when browsing manually, and secure credential use in agent-assisted workflows such as Work / Codex.
A particularly useful workflow would be:
“Create an account for me on this service using my work email, generate a strong, unique password, and save the credentials to my password manager.”

Before proceeding, ChatGPT should display a trusted confirmation dialog showing the exact website domain, the selected email address, and the destination vault. I would then approve the operation and unlock my password manager if necessary.
The AI model itself should not need to see the password or have access to the entire vault. Password generation, storage, and form filling should be handled by a separate, secure component. The agent should receive only the operation’s status, without exposing passwords or other secrets in chat history, model memory, screenshots, or tool logs.
Access should be scoped to specific websites and accounts, with revocable permissions and an activity log that never contains passwords. Approving account creation should not automatically authorize purchases, paid subscriptions, or changes to security settings.
The workflow should also handle failures safely. If registration or credential storage fails, the user should see exactly which steps succeeded and which did not. A generated password should never be lost after an account has already been created.
There is no need to support every password manager from the start. An initial integration with one established provider, or a built-in secure solution designed to support third-party password managers later, would already be valuable.

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 issue names no files, tests, or entry points. Start by reviewing the macOS desktop app’s built-in browser and Work / Codex credential flows, then define the integration boundaries and confirmation steps. Done should include scoped approvals, secret isolation, safe failure handling, and an activity log without passwords.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.