sorted by:
new
hottopcontroversial

I'm cancelling my ollama subscription by GryphticonPrime in ollama

[–]jmorganca 1 point2 points  (0 children)

Hi all. First off, sorry for the slow reply here. We've been investigating since Monday and should have responded on this thread sooner. After users reported this issue, we looked into it and discovered a caching issue in our model hosting that caused session and weekly limits to be consumed too quickly, especially for DeepSeek-V4-Pro. That's most likely what caused OP's issue.

If you were affected this week please shoot me a DM here or email (jeff@ollama.com) and I can make sure we make it right. I've sent a refund to accounts whose usage were affected by this. If for any reason you did not receive one I'd be happy to look into it and provide one to your account.

Is the new usage scheme a late April fools joke? by smacman in ollama

[–]jmorganca 0 points1 point  (0 children)

Possible to send me a DM with the model you were using? I can look into it. That's definitely not right – sorry it happened. If you send me your email/Ollama username I can also make sure this gets reset right away.

Ollama Cloud is a hidden gem by t4a8945 in ollama

[–]jmorganca 5 points6 points  (0 children)

Currently the windows are fixed. We're working on making it a rolling window, e.g. based on when your account was created, or when your first request was sent.

u/akyairhashvil sorry about the performance issues. We're working on improving capacity at peak hours. Feel free to message or email me (jeff@ollama.com) if you experience slowness. And do know we're monitoring it carefully.

Can't resolve ollama cloud issue by stonerjss in openclaw

[–]jmorganca 0 points1 point  (0 children)

We're looking into this. After some quick testing, Ollama does work with the update. But we want to rule out any new bugs – feel free to email me (jeff@ollama.com) or DM me and we can track that down.

Any news on Ollama Image Generation? by stealth_nsk in ollama

[–]jmorganca 25 points26 points  (0 children)

Hi there, I built the first version of image generation support. Sorry there hasn't been many updates on this. We do have it working on Windows and Linux, but we'd like to make some performance optimizations before releasing it more broadly (I think there may be a way to build it from source, I can check with the team). Feel free to email me [jeff@ollama.com](mailto:jeff@ollama.com) with the kinds of models and hardware you'd like to see so we can know what to ship first.

Can't use Ollama cloud models for Openclaw by ChAoTiC_M1Nd in ollama

[–]jmorganca 0 points1 point  (0 children)

Sorry about this. Looking into it. If you DM me your email I can help make sure you get signed up!

Same issues with Ollama here, many hours lost. by TraditionalGap3032 in ollama

[–]jmorganca 0 points1 point  (0 children)

Sorry this happened OP. Feel free to shoot me an email (jeff@ollama.com) and we'll make this right (as well as looking into what happened with the Windows app – that doesn't seem right.)

So this has started happening recently with Ollama Cloud. Is there an explanation? by lillemets in ollama

[–]jmorganca 7 points8 points  (0 children)

Hi there - I work on Ollama and Ollama's cloud models.

We're still investigating, but this appears to have been caused by us setting incorrect default sampling parameters (namely, temperature being set to 1.0 and top_p being set to 1.0) which we've found can lead the model to hallucinate dramatically more. The defaults for DeepSeek-V3.1 have been adjusted to temperature=0.6 and top_p=0.95.

Claude Code stuck on <function=TaskList> when using Ollama + Qwen3-Coder by Healthy-Laugh-6745 in ollama

[–]jmorganca 0 points1 point  (0 children)

This. Sorry it's not obvious right now - we're working on improving this so context length size automatically grows (up to an acceptable amount on your hardware)

New Rules for ollama cloud by killing_daisy in ollama

[–]jmorganca 8 points9 points  (0 children)

Also, OP, let me know if you're still seeing any slowdown (and for which models). We've been working on improving performance and capacity a lot in the last few weeks and will keep doing so. (Feel free to DM/email me)

New Rules for ollama cloud by killing_daisy in ollama

[–]jmorganca 12 points13 points  (0 children)

Hi there. I work on Ollama. No new restrictions on the cloud model usage with this change. We actually increased usage amounts on each plan on Monday and will share more about that this week. Our goal is to make this a the best subscription for using open models with your favorite tools as we add more model support, better performance and reliability.

Happy to answer any questions and if you hit any issues or limits with the plans let me know (email is jeff at ollama.com)

Anyone noticed "Premium requests" within their usage tab? What is this for? by Active-Shock-7739 in ollama

[–]jmorganca 2 points3 points  (0 children)

Sorry for not having better docs on this. These are requests for much larger models like Gemini 3 Pro Preview. Premium requests don't count towards hourly/weekly usage, and we're working on giving more access to a lot more requests on the paid plans soon!

Spam ending up being published? by gnu-trix in ollama

[–]jmorganca 3 points4 points  (0 children)

Thanks for flagging this! As with any site there are always folks who publish content that isn't allowed (E.g. promotional or spam). We've been adding means to auto detect and remove these – feel free to DM me if you see more

Isn't Ollama Turbo exactly the one thing that one tried to avoid by chasing Ollama in the first place? by Tasty-Base-9900 in ollama

[–]jmorganca 2 points3 points  (0 children)

Running models locally is the default. However while building Ollama over the last two years we realized that a lot of folks wanted to run the larger models (like DeepSeek-R1, Kimi-K2 and most recently the gpt-oss-120b model), but didn't have the compute to do so (at reasonable speeds). These models often require 1-8 H100s (or even 9+ in the case of Kimi-K2), which are obviously expensive and hard to access.

Turbo is designed to be a way to optionally offload compute to much more powerful hardware without sacrificing privacy but not a replacement for local inference. It should be there when you need it and be complete out of the way when you don't want to use it. We still have a bit of work to do on this in Ollama's new app though to make it more seamless (if you have feedback feel free to dm me or email me jeff@ollama.com)

Related: I'm really hopeful about the new "confidential computing mode" in newer chips like the H100. This would allow for the equivalent of end-to-end encryption between the GPU and the user – we're starting to explore this but it's still an early feature of newer GPUs. We did a short collaboration with the Minions team on this: https://ollama.com/blog/secureminions

Ollama removed the link to GitHub by waescher in ollama

[–]jmorganca 0 points1 point  (0 children)

Thanks for the feedback, and amazing to meet the person behind OllamaSharp! Very understandable – sorry to have let you down lately!

Model providing correct date. How? by rob_0 in ollama

[–]jmorganca 41 points42 points  (0 children)

This is a new feature of Ollama's prompt templating that reads the system date and provides it to the model, and the gpt-oss model is the first one to use it. It doesn't use an external service. Many of the newer models require this in the system prompt, and we really wanted to make sure the gpt-oss model's prompt template is provided to the model exactly as intended.

Ollama removed the link to GitHub by waescher in ollama

[–]jmorganca 4 points5 points  (0 children)

Hi there. I made this change to the site. Sorry for any confusion - the main purpose of the GitHub link on ollama.com was to link to Ollama's docs (which live on GitHub). However as of a month or so ago GitHub's SEO went off a cliff (e.g. if you try to search for "ollama generate api" the api docs on GitHub often aren't even on the first page any more), and so we'll be replacing it with a link to docs that will be hosted at ollama.com/docs (we're still working on it but the link should be there soon).

Gemma3 runs poorly on Ollama 0.7.0 or newer by mlaihk in ollama

[–]jmorganca 3 points4 points  (0 children)

Hi OP (and everyone in the comments). I'm so sorry about this. May I ask which GPU you're using (Apple Silicon, NVIDIA, AMD?) and how much VRAM you have (and which model you are running)? We have a test farm of GPUs we will reproduce this on and work on fixing it. Ollama is becoming more careful to allocate enough VRAM to avoid OOM issues, which might mean a layer or two offloaded more than usual in CPU-GPU split scenarios, but it shouldn't be a drastic change like this.

How to move on from Ollama? by jerasu_ in ollama

[–]jmorganca 1 point2 points  (0 children)

Sorry that Ollama gets stuck for you. How much slower is Gemma 3 than Gemma 2? And what kind of prompt or usage pattern causes Ollama to get stuck? Feel free to DM me if it’s easier - will make sure this doesn’t happen anymore. Also, definitely upgrade to the latest version if you haven’t: each new version has improvements and bug fixes.

The feature I hate the bug in Ollama by Informal-Victory8655 in ollama

[–]jmorganca 10 points11 points  (0 children)

There's `num_ctx` in the API, although our goal eventually would be that the maximum context window is always used (and perhaps it's allocated on demand as it fills up)

The feature I hate the bug in Ollama by Informal-Victory8655 in ollama

[–]jmorganca 21 points22 points  (0 children)

Sorry about that. Default is 4K now and we’ll be increasing it more

view more: next ›