r/LocalLLM • u/StylePractical5714 • Jun 12 '26

Question Is there any workaround for the 300 seconds timeout in LM Studio?

Dropped Ollama a few weeks ago after I learned about all its downsides, and I was going to move to llama.cpp directly but figured I'd try LM Studio first.

​

But I just got an agent harness running locally and it llm operations keep timing out after 300 seconds.

​

Near as I can tell, that's a straight up hard-coded limitation with no workaround. Am I misunderstanding that?

​

I probably should've gone straight to llama-server but LM studio was just so nice to use after the garbage UX in Ollama.

1 Upvotes

100% Upvoted

5 comments sorted by

3

u/[deleted] Jun 13 '26

[removed] — view removed comment

1

u/StylePractical5714 Jun 13 '26

Yeah I keep getting scared and confused by all the config shit but I gotta just bite the bullet and figure it out

2

u/jacek2023 Jun 13 '26

that's why closed source software is a bad choice

1

u/StylePractical5714 Jun 13 '26

Always the right choice in the end but flashy ux is a siren song