PulseAugur
EN
LIVE 04:02:00

Ollama API fails to retain conversation history with previous_response_id

By PulseAugur Editorial · [2 sources] ·

Ollama's API for handling conversational responses has a bug where it fails to retain conversation history when the `previous_response_id` parameter is used. Instead of continuing the dialogue, the API treats each request with this parameter as a new, isolated interaction, costing the same number of tokens as a fresh start but yielding incorrect or unrelated responses. This issue affects both local and potentially hosted models, leading to plausible but wrong answers or empty outputs when tool calls are involved, making it difficult to detect as the API does not return an error. AI

IMPACT This bug in Ollama's API prevents proper conversation history management, potentially leading to incorrect responses and hindering the development of reliable AI agents that rely on context.

RANK_REASON The cluster describes a bug in an API endpoint for a specific tool, Ollama, which impacts its conversational capabilities.

Read on Mastodon — sigmoid.social →

AI-generated summary · Google Gemini · from 2 sources. How we write summaries →

Ollama API fails to retain conversation history with previous_response_id

How we ranked this

Signal score
25 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
The cluster describes a bug in an API endpoint for a specific tool, Ollama, which impacts its conversational capabilities.
Source corroboration
2 independent sources
Multiple independent publishers reporting the same story raises confidence that it's real and newsworthy.
Topics
product, other
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [2]

  1. Mastodon — sigmoid.social TIER_1 English(EN) · [email protected] ·

    TL;DR: send previous_response_id to Ollama's /v1/responses and it is accepted, the reply is HTTP 200... # ollama # llm # ai # devops # software # coding # devel

    TL;DR: send previous_response_id to Ollama's /v1/responses and it is accepted, the reply is HTTP 200... # ollama # llm # ai # devops # software # coding # development # engineering # inclusive # community Ollama's Responses API accepts previous_response_id, returns 200, and forge…

    LINKS dev.to/…/ollamas-responses-api-accepts-pr…
  2. dev.to — LLM tag TIER_1 English(EN) · The Homelab Postmortem ·

    Ollama's Responses API accepts previous_response_id, returns 200, and forgets the whole conversation

    <p><strong>TL;DR</strong>: send <code>previous_response_id</code> to Ollama's <code>/v1/responses</code> and it is accepted, the reply is HTTP 200 with <code>"status": "completed"</code> and <code>"error": null</code>, and the model has never seen the previous turn. A request tha…

RELATED ENTITIES

RELATED TOPICS