DhanushSantosh 7583598a05 fix: differentiate Codex CLI models from Cursor CLI models ...

- Fix isCursorModel to exclude Codex-specific models (gpt-5.1-codex-*, gpt-5.2-codex-*)
- These models should route to Codex provider, not Cursor provider
- Add CODEX_YOLO_FLAG constant for --dangerously-bypass-approvals-and-sandbox
- Always use YOLO flag in codex-provider for full permissions
- Simplify codex CLI args to minimal set with YOLO flag
- Update tests to reflect new behavior with YOLO flag

This fixes the bug where selecting a Codex model (e.g., gpt-5.1-codex-max)
was incorrectly spawning cursor-agent instead of codex exec.

The root cause was:
1. Cursor provider had higher priority (10) than Codex (5)
2. isCursorModel() returned true for Codex models in CURSOR_MODEL_MAP
3. Models like gpt-5.1-codex-max routed to Cursor instead of Codex

The fix:
1. isCursorModel now excludes Codex-specific model IDs
2. Codex always uses --dangerously-bypass-approvals-and-sandbox flag

2026-01-08 23:03:03 +05:30

..

lib

Merge branch 'v0.9.0rc' into remove-sandbox-as-it-is-broken

2026-01-07 15:01:31 -05:00

providers

fix: differentiate Codex CLI models from Cursor CLI models

2026-01-08 23:03:03 +05:30

routes

feat: address pr comments

2025-12-29 16:03:27 +01:00

services

feat: enhance global settings update with data loss prevention

2026-01-07 21:38:46 -05:00