Description

OllamaLLM in the TypeScript SDK ignored the user-provided url config and always connected to localhost:11434, even when a remote Ollama server was configured.

Root cause: The constructor used config.config?.url (double-nested, always undefined) instead of config.url. Additionally, the url field was missing from the LLM config pipeline —
ConfigManager didn't pass it through, and Zod validation stripped it.

Fix: Three changes to match how the embedder side already works correctly:

• ollama.ts — Fix config.config?.url → config.url || config.baseURL
• config/manager.ts — Pass url through in LLM config
• types/index.ts — Add url to LLMConfig interface and Zod schema

Fixes #4059, fixes #4104

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Unit Test

4 new tests in config-manager.test.ts covering:

• URL preserved in LLM config when provided
• baseURL and url coexist without interference
• Default baseURL fallback when neither is provided
• Both embedder and LLM url preserved independently

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Maintainer Checklist

• closes OllamaLLM constructor uses wrong config nesting — falls back to localhost:11434 ignoring configured URL #4059
• closes How to configure openclaw-mem0 with Local Ollama when its installed on a different system in the network? #4104