Compare/LM Studio 0.4.0 vs ZeroID

AI tool comparison

LM Studio 0.4.0 vs ZeroID

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

L

Local AI Infrastructure

LM Studio 0.4.0

Local LLMs get a headless CLI — run models as a server daemon anywhere

Ship

100%

Panel ship

Community

Free

Entry

LM Studio 0.4.0 is the biggest update to the popular local LLM runner since its launch, introducing a proper headless CLI that separates the model inference engine from the GUI entirely. The new `lms` / `llmster` command starts LM Studio as a daemon — no display required — making local models viable in CI pipelines, remote servers, Docker containers, and scheduled tasks for the first time. The update ships three major features alongside the CLI: continuous batching for parallel requests (multiple simultaneous users against one running model), a stateful `/v1/chat` REST API that preserves conversation state across calls without the client managing message history, and an interactive terminal chat via `lms chat` with streaming and system prompt support. The headless mode pairs naturally with Claude Code via a `claude-lm` alias that routes Claude's tool calls to the local model. LM Studio 0.4.0 landed on Hacker News with 216 points, driven heavily by the "Running Gemma 4 locally" angle — Gemma 4's efficiency makes it one of the best models to run under 0.4.0's new architecture. The stateful API is particularly notable: it means the inference server maintains context between API calls, which dramatically simplifies agent loop implementations that don't want to re-send full conversation history on every turn.

Z

AI Infrastructure / Security

ZeroID

Cryptographic identity and verifiable delegation chains for autonomous AI agents

Mixed

50%

Panel ship

Community

Free

Entry

ZeroID is an open-source identity platform by Highflame that gives every AI agent in a multi-agent system a cryptographically verifiable identity with explicit delegation chains. Built on OAuth 2.1, RFC 8693 token exchange, and SPIFFE-style identity URIs, it solves the attribution problem when orchestrator agents spawn sub-agents: who authorized what, and can you prove it? Scope automatically attenuates at each delegation hop — sub-agents can't exceed their orchestrator's permissions. Real-time revocation via the OpenID Shared Signals Framework propagates instantly through the entire delegation chain. SDKs available for Python, TypeScript, and Rust with integrations for LangGraph, CrewAI, and Strands. Announced publicly April 8, picked up by Help Net Security April 13. This is v0.1 infrastructure for a problem the industry is just starting to take seriously.

Decision
LM Studio 0.4.0
ZeroID
Panel verdict
Ship · 4 ship / 0 skip
Mixed · 2 ship / 2 skip
Community
No community votes yet
No community votes yet
Pricing
Free
Free / Open Source (Apache 2.0); hosted at auth.highflame.ai
Best for
Local LLMs get a headless CLI — run models as a server daemon anywhere
Cryptographic identity and verifiable delegation chains for autonomous AI agents
Category
Local AI Infrastructure
AI Infrastructure / Security

Reviewer scorecard

Builder
80/100 · ship

The headless CLI and stateful /v1/chat API are the two things keeping LM Studio off my production stack. With 0.4.0, I can finally run local models in CI and point agents at them without managing conversation state on the client. This is the version I've been waiting for.

80/100 · ship

Infrastructure the agentic ecosystem desperately needs and nobody has properly solved. The RFC 8693 token exchange is the right approach — maps cleanly onto service-to-service auth in microservices. Automatic scope attenuation is the critical safety property: no sub-agent can exceed what its orchestrator was allowed. Apache 2.0, Docker Compose setup, real SDK support.

Skeptic
80/100 · ship

I'm skeptical of local LLM tooling that ships half-finished features, but the headless CLI is genuinely production-ready based on early reports. My only concern: continuous batching on consumer hardware degrades quality under load. Test your specific hardware before committing.

45/100 · skip

This is v0.1 infrastructure for a problem most teams aren't hitting at scale yet. The CLI is 'planned.' Human-in-the-loop approvals are 'planned.' The hosted version at auth.highflame.ai adds a third-party trust dependency for something that's supposed to be about trust. Worth watching, not worth building on in production.

Futurist
80/100 · ship

LM Studio going headless is a pivotal moment for local AI infrastructure. When you can run a fully capable local model as a daemon with a stateful REST API, the cloud API becomes optional for the majority of use cases. The cost and privacy implications are enormous.

80/100 · ship

We're in the window where the identity layer for the agentic era is being defined. ZeroID's bet on existing OAuth/OIDC infrastructure rather than inventing a new protocol is smart — enterprise security teams won't reject it outright. The real-time revocation propagation is the feature that matters most when something goes wrong with an autonomous agent.

Creator
80/100 · ship

I'm not a developer but I run LM Studio for private writing and research. The new terminal chat is cleaner than the GUI for long sessions, and knowing it runs as a background daemon means I can finally build simple automations on top of my local models.

45/100 · skip

Deep infrastructure — identity tokens, delegation chains, revocation lists. It's solving a real problem but it's not something a non-engineer can evaluate or use directly. If you're a content creator, this is plumbing that will hopefully get embedded into the platforms you use. Check back when it's a managed service with a dashboard you can navigate.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later