Replace default o3-mini with o4-mini

[PeterDaveHello]

User description

We should change the default setting from o3-mini to o4-mini to take advantage of the same price while benefiting from improved performance and capability.

---

PR Type

Enhancement, Documentation

---

Description

• Updated default model from o3-mini to o4-mini across documentation and configuration.

• Adjusted references to reflect the new default model in usage guides and examples.

• Ensured consistency in model naming in all relevant files.

---

Changes walkthrough 📝

	Relevant files
Documentation	index.md Updated model reference in Chrome extension documentation docs/docs/chrome-extension/index.md Replaced o3-mini with o4-mini in extension description. Updated model reference for improved clarity. +1/-1      locally.md Updated model reference in local installation guide            docs/docs/installation/locally.md Changed model reference from o3-mini to o4-mini. Updated instructions for acquiring keys with the new model. +1/-1      pr_agent_pro.md Updated model references in PR-Agent Pro overview                docs/docs/overview/pr_agent_pro.md Replaced o3-mini with o4-mini in model selection section. Updated supported languages section to reflect the new model. +2/-2      changing_a_model.md Updated default model in model-changing guide                        docs/docs/usage-guide/changing_a_model.md Updated default model reference from o3-mini to o4-mini. Adjusted examples and reasoning effort descriptions. +2/-2      qodo_merge_models.md Updated supported models and configuration examples            docs/docs/usage-guide/qodo_merge_models.md Replaced o3-mini with o4-mini in supported models list. Updated configuration examples to reflect the new model. +3/-3
Configuration changes	configuration.toml Updated default model in configuration file                            pr_agent/settings/configuration.toml Changed default model from o3-mini to o4-mini. Ensured fallback models remain consistent. +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

No code suggestions found for the PR.

[PeterDaveHello]

Maybe this one should wait for #1708

cc @mrT23

[mrT23]

/implement change fallback model to 'gpt-4.1'

[qodo-merge-pro-for-open-source]

Code Implementation 🛠️

Implementation: Update the fallback model from "gpt-4o-2024-11-20" to "gpt-4.1" as requested.

Suggested change

	model="o3-mini"
	model="o4-mini"
	fallback_models=["gpt-4o-2024-11-20"]
	model="o4-mini"
	fallback_models=["gpt-4.1"]

See review comment here

[PeterDaveHello]

Maybe leave it in another change will be cleaner 😆

[mrT23]

if we are updating to more modern models, I do want to remove the 'gpt-4o' from the config.
it looks outdated and unmaintained.
And its just the fallback model (that should not be called in normal usage)

[PeterDaveHello]

Thanks for the suggestion. I see the importance of updating to modern models. Would you mind if I submit a separate PR for this change? It would help keep the commits cleaner and make it easier for maintainers to track changes. What do you think?

[mrT23]

Thanks for the PR.
i will soon publish some benchmarks on o4-mini for PR code analysis - and indeed its very good (better than sonnet-3.7)

Please address the comments above, and we can merge

[PeterDaveHello]

Sure, I will be back with the updates soon.