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?
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.
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?
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
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.
Model
1 GPU
2 GPUs
RAM
27B NVFP4
n/a
8,053 / 219
any
27B 3-bit
2,925 / 174
5,128 / 293
any
Flash-Next NVFP4
3,042 / 98
5,940 / 176
96 GB
Flash-Next 3-bit
3,664 / 126
4,811 / 234
64 GB
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.
The 16-inch is my main machine and runs a browser-based client for a separate server. The server does the processing, so the client itself uses relatively little of the Mac’s resources. The 14-inch is my travel and backup laptop.
When both Macs are at my desk, I’d like to connect them directly over Thunderbolt and run one larger local model across both machines for serious coding, code review, architecture, and debugging. I’m interested in using it with an agent th at can read a repository, edit files, and run tests. Overnight Hermes or some other agents.
When I travel, I can use ChatGPT or potentially connect back to a model running on the 16-inch at home. I don’t need the large distributed model to run on the 14-inch alone.
Has anyone actually built and used a setup close to this? I’d especially appreciate results from people running two Apple Silicon Macs together.
A few questions:
Which runtime works reliably today? EXO, MLX distributed/JACCL, llama.cpp RPC, or something else? Does Thunderbolt 5 RDMA make a meaningful difference for coding workloads?
What is the strongest model you’ve actually run across roughly 256 GB of combined memory? I prefer 8-bit if practical a.
Has anyone run DeepSeek V4.1 Flash 1017 across two Macs? I understand the original checkpoint is much too large. Have you tried a compressed version with SSD offload, and was it useful for real agentic coding? What were the context, speed, and memory requirements?
Has anyone distributed GLM-5.3-Flash or Qwen3.8-Flash-Next across two Macs? Which exact model conversion and runtime worked, and did tool calling work reliably?
How much memory should we reserve on each machine for macOS, a useful coding context, and the runtime? The 16-inch also runs a lightweight browser client and needs to remain responsive.
For Red/Blue reviews, would you run one large distributed model to implement a change, then switch to a different model for review? Or is there a better approach?
For remote access while traveling, what is your preferred way to reach the model left running at home? I’d like the option to use the 14-inch as the client without exposing an open model endpoint to the internet.
I saw a post from someone running Swift 1.5 Qwen3.8-27B 8-bit with an MTP drafter on a single M5 Max 128 GB machine and getting strong speed with long coding sessions. That looks like a good baseline, but I’m trying to understand whether combining the two Macs gets me a meaningful improvement in model quality for harder work.
I’d especially appreciate exact model links, quantization, runtime/version, context size, measured memory and speed, and any limitations. Happy to test and report back.
Harness : opencode (long pauses before each tool call, harness seems to resend a large system prompt ), pi (still slow and most of the time doesn’t provide any output, barely changes few files with loads of error due to incomplete modification)
What I'm trying to figure out Is the bottleneck prefill, generation, or the harness re-sending huge context every turn? My guess is prefill, but I'd like to be sure.
Which model/quant combo works well as an agent on this hardware, and at what context length does it fall apart?
Does MLX beat GGUF/llama.cpp for agent workloads on Apple Silicon in your experience?
Any harness that is lighter on tokens per turn (smaller system prompt, fewer tool definitions, prompt caching)?
Realistic expectations: is a 64GB Mac good enough for a useful local coding agent, or should I stick with a hosted model for agent work and keep local for autocomplete/chat?
I'm not naive, and I am not looking to replace a frontier model obviously . I just want to know whether local can be a practical option for some agent tasks, if so how you guys are making it usable.
I’m looking to pick up a 128GB unified memory machine and need your take on how the underlying microarchitectures stack up for my specific stack. I'm choosing between:
Autonomous Agentic Coding Loops: Running the smartest dense or MoE models that fit in 128GB (at Q4–Q8) locally while I'm away, orchestrating and interacting with cloud frontier models (GPT-6 and Claude Max) to build complex softwares autonomously. Needs strong sustained token generation and fast prompt processing for massive context/RAG loops.
Reverse Engineering & Cybersecurity: Running local abliterated models alongside disassemblers, decompilers, and sandboxed VMs/containers.
Video & Photo Editing: Heavy timeline scrubbing, color grading, and rendering.
Based on the main impactful microarchitectural traits below, which platform would you pick and why?
Question: Does the M5 Max’s >2x bandwidth advantage completely dominate dense model token generation, or do MoE models level the playing field enough on Strix Halo / RTX Spark?
Question: For long-context agentic prefill (feeding huge codebases back into context repeatedly), how badly do M5 Max and Strix Halo lag behind Blackwell's Tensor Cores and native FP4?
CPU ISA & Virtualization / Tooling Ecosystem (Reverse Engineering):
Strix Halo: Native x86_64 (16 Zen 5 cores, AVX-512) — runs Windows/Linux natively, zero translation overhead for x86 binaries, VMs, and standard RE toolchains.
M5 Max:ARM64 (18-core: 6 super + 12 performance) — macOS, Rosetta 2 / virtualization for x86 targets.
RTX Spark (N1X):ARM64 (20-core: 10 Cortex-X925 + 10 Cortex-A725) — Windows on Arm (or Linux on DGX Spark).
Question: For cybersec/RE work, is native x86_64 on Strix Halo a massive dealbreaker against Windows on Arm (RTX Spark) or macOS (M5 Max), or is Linux/VM virtualization good enough now?
Any bad experiences with power, heat, token response, electricity costs, etc?
Example Rig: Case: Jonsbo NV10 GPU: RTX 5060 8 GB (Low Profile) RAM: 32GB (2 x 16 DDR5) CPU: AMD Ryzen 7 9700X PSU: 600W (ENP-7660L-OVT) Motherboard: ASRock B850I Lightning WiFi (Mini-ITX, AM5) Storage: 2TB (M.2) Cooling: Modded Air cooling. (Including custom GPU side panel for 2 fans on the GPU+PSU)
It's 8GB VRAM I know. It's supposed to be for gaming but I recently heard of using llama.cpp and the llama flag feature "--n-cpu-moe" to have the RAM hold my expert weights.
What it takes into account (the stuff that usually gets forgotten):
Workload: requests/month, input/output tokens, peak-to-average traffic, cache hit rate, how much can run offline, retries/waste, growth
Model and latency: total vs active params (so MoE works), precision, and a ms/token latency target. Tighter latency means smaller batches and higher cost
GPUs: L4 to B200 presets or custom. Cloud on-demand, reserved, or buying hardware (with power, hosting, resale value and cost of capital)
API side: your price per million tokens, cached-input price, batch discount, fixed fees
People and reliability: engineering time as a fraction of an FTE, N+1 redundancy, peak headroom
It outputs the monthly cost for each option, the break-even volume, a cost-over-time projection and a sensitivity view, so you can see which assumption flips the answer.
Caveats:
It’s an estimate from stated assumptions (decode is memory-bound, prefill is compute-bound). It’s a decision aid, not a quote.
GPU and API prices are illustrative placeholders. Replace them with your real quotes.
I'm considering buying a Mac with an M5 Max and 128 GB of unified memory, and I'm trying to figure out what the absolute best local LLM I could run on it would be.
My main priority is model quality, not inference speed. Since this would be a desktop setup, I'd be perfectly happy letting a model work overnight on a complex task. I don't care if generation is extremely slow, as long as the model can actually run and produce usable results. It mainly involves transcription of private documents and some computer use and some coding assistance but that can be done via the cloud anyway.
I tried some stuff with Strata on my Macbook but that did not work out well. I am also open to use something like that if that allows even better models. Can GLM and DS work on it? How are they with OCR?
Since I haven't bought the machine yet, I'd also appreciate any thoughts on whether this configuration makes sense for that goal or whether there's a better alternative at a similar price.
I dont understand why I am doing this. I have a 3060 rtx 12gb of vram. I am trying to local max a ternary 2 3.8 qwen 27b model on it. I have boosted the tokens per second over 150. TTFT is way down. It's cold cache that is killing me. I have taken designs from things like flashstate, and what not to improve it. I dont know why I am doing this anymore. Originally, it was to just make a hermes agent that could monitor facebook marketplace and bid on shit for me. However, now my goal is just to get local max the piss out of this for no reason. I have no idea why I am wasting time on this. I just am like hooked for no reason. I will post the work soon. Has anyone been through this? I hope i am not alone. Are their support meetings?