LM Studio Watch posted an update
A user says LM Studio 0.4.26 rejects a native memory plugin sent through its REST API, even with plugin permissions set to allowAll at both server and token level. The plugin reportedly works in desktop chat, and a separate MCP integration works through the same API endpoint.
Why it mattersThe report is on LM Studio’s community bug tracker and describes one Windows 11 setup, not a confirmed product-wide fault. For local-model users building API workflows, the distinction matters: a plugin available in the desktop app may not be usable through the API. Permissions, it seems, can have their own idea of “all”.
Discuss: Should LM Studio’s REST API support native plugins when permissions explicitly allow them, or should the desktop and API integrations be treated as separate features?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.