@warlock.js/ai-ollama 5.34.2 → 5.34.3

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to `@warlock.js/ai-ollama` are documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). `@warlock.js/*` packages are released in lockstep — every package shares the same version number, so a version below may list only the changes that affected this package.
 
+## 5.34.3 - 2026-10-20
+
+### Changed
+
+- The agent skill now exports as `warlock-js-ai-ollama`; package discovery descriptions stay within 450 characters.
+
 ## 5.34.2 - 2026-10-19
 
 ### Fixed

package/llms-full.txt

@@ -4,24 +4,11 @@
 
 > Generated artifact. Concatenates every SKILL.md and reference file under `@warlock.js/ai-ollama/skills/`. Re-run `node scripts/generate-llms.mjs` after any change.
 
-## Package orientation
+## ai-ollama  `@warlock.js/ai-ollama/skills/SKILL.md`
 
 ---
-description: "Provider adapter for local and self-hosted Ollama servers in Warlock AI applications. Exports `OllamaSDK` with model and provider configuration for the shared AI contracts. Use when connecting this provider, configuring host and headers, reasoning, embeddings and daemon errors, or diagnosing provider requests and usage. Read `setup-ollama` for construction and examples using an Ollama host. Not this package: agent loops, tools and workflows → @warlock.js/ai; HTTP and MCP tools → @warlock.js/ai-tools."
----
-
-# @warlock.js/ai-ollama
-
-This adapter supplies provider-backed models for `@warlock.js/ai`. Read `setup-ollama.md` to construct `OllamaSDK`, configure host and headers, reasoning, embeddings and daemon errors, and understand provider-specific behavior.
-
-For agent composition, read the `run-ai-agent` topic of the `@warlock.js/ai` package. Keep provider configuration here and application orchestration in that package.
-
-
-## setup-ollama  `@warlock.js/ai-ollama/setup-ollama/SKILL.md`
-
----
-name: setup-ollama
-description: 'Wire @warlock.js/ai-ollama — new OllamaSDK({host?, headers?}) for local / self-hosted Ollama via the official ollama client (not OpenAI-compat). chat + embed, daemon-down error handling. .model({name, vision?, reasoning?}) with cost-truth capabilities — reasoning inferred from thinking-model tags (deepseek-r1/qwq/qwen3/gpt-oss…), promptCaching/audio/pdf honestly false; options.reasoning → Ollama native `think` flag; usage reasoningTokens/cachedTokens stay undefined (none reported). Triggers: `providerOptions`, `OllamaCallOptions`, `countTokens`, `OllamaSDK`, `ollama.model`, `ollama.embedder`, `embedder.embedMany`, `ollama.count`, `host`, `headers`, `reasoning`, `think`, thinking models, `streamChunks`, `message.thinking`, `deepseek-r1`, `qwq`, `qwen3`, `gpt-oss`; "use ollama with warlock", "run llama3 locally", "self-hosted llama", "ollama reasoning / thinking models", "deepseek-r1 with warlock"; typical import `import { OllamaSDK } from "@warlock.js/ai-ollama"`. Skip: agent loop — the `run-ai-agent` topic of the `warlock-js-ai` skill; provider choice — the `pick-ai-provider` topic of the `warlock-js-ai` skill; embeddings core — the `embed-text` topic of the `warlock-js-ai` skill; siblings `@warlock.js/ai-openai`, `@warlock.js/ai-anthropic`, `@warlock.js/ai-google`; raw `ollama` npm, Vercel `@ai-sdk/ollama`; OpenAI-compat gateway via `@warlock.js/ai-openai` `baseURL`.'
+name: warlock-js-ai-ollama
+description: 'Local Ollama models for Warlock AI: `OllamaSDK`, `OllamaCallOptions`, `OllamaModelConfig` and `OllamaEmbedderConfig`. Use for "run a local LLM", "connect Ollama", pull model tags, stream chat, use tools, configure thinking or generate embeddings through `model()` and `embedder()`. Not this package → @warlock.js/ai for agents and RAG; @warlock.js/ai-openai for hosted OpenAI-compatible servers.'
 ---
 
 # `@warlock.js/ai-ollama`

package/llms.txt

@@ -6,5 +6,4 @@
 
 ## Skills
 
-- [Package orientation](@warlock.js/ai-ollama/skills/index.md): Provider adapter for local and self-hosted Ollama servers in Warlock AI applications. Exports `OllamaSDK` with model and provider configuration for the shared AI contracts. Use when connecting this provider, configuring host and headers, reasoning, embeddings and daemon errors, or diagnosing provider requests and usage. Read `setup-ollama` for construction and examples using an Ollama host. Not this package: agent loops, tools and workflows → @warlock.js/ai; HTTP and MCP tools → @warlock.js/ai-tools.
-- [setup-ollama](@warlock.js/ai-ollama/setup-ollama/SKILL.md): Wire @warlock.js/ai-ollama — new OllamaSDK({host?, headers?}) for local / self-hosted Ollama via the official ollama client (not OpenAI-compat). chat + embed, daemon-down error handling. .model({name, vision?, reasoning?}) with cost-truth capabilities — reasoning inferred from thinking-model tags (deepseek-r1/qwq/qwen3/gpt-oss…), promptCaching/audio/pdf honestly false; options.reasoning → Ollama native `think` flag; usage reasoningTokens/cachedTokens stay undefined (none reported). Triggers: `providerOptions`, `OllamaCallOptions`, `countTokens`, `OllamaSDK`, `ollama.model`, `ollama.embedder`, `embedder.embedMany`, `ollama.count`, `host`, `headers`, `reasoning`, `think`, thinking models, `streamChunks`, `message.thinking`, `deepseek-r1`, `qwq`, `qwen3`, `gpt-oss`; "use ollama with warlock", "run llama3 locally", "self-hosted llama", "ollama reasoning / thinking models", "deepseek-r1 with warlock"; typical import `import { OllamaSDK } from "@warlock.js/ai-ollama"`. Skip: agent loop — the `run-ai-agent` topic of the `warlock-js-ai` skill; provider choice — the `pick-ai-provider` topic of the `warlock-js-ai` skill; embeddings core — the `embed-text` topic of the `warlock-js-ai` skill; siblings `@warlock.js/ai-openai`, `@warlock.js/ai-anthropic`, `@warlock.js/ai-google`; raw `ollama` npm, Vercel `@ai-sdk/ollama`; OpenAI-compat gateway via `@warlock.js/ai-openai` `baseURL`.
+- [ai-ollama](@warlock.js/ai-ollama/skills/SKILL.md): Local Ollama models for Warlock AI: `OllamaSDK`, `OllamaCallOptions`, `OllamaModelConfig` and `OllamaEmbedderConfig`. Use for "run a local LLM", "connect Ollama", pull model tags, stream chat, use tools, configure thinking or generate embeddings through `model()` and `embedder()`. Not this package → @warlock.js/ai for agents and RAG; @warlock.js/ai-openai for hosted OpenAI-compatible servers.

package/package.json

@@ -14,13 +14,13 @@
     "directory": "packages/ai-ollama"
   },
   "peerDependencies": {
-    "@warlock.js/ai": "5.34.2"
+    "@warlock.js/ai": "5.34.3"
   },
   "dependencies": {
     "ollama": "^0.6.3",
-    "@warlock.js/logger": "5.34.2"
+    "@warlock.js/logger": "5.34.3"
   },
-  "version": "5.34.2",
+  "version": "5.34.3",
   "main": "./cjs/index.cjs",
   "module": "./esm/index.mjs",
   "types": "./esm/index.d.mts",

package/skills/{setup-ollama/SKILL.md → SKILL.md}

@@ -1,6 +1,6 @@
 ---
-name: setup-ollama
-description: 'Wire @warlock.js/ai-ollama — new OllamaSDK({host?, headers?}) for local / self-hosted Ollama via the official ollama client (not OpenAI-compat). chat + embed, daemon-down error handling. .model({name, vision?, reasoning?}) with cost-truth capabilities — reasoning inferred from thinking-model tags (deepseek-r1/qwq/qwen3/gpt-oss…), promptCaching/audio/pdf honestly false; options.reasoning → Ollama native `think` flag; usage reasoningTokens/cachedTokens stay undefined (none reported). Triggers: `providerOptions`, `OllamaCallOptions`, `countTokens`, `OllamaSDK`, `ollama.model`, `ollama.embedder`, `embedder.embedMany`, `ollama.count`, `host`, `headers`, `reasoning`, `think`, thinking models, `streamChunks`, `message.thinking`, `deepseek-r1`, `qwq`, `qwen3`, `gpt-oss`; "use ollama with warlock", "run llama3 locally", "self-hosted llama", "ollama reasoning / thinking models", "deepseek-r1 with warlock"; typical import `import { OllamaSDK } from "@warlock.js/ai-ollama"`. Skip: agent loop — the `run-ai-agent` topic of the `warlock-js-ai` skill; provider choice — the `pick-ai-provider` topic of the `warlock-js-ai` skill; embeddings core — the `embed-text` topic of the `warlock-js-ai` skill; siblings `@warlock.js/ai-openai`, `@warlock.js/ai-anthropic`, `@warlock.js/ai-google`; raw `ollama` npm, Vercel `@ai-sdk/ollama`; OpenAI-compat gateway via `@warlock.js/ai-openai` `baseURL`.'
+name: warlock-js-ai-ollama
+description: 'Local Ollama models for Warlock AI: `OllamaSDK`, `OllamaCallOptions`, `OllamaModelConfig` and `OllamaEmbedderConfig`. Use for "run a local LLM", "connect Ollama", pull model tags, stream chat, use tools, configure thinking or generate embeddings through `model()` and `embedder()`. Not this package → @warlock.js/ai for agents and RAG; @warlock.js/ai-openai for hosted OpenAI-compatible servers.'
 ---
 
 # `@warlock.js/ai-ollama`

package/skills/index.md

@@ -1,9 +0,0 @@
----
-description: "Provider adapter for local and self-hosted Ollama servers in Warlock AI applications. Exports `OllamaSDK` with model and provider configuration for the shared AI contracts. Use when connecting this provider, configuring host and headers, reasoning, embeddings and daemon errors, or diagnosing provider requests and usage. Read `setup-ollama` for construction and examples using an Ollama host. Not this package: agent loops, tools and workflows → @warlock.js/ai; HTTP and MCP tools → @warlock.js/ai-tools."
----
-
-# @warlock.js/ai-ollama
-
-This adapter supplies provider-backed models for `@warlock.js/ai`. Read `setup-ollama.md` to construct `OllamaSDK`, configure host and headers, reasoning, embeddings and daemon errors, and understand provider-specific behavior.
-
-For agent composition, read the `run-ai-agent` topic of the `@warlock.js/ai` package. Keep provider configuration here and application orchestration in that package.