OpenAI recently introduced OAuth authentication for ChatGPT subscriptions, allowing tools like Cline to use your existing subscription instead of managing API keys. Here are the key restrictions: cline
The main restriction is rate limiting tied to your ChatGPT subscription tier: reddit
- Plus users: Around 300–1,500 local messages every 5 hours, or 50–400 cloud tasks depending on complexity
- Pro users: Higher limits but still capped with 5-hour and weekly limits
- Usage counts against your overall ChatGPT subscription quota, not separate API credits github
Many users report hitting limits quickly, especially with intensive agentic coding workflows. community.openai
The models available depend on your subscription tier :
- gpt-5.2-codex: Optimized for agentic coding
- gpt-5.2: General-purpose with strong reasoning
- gpt-5-mini: Fast and cost-effective
- o3 / o4-mini: Advanced and everyday reasoning tasks
| Aspect | OAuth (ChatGPT Subscription) | API Keys |
|---|---|---|
| Pricing | Flat-rate (subscription) cline | Pay-per-token reddit |
| Limits | Time-based (5h/weekly caps) github | Token/request limits platform.openai |
| Setup | One-click sign-in | Manual key management |
| Credential exposure | Tokens handled automatically cline | Risk of accidental commits |
- Shared quota: Usage in Cline draws from the same pool as your ChatGPT web/app usage github
- No separate budget: You cannot add API credits to bypass OAuth limits—they're tied strictly to your subscription tier github
- Security: Your OpenAI credentials never leave OpenAI's servers; Cline only receives access tokens cline
For heavy coding use, some users find the 5-hour and weekly caps frustrating and prefer third-party providers or direct API access for more flexibility. community.openai
The Code Review in OpenAI Codex is a dedicated feature that analyzes your code changes and provides feedback before you commit or open a pull request. It has a separate usage quota from regular local/cloud tasks.
What Code Review Does
The
/reviewcommand launches a specialized reviewer that examines diffs and reports prioritized, actionable findings without modifying your code. It offers several review modes:[inventivehq]Review against a base branch: Compares your branch against
mainordevelopbefore opening a PRReview uncommitted changes: Analyzes staged or modified files
Review a commit: Examines a specific commit
Custom review instructions: Tailored analysis (e.g., "Focus on SQL injection and XSS vulnerabilities")[inventivehq]
Why It Has Separate Limits
Code reviews are treated differently because they're designed to provide "the quality and depth of a senior engineer". The reviews:[linkedin]
Use a more capable model by default (GPT-5.2-Codex)[openai]
Analyze entire diffs rather than responding to individual prompts
Generate comprehensive, structured feedback
Weekly vs. Per-Task Quotas
The code review quota is intentionally lower because each review consumes significant compute to thoroughly analyze your changes. It's meant for pre-commit/pre-PR checks rather than continuous use throughout development.[openai]
What Code Review Does
The
/reviewcommand launches a specialized reviewer that examines diffs and reports prioritized, actionable findings without modifying your code. It offers several review modes: [inventivehq](https://inventivehq.com/knowledge-base/openai/how-to-use-codex-for-code-review)mainordevelopbefore opening a PRWhy It Has Separate Limits
Code reviews are treated differently because they're designed to provide "the quality and depth of a senior engineer". The reviews: [linkedin](https://www.linkedin.com/posts/openai_automatic-code-reviews-with-[openai](https://openai.com/index/introducing-upgrades-to-codex/)-codex-activity-7391540012443590656-5j_Q)
Weekly vs. Per-Task Quotas
/reviewcommand or GitHub PR reviewsThe code review quota is intentionally lower because each review consumes significant compute to thoroughly analyze your changes. It's meant for pre-commit/pre-PR checks rather than continuous use throughout development. [openai](https://openai.com/index/introducing-upgrades-to-codex/)