LM Studio users seek ZIP analysis

LM Studio already covers a lot of the local-AI stack, but this post shows how quickly users run into tooling limits when they try to treat a local chat UI like a full code-analysis agent.

• –LM Studio’s official docs position it as a local LLM app for chat, model serving, MCP, and offline document RAG
• –The docs explicitly describe document attachments for `.docx`, `.pdf`, and `.txt`, not ZIP archives or repo ingestion as a first-class workflow
• –For developer use cases, the missing piece is usually not raw model access but automation around unpacking files, traversing projects, and feeding the right context into the model
• –That makes this a good snapshot of where local AI still lags cloud assistants: privacy is there, but convenience and repo-aware workflows still need extra setup