fix(ollama): make agent + tool calls work against Ollama Cloud

[craigamcw]

Problem

Using Ollama Cloud (https://ollama.com/v1) with the agent fails with 400 invalid message format — but only on the cloud endpoint; local Ollama and other relays accept the same requests. Captured the exact request body Ollama Cloud rejects and traced it to two serialization issues.

Fixes

1. User content serialized as an array instead of a string
For any image-capable model, the openai-completions provider emitted content: [{ "type": "text", "text": "…" }]. Ollama Cloud only accepts a plain string for text content. This flattens text-only content to a string (the standard OpenAI Chat Completions form that OpenAI, OpenRouter, and Ollama all accept), keeping the array form only when there's an actual image.
→ patches/@mariozechner+pi-ai+0.60.0.patch

2. Non-standard { "type": "thinking" } content block on follow-up turns
DeepSeek-V4 models set requiresThinkingInContent, which serializes the assistant's prior thinking into content[] as { "type": "thinking", … }. Some custom relays require that, but Ollama Cloud rejects it (it's not a valid OpenAI content type), so the second agent turn (after a tool call) 400s. This disables it specifically for the ollama.com endpoint while leaving it on for local Ollama and other relays.
→ src/main/claude/pi-model-resolution.ts

Tests

• src/tests/claude/pi-model-resolution.test.ts: new cases asserting requiresThinkingInContent is false for ollama.com and true for other relay endpoints.
• Full pi-model-resolution / deepseek-thinking-serialization / claude-sdk-one-shot suites pass; tsc --noEmit clean.

Verified end-to-end: a multi-turn, tool-using agent session with deepseek-v4-pro on Ollama Cloud now completes successfully.

🤖 Generated with Claude Code

[github-actions]

Review mode: initial

Findings

• [Minor] ollama.com endpoint detection could match unintended subdomains (e.g., https://xollama.com). The check endpoint.includes('ollama.com') is broad; consider using a more precise pattern like endpoint.includes('//ollama.com') or a URL hostname parse to reduce false positives.
  Suggested fix in src/main/claude/pi-model-resolution.ts:337:

  const endpointUrl = new URL(options.customBaseUrl || nextModel.baseUrl || '');
  const isOllamaCloud = endpointUrl.hostname === 'ollama.com' || endpointUrl.hostname.endsWith('.ollama.com');

Summary
No blockers or major issues found. The patch and runtime override correctly address the two serialization incompatibilities with Ollama Cloud. The detection logic for ollama.com is adequate for the known endpoints but could be tightened to avoid false matches. Test coverage is good.

Testing
Existing tests pass (vitest suites for pi-model-resolution). Not run (automation).

Open Cowork Bot