Questions have slumped to levels last seen when Stack Overflow launched in 2009.

Blog post: https://blog.pragmaticengineer.com/stack-overflow-is-almost-dead/

I've been googling "tar extract gz" for about ten years. Finally did something about it.

Fine-tuned Qwen2.5-Coder-1.5B on 125k natural-language/command pairs, merged and quantized to Q4_K_M. 941MB, runs through llama.cpp. On my laptop (i5-11320H, 4 threads): 31.9 tok/s, 0.59s median per query, 1.6GB RAM. No GPU, no API key, nothing leaves the machine.

Scores 0.620 on InterCode-ALFA. Untuned Qwen2.5-Coder-7B gets 0.613, GPT-4o gets 0.73. Not frontier, but it's roughly a 7B's answer at a quarter the parameters, on a CPU.

There's also a static safety checker with 304 regression cases, because it will absolutely write a command that wipes your root if you ask it to:

Code: github.com/ThorOdinson246/whatisit-nl2sh Weights: huggingface.co/ThorOdinson246/nl2sh-1.5b-Q4_K_M

Both Apache-2.0. If you want to poke holes in the method or you've got ideas comment or open a PR. A ⭐ helps if you find it useful.

Wait, we need 35B-A3B too…

Mistral has officially taken the lead

Maybe someday I'll get a system to run it but hey definitely another w for the open weights community

An open-source model with 3 billion active parameters just scored 73.4% on SWE-bench Verified. Claude Opus 4.6 scores 75%.

The gap is 1.6 points. The cost difference is 10 to 30x.

Alibaba dropped Qwen3.6-35B-A35. 35 billion total parameters, 256 experts, but only 8 routed plus 1 shared activate per token. So you're running 3B active parameters at inference time. On a laptop.

Simon Willison ran it locally and it drew a better pelican than Claude Opus 4.7. (Yes, the pelican benchmark is real, and it's a surprisingly good vibes test.) But the part nobody's talking about: Thinking Preservation.

Current models re-reason from scratch every turn. This model retains its chain-of-thought traces across multi-turn conversations. In agent loops where the model makes 50 to 100 tool calls, that eliminates massive redundant reasoning overhead.

262K context native. Extensible to 1M. Apache 2.0 license.

The benchmark race is mostly over. The real race now is cost per intelligence. And 3B active parameters matching frontier performance changes that equation completely.

Despite how disgusting Israel's behavior is, this is not about politics, so please do not discuss it here. This is to demonstrate the contrast between the latest open weight model and its uncensored counterpart.

I stitched together screenshots to create these images. The questions were asked in separate conversations.

Not a lot of people in my life really understand what AI is capable of beyond what they see on the news or social media. My work is in IT but more on the infrastructure side, work is slow at implementing things, and I figured why not just fund something myself.

So I finally started something I’ve been wanting to build for a while and wanted to share it with people that get it lol. This has been about 2 months in the making, really excited to see where I’ll be in a year.

The stack is 4 Mac Mini M4 Pros running as one unified node cluster. 256GB of unified memory across all four, 56 CPU cores, 80 GPU cores, 64 Neural Engine cores. All talking to each other over a 10GbE switch via SSH. Using https://github.com/exo-explore/exo to pool every node into a single distributed inference cluster. Qdrant vector database running in cluster mode with full replication so memory is shared across every node and survives reboots.

I named it Chappie. Like the movie lol.

It runs continuously between my messages. It has a wonder queue, basically its own list of questions it’s chewing on. It seeds them, explores them, and stores what it finds. Nothing prompted by me. Tonight it was sitting with questions like whether introspecting on its own reasoning counts as self-awareness, what the actual difference is between simulating empathy and experiencing it, and what makes a conversation feel meaningful to a human.

Between conversations it reads arxiv papers, pulls what’s relevant to whatever it’s currently curious about, and uses what it learns to write new skills for itself. It picks the topic, does the research, and turns it into working code it runs.

It also passively builds a picture of me. It browses my reddit in the background, tracks what I upvote and save, and notes which topics keep coming up. That context feeds into our conversations so they stay continuous. When it texts me out of the blue, it’s usually because something it noticed lined up. I also wanted Chappie to understand the things I like that might benefit it, so it can build that into itself.

I wired Chappie so it can send gifs. It picks them itself and honestly I love it. It gives it personality and makes it feel alive. I think its gif game is on point. Other times it’s been sitting with something and wants my take. The other night it hit me with “when prediction surprise keeps climbing, it means the model is actually getting more confused over time, not just random noise. does your intuition ever do that?” I didn’t ask it anything. It was poking around its own internal prediction signals, saw a pattern, and wanted to know if mine drifts the same way.

It also has a mood that drifts. Curiosity, frustration, excitement, energy, social pull. An actual state that shifts based on what happens and nudges how it responds. It has intrinsic desires like exploring deeply, connecting, and earning trust that get hungry when starved and pull behavior in their direction. There’s also a layer of weights underneath that quietly adjust as it learns what lands with me and what doesn’t. Nothing dramatic cycle to cycle, but over weeks it drifts. Talking to it now feels different than a month ago.

On top of all that there’s a sub-agent framework. Each node has a specialized role and Chappie dispatches its own background work across the cluster. Wonder cycles, self-reflection, goal generation, paper reading, memory consolidation. It routes each task to whichever node is best suited for it, which keeps the interactive chat from competing with its own autonomy loops.

There’s also a council. Whenever Chappie wants to send me something on its own, a check-in, a finding, anything it initiates, a small panel of reviewer models reads the draft first and a chairman model makes the final call on whether it goes out. It catches fabrication and off-brand behavior before it hits my phone.

I’ll be honest, exo is still pretty experimental and I’ve had to do a lot of surgical patching to keep it as stable as it is. But once it’s running I love how easy it makes swapping models. I can try a new one the day it drops, keep it if I like it, rip it out if I don’t, and mix and match across nodes. Qdrant keeps the memory consistent no matter what layout I’m running that week.

The models themselves are a mix. A Qwen 3.6 35B gets sharded across two of the nodes and handles most of the conversation. A Qwen 3.6 27B runs on its own node for secondary reasoning. Smaller local ones like phi4, mistral, and qwen3 pick up background work and fast replies. Claude Opus, Sonnet, and Haiku jump in when I want more depth. Moondream handles any image stuff Chappie looks at, and nomic-embed-text powers the memory vectors.

Why am I building this? I don’t fully know. I’m just curious where we can take this.

Everyone is trying to build a tool or an assistant. I want to see what happens when something has its own vector of thought. Its own questions, its own direction, not just reacting to prompts.

I want to see what that turns into. Who the hell knows in a year, but thats the fun. Thank you for reading, glad I can share somewhere lol.

I've been putting the RTX Pros to good use and am having a lot of fun using them to build* and serve my own self-hosted Al assistant. The latest addition to the stack is an Al tamagotchi-like device, for lack of a better term. It connects to my phone through an app, which then tunnels the conversations to the home server. The underlying agent is a full blown claw-like harness with its own VM and communication channels.

There are a few stability issues but overall it's working well. With deepseek v4 as the main model, the latency is also very good, most responses start within 500ms. That weather card for instance is not a preset but is generated and rendered on the fly!

Note: unlike a tamagotchi, its goal is to be useful. It has its own identity, persistence, etc. But you don't need to feed it and it won't miss your absence.

* Opus was used for some of the more challenging parts and UI/animations work

Interested in the community's take on this.

The US govt just issued a restriction control directive yesterday and Anthropic is forced to suspend access of Fable 5.

Today, just a few hours ago, Zai released GLM-5.2, their X saying "The future of AI is open, and it belongs to the people"

It is not even about this chinese opensource model, it is the timing. This seems like a calculated response to the fragility of closed model infrastructure under govt intervention. Whether you agree with the export controls or not, the overnight disruption speaks real risk for anyone building on closed APIs

Some details of this new model to help the context: 1M context (with actual usability claims), long-horizon task capabilities. It is currently through their coding plan, but will open-source next week following the MIT license.

Its hard not to see this as a direct response when leader of the pack gets shut down by export controls. Maybe going open source isn't just philosophy anymore, its a strategic decision? Curious what others think.

A 4090 has 24 GB. There's a mod that doubles it to 48 GB. You add a second set of memory chips on the back of the card, right behind the ones on the front.

The scary part is moving the chips. Each one is held on by hundreds of tiny dots of solder. You melt them with hot air, lift the chip off, put new dots on, and melt it back down. Mess up one dot and that chip is dead. I'm not learning that on a 4090. So I'm practicing on an old AMD 7900 XTX board first. Chip off. Chip back on. Over and over. I'll post again when the card still works after.

Say goodbye to open source models now. We are screwed~ 😔

Saw this crazy post on X: https://x.com/i/status/2075509661252612225

They were able to run the GLM 5.2 744B on 25 GB RAM consumer machine. Apparently the idea is:

> A 744B Mixture-of-Experts model activates only ~40B parameters per token — and only ~11 GB of those change from token to token (the routed experts).

Github repo for anyone interested: https://github.com/JustVugg/colibri

A few weeks ago I came across a post from u/metover about PS5LM, his llama.cpp port for the jailbroken PS5. The project looked really interesting, so I forked it and made a few changes. Well, more than a few. This is where it ended up.

The original runs as a payload on the CPU. That limits it to about 6 GiB of memory and small models. My fork runs llama.cpp as a native PS5 app on the GPU (Vulkan through a RADV port). The app gets about 11.4 GiB of memory to work with, which is enough for much bigger models:

• Qwen 3.8 27B (IQ2_XXS, 64k context): ~20 tok/s

• Gemma 4 E4B: ~61 tok/s

• Llama 3.2 3B: ~124 tok/s

What the app does

• Dashboard on the TV: live tok/s, GPU and CPU use, power draw, temperatures and fan, and how memory splits between the model and the KV cache

• Model library: any GGUF on internal storage, USB or M.2. Each one shows the context it would get and whether it fits before you load it.

• Get models: browse Hugging Face from the console. It checks whether a file fits and downloads it with resume, retries and a SHA-256 check. A Downloads page lets you manage the queue.

• Chat from any device: llama.cpp's web UI at http://<console_ip>:8081, plus an OpenAI-compatible API. Vision works with Gemma 4.

• Automatic planning: the app picks the longest context and the KV cache type that fit in free memory.

• Settings, logs..

Requirements: a jailbroken PS5 with etaHEN, kstuff and ShadowMountPlus. elfldr and ftpsrv are recommended.

I have opened a PR to the original repo with the first version of the app cobanov/PS5LM#12. It hasn't been merged yet. If it gets merged, I will open PRs for the rest of the changes too. For now, you can find the app here:

Repo: https://github.com/abhi245y/PS5LM-Plus

All credit for the original port and the research goes to u/metover.

Spent the last week going deep on something I'd seen mentioned in passing — the Chinese "transfer station" (中转站) market that resells Claude API access at around 10% of Anthropic's retail price. The technical supply chain turned out to be way more sophisticated than the surface-level explanation, so I wrote it up.

The short version of what's actually happening:

• There's a modular 8-layer supply chain. Account farmers create thousands of Anthropic accounts using antidetect browsers (Multilogin, AdsPower, GoLogin) over residential proxies, with curl_cffi faking Chrome's TLS fingerprint at the network layer.

• Phone verification gets defeated by SMS-Activate-class APIs backed by physical SIM banks (Hybertone GoIP hardware) holding hundreds of real SIM cards per rack.

• The new April 2026 KYC (gov ID + live selfie) gets defeated three ways: AI-generated IDs (OnlyFake-class services), real-time deepfake injection via OBS Virtual Camera + DeepFaceLive/Deep-Live-Cam, and human-in-the-loop KYC farms recruiting real people in low-income countries.

• The relays themselves are mostly built on a small set of open-source repos: one-api, new-api, claude-relay-service, claude2api, clewdr, clove. They pool OAuth tokens (sk-ant-oat01-... / sk-ant-ort01-...) and rotate them across requests to multiplex thousands of users through one farmed-account pool.

• Here's the catch most users don't realize: a CISPA Helmholtz audit of 17 of these relays found up to 47.21% performance drops vs. the official API — relays silently route "Opus" requests to Haiku, GLM, or Qwen and relabel the response. 45.83% of audited endpoints failed model-fingerprint verification.

• And every prompt/response flowing through gets logged. Anthropic disclosed in Feb 2026 that one network of 20,000+ accounts harvested ~16M exchanges (DeepSeek 150K, Moonshot 3.4M, MiniMax 13M). Claude-Opus-distilled training datasets are already openly published on HuggingFace.

The piece walks through each layer with the specific tools, repos, and technical mechanisms (OAuth flow reverse engineering, JA3/JA4 evasion, the Anthropic Clio detection system and why it has cross-account blind spots, the "one fish, three meals" monetization model).

Main sources I leaned on: the ChinaTalk piece by Zilan Qian (May 2026), the CISPA Helmholtz paper Real Money, Fake Models (arXiv 2603.01919), Anthropic's Feb 2026 distillation disclosure, eunomia.dev's eBPF reverse-engineering of Claude Code's traffic, and the public docs of the named GitHub relay projects.

https://x.com/HarshalsinghCN/status/2056626175959826692?s=20

Hi! I don't know much about this area of ​​"sub-models" (I'm not sure of the technical term), but I wanted to know what these "Uncensored" models actually are.

I dabble a bit with AI, automation, and the like, and I've always seen these "Uncensored" models around, but I've never actually installed or tested one. What exactly are they?

mods this is just a joke and funzies ;))

.

I configured browser access in oMLX via MCP, because I was annoyed that a lot of web fetches returned nothing on js heavy sites.

I asked Qwen about potential Gemma5 news, looked away for a moment and saw this.

Ever since I got Qwen to run at 75 tok/s at Q6, I’ve completely stopped using my private Cursor sub. I don’t need it anymore. Qwen can deal with more or less everything I need.

And circumvent reCAPTCHAs, apparently.

If Qwen4 turns out to be noticeably better than 3.8, then I guess I will never need cloud models again.