fix: Streaming stalls mid-generation with Ollama models, requires user input to resume
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the stall with an Ollama model using the listed generation settings, then trace the streaming/Ollama provider and agent loop involved in resuming after input. Done means long or multi-step responses continue generating without user intervention across the reported Ollama models.
Written by the indexing model from the issue text.
Description
Bug Description
When using Ollama models, streaming output stalls mid-generation.
The agent loop pauses and waits for user input before continuing.
Typing anything (Enter or a short message) causes generation to resume.
Expected behaviour: streaming continues uninterrupted without user intervention.
Steps to Reproduce
1. Run kit with any Ollama model (tested: ollama/gemma4:latest, ollama/qwen3:14b)
2. Ask a question that produces a long or multi-step response
3. Observe output stops mid-generation
4. Type anything and press Enter — generation resumes
Relevant Code / Configuration
temperature: 0.6
top-k: 20
top-p: 0.95
max-tokens: 8192
thinking-level: "off"
max-steps: 50
Affected Component
Streaming / Ollama provider
Kit Version
dev (go install github.com/mark3labs/kit@latest, built 2026-05-25)
Additional Context
Ollama version: 0.30.6
Hardware: Apple M4 Mac mini
No keepalive or poll-interval flags available in kit --help.
Issue occurs consistently across multiple sessions and models.
Checklist
- I've searched existing issues and this hasn't been reported yet
- I've tested with the latest version of Kit
- Dominant language
- Go
- Stars
- 134
- Forks
- 24
- Avg merge
- 8h 59m
- Merged PRs (30d)
- 23
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mark3labs/kit
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100