Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/config/index.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@ export const chatgptApiModelKeys = [
'chatgptApi4o_128k',
'chatgptApi4oLatest',
'chatgptApi5Latest',
'chatgptApi5_1Latest',

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While adding the new model here is logical, it places the gpt-5 models between gpt-4o models (chatgptApi4oLatest on line 54 and chatgptApi4oMini on line 57), which can be confusing for future maintenance. To improve readability, it would be better to group all models of the same family together. A small refactoring to group all gpt-4o models before the gpt-5 models would be an improvement.

'chatgptApi4oMini',
'chatgptApi4_8k',
'chatgptApi4_8k_0613',
Expand Down Expand Up @@ -256,6 +257,7 @@ export const Models = {
},
chatgptApi4oLatest: { value: 'chatgpt-4o-latest', desc: 'ChatGPT (ChatGPT-4o latest)' },
chatgptApi5Latest: { value: 'gpt-5-chat-latest', desc: 'ChatGPT (ChatGPT-5 latest)' },
chatgptApi5_1Latest: { value: 'gpt-5.1-chat-latest', desc: 'ChatGPT (ChatGPT-5.1 latest)' },

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The ordering in the Models object is also becoming inconsistent. For instance, gpt-4.1 models are defined after gpt-5.1. While this is a pre-existing issue, for better maintainability, it would be beneficial to group these model definitions by family. A follow-up task to refactor the order would be valuable.


chatgptApi4_1: { value: 'gpt-4.1', desc: 'ChatGPT (GPT-4.1)' },
chatgptApi4_1_mini: { value: 'gpt-4.1-mini', desc: 'ChatGPT (GPT-4.1 mini)' },
Expand Down
Loading