Pinned Tweet
Got into running AI models on my own hardware, testing, building agents, and sharing what actually works. Follow for daily insights, hardware tips, and no-BS tech talk (+ an additional rant from time to time).
Here's a video of local AI folks going to Qwen4 immediately after release.
Qwen just leaked a 120B model that can see, hear and think...
"qwen4-omni-120b-think" showed up in the test files of Qwen's own code, along with a 1M token context window for Qwen4
and that's on top of the lineup we're reportedly getting:
> Qwen4-Max
> Qwen4-Plus
> Qwen4-Flash
> Qwen4-27B
Qwen's Omni models handle text, images, audio and video all in one model, so a 120B one with reasoning would be huge
Alibaba Cloud's CTO reportedly said "next week" on stage last Wednesday, so this could all drop any day
Qwen4-27B is going on my 3090 the second it does
also I found a video of us all migrating to Qwen4-27B:
The next big battle in AI model development will be who can their hands on as much private, proprietary data as possible.
That will allow models to gain capabilities which their competitors can't touch.
If you enjoyed the preview, here's the real deal!
👋Hy4 is here, new with vision.
Firmly among the leading open models.
More productive everywhere: finance, frontend, game, officework, research…
Built responsibly, with cyber/biosecurity in mind.
Try it out and let us know!
🔗:hy.tencent.ai/research/hy4?l…
People will download a 210GB game without blinking, then call a local AI model "too big."
My daily driver is about 119GB and it actually does work for me.
You have the disk. You have the RAM and probably a GPU. You just haven't tried yet.
Revolut moved its engineers to open-weight GLM models running on GPUs it rents itself, at about a tenth of the cost and with no usage caps.
Frontier models are now just for edge cases.
The banks figured out what us local AI bros already knew😂
BREAKING: Revolut moved ~2,000 engineers onto self-hosted GLM for coding and pushed Claude Code and Codex to the exception list.
Per David Abitbol, who leads AI ops there: 56 Nvidia B200s, a blended 30 cents per million tokens, roughly a tenth of what they paid Anthropic and OpenAI. Engineering lead time improved 70%.
Here's the part that matters: the gains showed up when tokens stopped being rationed. Engineers quit saving AI for the hard tickets and pointed it at everything.
Frontier models become the exception, open weights become the default. That's a pricing problem for every lab heading to IPO.
h/t @OliverMolander
Would you move your team off frontier APIs if the bill dropped 90%?
Claude Duet is still a US-only waitlist.
The open-source version, Open Duet, already runs a team of agents with memory, a lead agent splitting the work, and asking before it acts, all on your hardware.
Works with Ollama or whatever you choose and you can put it to work tonight!
Read this one carefully: 1,035 tok/s is the TOTAL across 64 sessions. One chat gets ~127.
Both matter if you run agents at home:
- single speed = how fast one agent thinks
- batched speed = how many agents one GPU can feed
I've got only two sharing one Qwen 27B, so many to go!
A single RTX 3090 is reportedly pushing 1,035 tokens/s of aggregate throughput while serving 64 concurrent Qwen3.8-27B sessions.
The interesting part? This is a 24GB GPU running with a 250W power limit.
No multi-GPU setup. No expensive inference accelerators. Just one RTX 3090, vLLM and an open-source project called HyperQwen.
The reported configuration
• GPU: NVIDIA RTX 3090 (24GB VRAM)
• Power limit: 250W
• Model: Qwen3.8-27B
• Inference engine: vLLM
• Single-session generation: Approximately 127 tokens/s
• 64 concurrent sessions: Approximately 1,035 tokens/s combined
• Longest tested context: Up to 150K tokens
There are two numbers worth paying attention to.
The 127 tokens/s figure represents generation speed for a single session.
The 1,035 tokens/s figure is the combined output across 64 simultaneous sessions.
In other words, one conversation is not receiving 1,035 tokens every second. The server is distributing available GPU resources across multiple requests and accumulating the output from all of them.
That distinction changes how we should look at this result.
Local inference is also about serving multiple users
Most local LLM benchmarks focus on one question: How quickly can my GPU generate a response?
But developers building AI applications have another problem to solve.
What happens when several agents and applications need the same model at once?
Imagine one machine running:
• A coding agent modifying a repository.
• A research agent gathering information.
• A document assistant processing files.
• A code reviewer checking generated changes.
• Other applications sending requests to the same model.
Running a separate model instance for every application would be wasteful.
A shared inference server allows these applications to connect to one endpoint and use the same model infrastructure.
That’s the area HyperQwen is exploring.
Why more concurrent sessions increase throughput
A GPU serving one request may have processing capacity that isn’t fully utilised throughout generation.
With multiple requests arriving, vLLM can schedule their execution together through continuous batching.
Instead of treating every conversation as an isolated workload, the server combines work from multiple requests to keep the GPU busier.
Efficient KV-cache management also helps the system handle concurrent sessions without wasting as much memory on attention state.
There is a trade-off, though.
Higher aggregate throughput doesn’t automatically mean faster responses for each individual user. As more sessions compete for compute and memory, per-session generation speed and latency can change.
The objective is to increase the total amount of work the server completes, not necessarily make every conversation faster.
Getting started
HyperQwen provides two Docker Compose profiles:
Single-session mode
docker compose --profile single
Batch mode
docker compose --profile batch
The initial setup also requires some preparation. The first launch reportedly downloads around 9.5GB of Docker images, followed by a local model requantisation process involving approximately 20GB of data.
That initial work needs to finish before running the inference benchmarks.
Project: HyperQwen
GitHub: syv-ai/HyperQwen
Why this matters for developers
GPU specifications alone don’t tell us how useful a machine will be for running AI applications.
Single-session generation speed measures how quickly one user receives tokens. Aggregate throughput measures how much output the server can deliver across multiple users and applications.
Both are important, but they describe different aspects of inference performance.
HyperQwen’s reported results show what can be achieved by optimising the serving stack around a relatively affordable, widely available GPU.
For developers building local AI services, shared inference environments or multi-agent systems, this is worth exploring.
Big step forward in personal manufacturing.
Every time Bambu Lab release something, you know it's gonna` be good!
Bambu Lab H3C launches today.
Nine independent PrintTools™ that allow multiple nozzle sizes in a single print.
Powered by SwapTek™, Print-to-print tool switch only takes 6 seconds.
Multiple toolheads with multiple possibilities. Print, cut, draw and deboss. All on the same machine.
We built this machine. Now we want to see what you make with it.
--------------------------
To celebrate the launch, we're sending one H3C Combo to a maker ready for it.
How to enter:
• Follow @BambulabGlobal
• Like + Repost with: "Bambu Lab H3C. Tool Changer. Game Changer!"
• Comment: Which H3C feature impressed you the most?
Winner revealed: Nov 6, 4AM EST
Explore the H3C: share.bambulab.com/4yoyNdz
I keep telling you Hermes Agent is getting better and better. Every improvement means more ways for you and I to work and get stuff done!
Been focusing on the Desktop app this last week or two.
This PR should be welcome news to a lot of you power users.
On next full release later this week I think you'll start noticing the difference in the desktop app getting noticeably nicer.
Still a long way to go, but we'll get there. Lots of UX and design work coming shortly.
Let me get this straight, there is a vulnerability which allows an attacker to takeover a Linux server at any time if the server is exposed to the Internet, and Ubuntu and Red Hat haven't shipped a fix yet?
Interesting times ahead!
What a disaster atlasum.net/blog/cve-2026-98…
If RAM and GPUs weren't enough, next on the list of hard to find fairy dust items will be CPUs soon.
Intel is shifting production away from regular PC CPUs and putting more focus on server chips because AI demand is going crazy.
Intel is struggling to keep up with demand.
>AI companies are getting priority.
>There could be fewer CPUs available for desktop and laptop PCs.
>Prices could increase if supply gets tighter.
>Intel expects new factories and production capacity to help from late 2027.
Intel CEO Lip-Bu Tan described it as one of the most significant supply shortages in the company’s history.
Don't say you AI agent can't be funny. A good SOUL.md file will spice is up a little.
You do know what the SOUL.md file is, right?
Before you trust a "fast local AI" screenshot, ask:
Same model, or are experts being dropped?
What quant?
What context length? Cause this is monumentally important.
Prefill or decode speed?
Speed is easy, quality at speed is a bit more difficult.
Anthropic's blueprint for self-improving agents: memory + "dreaming" over past sessions.
Your own home version tonight:
- log every agent run
- let a local model review failures at night
- save fixes to a notes file it reads next run
Still local, but still smart and private.
OpenAI's first hardware: a $230 keyboard with 13 keys for Codex.
Price seems steep TBH.
You could find a macro keyboard elsewhere and give it to Codex to integrate it.
Or maybe build it, don't buy it, it could be a fun weekend project!
🚨 OPENAI JUST ENTERED THE HARDWARE RACE WITH A $230 AI KEYBOARD!
Sam Altman surprised approximately 50 Samsung executives with OpenAI's first branded hardware product, the Codex Micro Keyboard.
Here's what makes it different:
• Just 13 mechanical keys
• Rotary dial adjusts AI reasoning depth
• Joystick controls coding tasks
• LED lights display AI agent activity
• Voice commands replace traditional typing
• Price: $230, already sold out
THE BIGGER STORY:
OpenAI is moving beyond chatbots into hardware designed specifically for AI agents.
Altman's message to Samsung executives was clear:
Simply adopting AI won't create a lasting competitive advantage. Companies must use it to build better products and move faster.
For $AAPL, $MSFT, $GOOGL and Samsung investors, this raises an important question:
Could AI agents eventually replace traditional software interfaces?
THE NEXT COMPUTING REVOLUTION:
From typing commands to delegating tasks.
From using software to supervising AI.
The next trillion-dollar opportunity may be how humans interact with machines.
Follow @TMA_MarketIntel for AI, technology and market intelligence.
Folks running a 35B Qwen MoE on an 8GB RTX 4060 laptop at 38 tok/s.
MoE + good quants changed the "need a $10K rig" story.
What's the biggest model you've squeezed onto the smallest GPU?
I started my AI journey with a Ryzen 6900HX with the integrated Radeon 680M GPU.
Go try!
Sam Altman says the RAM in your PC sits mostly idle and belongs in datacenters.
Prove him wrong, get a 3060 and the RAM you have and go ahead an run local Qwen3.8 Flash Next or 27B.
Run an AI agent on top of that, let it do tasks for you.
Don't just doomscroll, build something!
Does the EU produce COB LEDs? NO
Does the EU produce small BMS boards? NO
Does the EU produce LED connectors? NO
But damn EU wants me to pay 30.69 Euro on a 36.68 order on Aliexpress.
My projects double in price because the damn EU taxes you into oblivion.
A bunch of THIEVES!
There is no way people are building things in these conditions.
This just favors sitting around and doing nothing, which is why almost all the countries in the EU are heading for collapse.
And then you look at VW which will probably go under, taking a whole area of Germany with it, and you quickly understand why this can't go on like this if we don't want to become like Venezuela or something.



















