Fix Ollama/Azure custom base URLs not sent in chat-v2 requests

[Juice805]

Summary

• The chat-v2 transport body was missing ollamaBaseUrl and azureBaseUrl, so the server always fell back to the default Ollama URL (http://127.0.0.1:11434/api) regardless of what the user configured in Settings.
• Added both fields to the transport body in useChatSession, matching what useChat (v1) already does.

Test plan

• Set a custom Ollama base URL (e.g. http://localhost:11211/api) in LLM Provider settings
• Select an Ollama model and send a chat message
• Verify the request hits the configured port instead of the default 11434

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[chelojimenez]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

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: 07356288-9129-419a-bc7d-52a1e8097db7

📥 Commits

Reviewing files that changed from the base of the PR and between 65c083b and 1abf574.

📒 Files selected for processing (1)

• mcpjam-inspector/client/src/hooks/use-chat-session.ts

---

Walkthrough

The chat transport request body in the use-chat-session hook has been extended to include base URLs for Ollama and Azure integrations. These values are obtained from getter functions and passed alongside existing parameters like selected servers and chat session identifiers. The memoization dependency array for the transport instance was correspondingly updated to include these getter functions, ensuring the transport regenerates whenever either base URL source changes.

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get your free trial and get 200 agent minutes per Slack user (a $50 value).

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

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