Family / Household sharing of unused Codex usage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Web / ChatGPT Codex
What feature would you like to see?
I would like to propose an optional Family / Household Usage Pool for Codex.
Each family member would keep a completely separate OpenAI account, with separate chats, memory, projects, files, privacy settings, and identity.
However, verified family or household members could voluntarily contribute some or all of their unused Codex usage allowance to a shared household pool.
Example:
- One household member uses Codex heavily and reaches their usage limit.
- Another household member has a paid subscription but uses little or none of their included Codex allowance.
Instead of sharing accounts, the second person could explicitly contribute part of their unused Codex allowance to the household pool, while the first person continues using Codex on their own account.
Possible safeguards:
- explicit approval from the person contributing usage
- verified Family / Household group
- monthly transfer or sharing limits
- ability to stop sharing at any time
- no access to another member’s chats, memory, projects, files, or data
- clear history of usage and transfers
This could reduce account sharing, improve security, and make paid subscriptions more useful for households where Codex usage is very uneven.
Additional information
OpenAI Support confirmed that Codex usage is currently account-scoped and non-transferable, and directed me to this repository to submit this as a feature request.
The proposal is not about merging accounts or sharing login credentials. Only the unused usage allowance would be shared, while all accounts and user data remain completely separate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or implementation entry points; begin by reviewing how Codex currently scopes usage to individual accounts. Done would require an agreed design for household verification, allowance transfers, limits, revocation, and privacy boundaries before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100