Skip to content

chore: upgrade - #1127

Closed
shunkakinoki wants to merge 1 commit into
mainfrom
chore/upgrade
Closed

chore: upgrade#1127
shunkakinoki wants to merge 1 commit into
mainfrom
chore/upgrade

Conversation

@shunkakinoki

@shunkakinoki shunkakinoki commented Mar 17, 2026

Copy link
Copy Markdown
Owner

Automated upgrade


Summary by cubic

Added LMStudio and Ollama as model providers in Codex config to enable local LLM endpoints. Defaults to http://127.0.0.1:1234/v1 (LMStudio) and http://127.0.0.1:11434/v1 (Ollama).

Written for commit 16726ff. Summary will update on new commits.

Copilot AI review requested due to automatic review settings March 17, 2026 03:26
@shunkakinoki
shunkakinoki enabled auto-merge (squash) March 17, 2026 03:26
@mesa-dot-dev

mesa-dot-dev Bot commented Mar 17, 2026

Copy link
Copy Markdown

You do not have enough credits to review this pull request. Please purchase more credits to continue.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs an automated upgrade by extending the system's configuration to support additional local large language model providers. The change enables integration with LMStudio and Ollama, enhancing the flexibility and capabilities for local model interactions.

Highlights

  • New Model Providers Added: Configuration for LMStudio and Ollama model providers has been added to the config.toml file, allowing the system to integrate with these local large language model services.
Changelog
  • config/codex/config.toml
    • Added configuration for the 'LMStudio' model provider, including its name and base URL.
    • Added configuration for the 'Ollama' model provider, including its name and base URL.
Activity
  • No specific activity (comments, reviews, etc.) has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Mar 17, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2389b7d6-7dff-443a-bad3-48482ce8a520

📥 Commits

Reviewing files that changed from the base of the PR and between 8cada5f and 16726ff.

📒 Files selected for processing (1)
  • config/codex/config.toml

📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Added support for LMStudio and Ollama as model providers, expanding available options for model selection.

Walkthrough

Two new model provider configurations have been added to the TOML configuration file: LMStudio and Ollama, each with their respective API base URLs. These new entries complement the existing CLIProxyAPI and OpenRouter providers, expanding the available model provider options without modifying existing configurations.

Changes

Cohort / File(s) Summary
Model Provider Configuration
config/codex/config.toml
Added LMStudio provider (base_url: http://127.0.0.1:1234/v1) and Ollama provider (base_url: http://127.0.0.1:11434/v1) to the configuration file.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 Hop, hop, hooray! The config grows,
LMStudio and Ollama in a row,
New models arrive with URLs so neat,
Making the provider zoo complete!
Local AI dreams at port twenty-thirty-four,
Eleven-thousand-four-thirty-four, and more! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: upgrade' is vague and generic, using a non-descriptive term that doesn't convey meaningful information about the specific changes made. Use a more descriptive title that specifies the actual change, such as 'chore: add LMStudio and Ollama as model providers in Codex config'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The description is related to the changeset, providing specific details about adding LMStudio and Ollama model providers with their default endpoints.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mesa-dot-dev

mesa-dot-dev Bot commented Mar 17, 2026

Copy link
Copy Markdown

Mesa Description

TL;DR

Automated dependency upgrade.

What changed?

Changes related to an automated upgrade. Specific file changes are not available in the provided summary.

Description generated by Mesa. Update settings

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request adds configuration for lmstudio and ollama as model providers in config/codex/config.toml. The changes are straightforward. I've suggested a minor improvement for consistency in the configuration file.

Comment thread config/codex/config.toml
Comment on lines +41 to +47
[model_providers.lmstudio]
name = "LMStudio"
base_url = "http://127.0.0.1:1234/v1"

[model_providers.ollama]
name = "Ollama"
base_url = "http://127.0.0.1:11434/v1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For consistency with the cliproxyapi provider which uses localhost, it would be better to use localhost here as well instead of 127.0.0.1. This improves readability and maintains a consistent style for local service endpoints in the configuration.

Suggested change
[model_providers.lmstudio]
name = "LMStudio"
base_url = "http://127.0.0.1:1234/v1"
[model_providers.ollama]
name = "Ollama"
base_url = "http://127.0.0.1:11434/v1"
[model_providers.lmstudio]
name = "LMStudio"
base_url = "http://localhost:1234/v1"
[model_providers.ollama]
name = "Ollama"
base_url = "http://localhost:11434/v1"

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No issues found across 1 file

auto-merge was automatically disabled March 17, 2026 03:29

Pull request was closed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Codex CLI configuration to include additional local OpenAI-compatible model providers, broadening the set of endpoints Codex can talk to during development.

Changes:

  • Add an LM Studio provider entry pointing at the local OpenAI-compatible endpoint.
  • Add an Ollama provider entry pointing at the local OpenAI-compatible endpoint.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment thread config/codex/config.toml
base_url = "http://localhost:8317/v1"

[model_providers.lmstudio]
name = "LMStudio"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants