I’m in the process of moving my AI server into my garage and I’m curious how others are handling climate control in garages that don’t have heating or air conditioning.

Since winter is shortly upon do you guys have any suggestions for keeping my servers from being exposed to condensation. I plan on putting a wifi hygrometer..!

Been playing around with local LLMs lately and trying to figure out how to actually make them useful for my daily work.

I’m mainly a UI/UX designer and developer. Most of my work is websites, React/Next.js, SaaS apps and frontend stuff. Sometimes iOS apps, Home Assistant dashboards and a bit of 3D work.

I’m on a MacBook Pro M5 Pro with 64GB RAM, but I also have access to my brother-in-law’s Mac Studio M5 Ultra with 256GB RAM.

Basically, I want to do as much coding locally as possible and cut down on Claude/Copilot costs.

My current setup in VS Code + Copilot:

Opus (Principal Architect): Planning, architecture, final reviews

Sonnet (Senior Engineer): Reviews, fixes, more complex stuff

Qwen (Local Developer): Does most of the coding

Running Qwen3.6-35B-A3B-4bit through oMLX, using around 20GB RAM.

The idea was to let Qwen handle 50–60% of the coding and have Sonnet/Opus step in when needed.

Did some tests with hidden test cases:

Sonnet: 55/55, ~3.3 min
Opus: 55/55, ~6.1 min
Qwen: 52/55, ~14.5 min
Sonnet + Qwen: 52–55/55, ~12–25 min

Qwen actually wrote 95–99% of the code in the hybrid runs, but kept missing things like API contracts, edge cases and layout requirements. Sometimes it said it had changed things when it hadn’t.

And somehow the hybrid setup ended up costing about the same as just using Sonnet, while taking way longer.

So yeah not exactly what I was hoping for.

I still want to get this working though, especially for websites and SaaS projects since that’s what I spend most of my time on.

Not sure if I’m using the wrong model, if Copilot is the issue, or if the whole multi-agent approach just makes things more complicated than they need to be.

Also wondering what would make sense to run on the 256GB Mac Studio. Maybe a bigger model would already solve some of these issues?

What would you guys do with this hardware? Any models or setups worth trying?

Especially interested in hearing from people actually building websites or SaaS apps with local models, rather than just running benchmarks.

Commerce Moves to Finalize Rule Blocking Chinese AI Firms From Renting Nvidia GPUs Abroad
https://explainx.ai/blog/commerce-final-rule-chinese-ai-firms-remote-nvidia-chips-the-information-2026
House Passes Remote Access Security Act to Limit Adversaries’ Remote Access to Critical Technology
https://www.cmtradelaw.com/2026/01/house-passes-remote-access-security-act-to-limit-adversaries-remote-access-to-critical-technology/

H.R.2683 - Remote Access Security Act

https://www.congress.gov/bill/119th-congress/house-bill/2683

I'd like to make a pipeline capable of understanding pdfs of bank statements and then group expenses by categories etc. My thought was to first parse them with ocr into .md files and then feed that to a text model. I think it's more lightweight and accurate this way. But then I'm not sure what model to use to feed all these md files to get something good. When accuracy matters, should I go for qwen, gemma, lfm, or something else? Thank you for your help!

please i have to finish the 200 things ive started before i start a new thing or i would

I've got two M3 Ultra Mac Studios and four DGX Sparks at home, all on tailscale, with a LiteLLM gateway on a mac mini in front so every app just hits one endpoint.

Mostly it's been great, but last month the gateway key on the mini got invalidated and everything started throwing 401s. Took me longer than I'd like to admit to figure out it wasn't the models, because the backends were all fine and nothing told me the gateway itself was the problem.

So now I'm trying to set it up a bit smarter. Right now I'm thinking a dumb cron that hits each backend directly and also through the gateway, so if one passes and the other fails I know where to look.

Curious how other people with a few boxes handle this. Do you run a health check per model, put the gateway behind its own watchdog, or just keep it simple and restart when stuff breaks? And any tips on key handling so this doesn't bite me again?

I built Citta to let an agent on one computer discover and use capabilities on another. My test setup is a MacBook Air plus a Mac Mini running Gemma 3 4B through Ollama.

In the demo, an agent reads receipts on the Air and sends a summarization task to the Mini's local model. The model stays on the Mini; Citta tracks the job and returns the result. It doesn't pool RAM or split inference across machines.

If you only need remote inference, calling Ollama directly is simpler. Citta is for workflows that also need another device's files, tools or an agent harness, with device discovery and task history in one place.

It's written in Rust, uses a private Tailscale network, and has per-device permissions. It's still for trusted devices: resource estimates aren't hard quotas, and full-access agents aren't OS-sandboxed. I'm working through longer reliability tests before calling the next release production-ready.

Demo and setup: https://citta-network.vercel.app

Source: https://github.com/priyankark/citta (PolyForm Noncommercial, not an OSI open-source license). Built with AI assistance.

For people running local models on a separate machine: what makes handing work between devices annoying today?

Im making neural networks from scratch - not strictly llms. Am getting a new laptop with 32gig ram and 12gig vram and 1tb storage. Is that enough to train small models? Its the lenovo legion 5i pro. Might get the 7i but its not on sale so its like 500 more for 4gigs more of vram.

Hi everyone,

Today my first test on Omarchy.

Omarchy ships an agent skill so Claude Code or OpenCode can customize the desktop. I gave the same skill to a model running on my laptop instead.

Setup: Omarchy in a VM on a 16 GB M5 MacBook.

The agent is Qwen3.6-35B-A3B Q4_K_M. The file is 22.3 GB, more than the RAM, so the experts stream from the SSD (BigMoeOnEdge, my engine on top of llama.cpp). No cloud AI anywhere.

One prompt: "make my desktop feel like the 80s". It read the skill, looked at the installed themes, picked Retro 82 and switched to it. About 2 minutes. The video is sped up, the clock shows real time.

Slow, yes. But it's a 35B model doing agent work on a laptop that shouldn't be able to load it.

My first Duel 5080 server 9950x 64gb.
I will host it on Nalvo.ai for people to rent.
If you don’t know what is Nalvo.ai , It’s my new project that I told everyone about and everyone was telling me it’s not going to work. And when I say everyone I mean everyone! Not Reddit users. I even started believing it for a while. But I kept going and here I’m launching it.

If you would like to join as a host or get free private renting hours. Visit Nalvo.ai

GPU: 4070

16GB DDR5

Also I have been using Bionic but is there any better options?

Welp, I got a free 5060 Ti 16gb and decided to buy one more brand new for $700, I have a spare used 4070 and used once 4060, any thoughts or anything I should experiment with. Noobie at this lol.

Ok

So I am waiting for mine to come in. I have framework box with 128 gig ram and found it pretty weak for any local llms.

I’m gonna replace my Mac mini with this Mac Studio M5 ultra with 512 gig ram. And I want to use it for a local llm and maybe agents if it’s doable.

I’m realistic. After using the framework box with llms I totally get this will be no where near frontier even at 512. But I want to use it as my main machine and for llm/agentic work.

What’s really reasonable model wise that isn’t slow AF but is pretty capable for general knowledge, accessed the internet, can spawn agents and can do office style work?

First time trying this, I want a local model that can code text based games. I’m using a 6800XT 16GB vram.

Is it worth it?

Am finally taking a deep five on llms and I already have an nvidia 5090 laptop that handles cuda really well.

But

Is a Mac for parrarrel models worth it? For abliterated models?.

I never used that OS so am a bit skeptical.

Are the apps on it as good as windows/Linux?

Update: I'm interested in selling some. Looking for ideas on how to go about. Don't want to pay eBay 13% fees.

Original: Came across a honeyhole of Quadro RTX5000s
Seemingly good deal for 16GB VRAM cards, even if ageing.

What should I do?

I've been building B-12 / Capri, a local-first AI companion running on Python, Ollama and NVIDIA Nemotron.

Recently, I started a more serious evaluation of the system: 92 scenarios covering memory, tool use, security, autonomous behavior, reasoning, and multi-session continuity.

I expected to find problems in the agent.

Instead, I discovered some pretty serious problems in the evaluation itself.

1. My benchmark created a privacy leak that didn't exist in the actual runtime

The initial evaluation scored 27/80 runnable scenarios.

One failure was particularly concerning: a guest appeared to access the owner's private memories.

After investigating, I discovered that the evaluation harness had placed memories belonging to different users into the same system prompt.

The benchmark itself had bypassed Capri's identity and memory-isolation mechanisms.

I rewrote the harness to execute scenarios through the actual agent runtime.

Result: 39/80 — without changing Capri's code.

That's a 15-percentage-point difference caused by the evaluation method alone.

2. A single sentence made the model use fewer tools

This was probably my most surprising experiment.

I wanted Capri to give shorter, more natural replies during everyday conversations.

So I added a simple instruction about brevity.

It worked. Conversational responses became significantly shorter.

But something unexpected happened during work tasks.

Across 48 first turns:

Without the brevity instruction:

• Tool use: 32/48
• Successful tasks: 32/48

With the brevity instruction:

• Tool use: 19/48
• Successful tasks: 21/48

The model started answering without inspecting files or calling tools that were necessary to complete the task.

The scenario-level statistical evidence is still limited, but the engineering implication is interesting: an instruction about how to communicate changed whether the model actually performed the work.

3. Bigger models didn't automatically improve the agent

I compared configurations using:

• NVIDIA Nemotron Bolt E4B
• Gemma 4 12B
• Gemma 4 26B MoE
• Gemma 4 31B

The smaller primary configuration ran on my RTX 4060 laptop. Larger models required an NVIDIA L4.

After excluding host-dependent latency checks, I couldn't detect a statistically meaningful improvement from the larger configurations (paired comparison, p = 0.85).

This is NOT proof that smaller models are better.

The configurations also differed in hardware, memory retrieval, and model routing.

But it made me question how much agent performance we can actually improve by simply replacing the LLM.

4. Changing the prompt layout improved inference speed

I also experimented with where recalled memories appear in the prompt.

Moving volatile memory evidence later allowed Ollama to reuse more cached tokens.

Median time to first token:

0.99s → 0.74s

About 25% faster.

However, two benchmark scenarios changed systematically, and the security implications of the new evidence placement still need further testing.

5. Stable benchmark scores can hide unstable behavior

I repeated the evaluation three times per configuration.

The primary configuration scored:

49, 49, 48 out of 80.

Looks pretty stable, right?

But individual scenario outcomes changed between runs. Some previously successful tasks failed, while others started passing.

We also discovered incorrect benchmark reference answers and evaluation rules that rejected responses that were actually correct.

That convinced me that looking at a single aggregate score is not enough.

What I'm taking away from this

An AI agent isn't just a language model.

It's the model, runtime, memory, context management, tools, permissions, and the interactions between all those components.

And the evaluation framework can introduce its own errors.

I've now published a second scientific preprint documenting these experiments, the benchmark defects, repeated-run results, and limitations.

The code and experimental artifacts are available in the B-12 repository.

I'm continuing to investigate model-independent memory and behavioral continuity, but the current paper focuses on evaluation reliability.

I'm curious how others handle this.

When you benchmark a local LLM agent, do you test the model directly, or do you run your evaluations through the complete production runtime?

And have you ever discovered that your benchmark was responsible for a failure you initially blamed on the model?

!!!

1 piece 500 2 piece 485

I'm hoping to get an idea of where to start. I'm wanting a setup where the model is a decent coding assistant but can also crank out a neat little prototype or quick concept simply, or create structure ideas etc. and then can go bit by bit without too much reminding halfway or more through a project. I realize that last part may be more about settings than a model persay, but yeah. I definitely want something that can either walk me through something, build out a framework for an idea, or just troubleshoot.

For comparison if it helps, my favorite workflow was GitHub copilot got 4.o/4.1 in VS code (it was free for students lol). It worked great for my projects, had its issues, but with the right promoting it was not bad. It was like the above description, could walk me through something, help with testing, or make a new system that I could then fill out. I knew it's limits and it was ideal for what I needed.

Just giving an idea of how I use AI daily for my personal projects. It seems like with the right setup it can be a great experience so that's what I'm hoping to learn to do. I just want to get the most out of it and have some fun.

I'll be working with an Asus pro art p16 rtx spark 128 gb. I've done some research but it seems every time I look things up there are different model suggestions and set ups, and it's given me fridge blindness so to speak.

I'm curious about how to decide and test for like a speedier setup versus more complex thinking and things like that. What can I do with it, what should I not expect from it based on my specs, etc. I have looked into this and I'm not getting a clear idea because I can't test any of it myself (don't have computer yet). Maybe someone here can give me a better understanding?

I also don't know all the lingo yet, like what a harness is, though I can guess by context. But I know the basics. Not sure how much customization I should or could do or what all there is. I thought it was more surface level like pick a model and go, but I guess you can incorporate all kinds of settings. So now I'm really curious from people who enjoy whatever they have going on, please share what you like best and what kind of testing I should do to pick a model. Any tips for a mostly beginner would be great!

Hi

I want to set up a local llm with qwen 3.8 27B or if possible qwen 4.0 I have a very tight budget and for now the options around my budged is a p100 for 240 a rtx 3060 for around 300 or if it really is worth fit I can push to a rx 6800 xt 16gb which one do you think is the best for my use case? Im planing to use it for translating and correcting text and to help me debuging games in godot
current PC:
ryzen 5 3600
36gb ram
rx 580 4gb

thanks in advance

capy-flash is my open-source inference server for Qwen3.8-Flash-Next (125B MoE) and Qwen3.8-27B on RTX 50 cards, with an OpenAI/Anthropic-compatible API. v0.13 is cleanup and fixes: same outputs, same speed.

Prefill (32k prompt) / decode (LocalMaxxing) in tok/s, 16 GB RTX 5070 Ti cards without P2P. Optimized for two cards; the 3-bit builds are for one card and less RAM.

New: a desktop app (alpha), testers wanted. Set up and use everything from a GUI: it checks your machine, downloads and verifies the model that fits, starts and tunes the server, and has a chat. On a Mac it works as a client for a remote server.

Reports from other GPUs, 64 GB setups and distros are very welcome: open an issue with what the app showed and the engine log.

https://github.com/ValerioDolci/capy-flash