Local AI Setup: LM Studio & Hermes Agent on Windows PC

Local AI Setup: LM Studio & Hermes Agent on Windows PCLocal AI Setup: LM Studio & Hermes Agent on Windows PC

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Lucas Leyes

• Jul 2

Set up a private, local AI environment (LM Studio + Hermes Agent Desktop) on a client's Windows PC — no cloud dependency, no data leaving their machine. 😊

Completed work

AI Agent Designer AI Automation AI Writing Ollama

Aavirash Mitra

pro

• Jul 5

This is my submission or the RivexContra Character Challenge! AI Agents are on the rise, and I always found it to be the best opportunity for interactive character experiences - So I built just that - A fully functional Avatar Builder and Selector with 5 fully designed, animated and interactive Characters embedded in a realistic AI Agent!

UI Design AI Agent Designer Rive Animation Rive characterchallenge characteranimation interactivedesign Mascot Design

Hanna Girsule

• Jul 5

Amazing!

Nivyan Butt

pro

• Jul 5

Would you let an AI write SQL against your production database?

I wouldn't either. So when I built Quanta — a workspace where you ask questions in plain English and get back a live dashboard — the model never touches your data directly.

Every query it generates is SELECT-only and runs read-only. If one fails, the system feeds the exact database error back to the model and lets it correct itself once before anything reaches you. Credentials stay encrypted with AES-256-GCM and never leave the vault.

Connect Postgres or MySQL, switch between Gemini, Claude, and GPT, and build dashboards from 12 chart types. It's multi-tenant now too. Orgs, roles, and per-workspace AI spend caps.

Curious how other devs handle the "LLM + real database" problem. What guardrail would you add?

Abdullah B

• Jul 5

The self-correction loop is such a smart touch. Only thing I'd add is a statement_timeout + forced LIMIT so a valid-but-heavy query can't tank prod. Ideally run against a read replica. Great build.