Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Bug: long running agent tasks in Ollama leads to unexpected stop tokens before tool calls

Ouverte
  • Quelque chose ne va pas ?
#672 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
74/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
clojure, ollama
Domaine
ai, backend

Piste de recherche

Start in src/eca/llm_providers/ollama.clj and read normalize-messages, comparing its message handling with the Anthropic adapter’s merge-adjacent-assistants. Check how request JSON keys are encoded and how assistant history items become Ollama chat messages. Done means prior tool calls are sent with the expected key and consecutive assistant content and tool calls are grouped as described; the issue names no test file, so locate the relevant provider tests.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

Describe the bug

When using the Ollama API and long running agent tasks, the models (tested on qwen 3.5/3.8) emit unexpected stop tokens where a tool call is expected.

To Reproduce

Steps to reproduce the behavior:

  1. Use a model hosted by Ollama with the Ollama Api
  2. Start a long running task
  3. At some point the model outputs: Now I edit file X <stop_token>

Expected behavior

The model emits a tool call request instead of the stop token.

Cause and fix

The reason for the behavior is twofold. Both problems are in normalize-messages in src/eca/llm_providers/ollama.clj.

  1. Previous tool calls are silently dropped. The assistant tool-call messages are built with the key :tool-calls, and the body is encoded with a plain (json/generate-string body) (no key-fn), so the wire key is "tool-calls". Ollama's /api/chat expects tool_calls (API docs) and silently ignores unknown fields, so the request succeeds but the model never sees its earlier tool calls. (The response side already reads :tool_calls correctly.)

  2. One model response is sent as several assistant turns. Each history item becomes its own message: the reasoning (as plain content), the visible text, and the tool call. Ollama renders every assistant message as its own finished turn. The model's history therefore contains many turns of the form "I'll do X now", followed by an end-of-turn marker. That never happened during generation, where the call followed in the same turn. The model imitates the pattern and ends its turn right after announcing the action, so the stop token becomes likely. Each failure also adds another such example, which is why it gets worse in long sessions.

Fix

  • Use :tool_calls instead of :tool-calls.
  • Merge consecutive assistant messages into one (reasoning first, then text, joined by a blank line, with all tool calls concatenated). A tool message between two responses keeps them separate. The Anthropic adapter already does this with merge-adjacent-assistants.

Workaround until released

Pointing the provider at Ollama with "api": "anthropic" avoids the problem, because that adapter already merges messages and sends tool_use blocks (Ollama converts them to tool_calls).

Langage dominant
Clojure
Étoiles
1k
Forks
82
Merge moyen
2 j 1 h
PR mergées (30 j)
23

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de editor-code-assistant/eca

Toutes les issues de editor-code-assistant/eca

Issues similaires

Plus d'issues Clojure

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.