Scope and Compliance
All contributions must remain within this scope:- Official OAuth authentication flows only - PKCE-based OAuth2 with proper token lifecycle management
- No token scraping, cookie extraction, or auth bypasses - All authentication must use legitimate OAuth endpoints
- No rate-limit circumvention techniques - Respect OpenAI’s rate limiting and usage policies
- No commercial multi-user resale features - This is a developer productivity tool for individual use
Local Setup
Node requirement:>=18.0.0
Development Standards
Code Quality Requirements
- TypeScript strict mode - All code must pass
strict: truecompilation - No type escape hatches - Forbidden:
as any,@ts-ignore,@ts-expect-error - Behavior-focused tests - All user-visible changes require test coverage
- Documentation parity - Keep docs aligned when commands, flags, paths, or defaults change
TypeScript Conventions
Documentation Requirements
When making behavior changes, update these files:README.md- High-level overview and quick startdocs/getting-started.md- Installation and first-time setupdocs/features.md- Feature descriptions and use cases- Affected
docs/reference/*files - Command references, settings, paths
Pull Request Process
Create Focused Branch
Include Command Evidence
In your PR description, include output from:This helps reviewers understand the runtime behavior.
Document Behavior Changes
- Update relevant documentation files
- Include migration notes for breaking changes
- Add examples of new functionality
- Update CHANGELOG.md (if maintaining one)
.github/pull_request_template.md when opening the PR.
Issue and Feature Requests
Before Opening Issues
- Search existing issues and PRs - Avoid duplicates
- Reproduce on latest
mainwhen possible - Include exact commands, output, and environment data
Bug Report Requirements
Include this diagnostic information:Feature Request Format
Include:- User impact - Who benefits and how?
- Policy/compliance consideration - Does this align with OpenAI terms?
- Alternatives considered - What other approaches did you evaluate?
- Implementation sketch - Rough technical approach (optional)
Security Reporting
Do not open public issues for vulnerabilities. Follow SECURITY.md for private disclosure:- Contact the maintainer privately via GitHub profile contact channel
- Include vulnerability description, reproduction steps, and impact assessment
- Target response time: within 48 hours
Code of Conduct
Expected Behavior
- Respectful, constructive communication
- Technically grounded discussions with evidence
- Clear reproduction steps when reporting issues
- Focus on facts and problem-solving
Unacceptable Behavior
- Requests to violate policy boundaries or OpenAI terms
- Credential sharing or unsafe security guidance
- Abusive or hostile communication
- Demands for features that enable terms violations
Testing Philosophy
See Testing Guidelines for detailed testing practices. Key principles:- 80% coverage threshold across statements, branches, functions, and lines
- Property-based testing for rotation logic and edge cases (using
fast-check) - Chaos testing for fault injection scenarios
- Windows filesystem safety - All cleanup uses
removeWithRetrywith EBUSY backoff
Repository Hygiene
dist/- Build output.tmp*/- Temporary directoriescoverage/- Test coverage reportsnode_modules/- Dependencies
License
By contributing, you agree that your contributions will be licensed under the MIT License as specified in LICENSE.This project is not affiliated with OpenAI. For OpenAI platform concerns, contact OpenAI directly.