A 40B coder that runs on a laptop, Walmart opens checkout to AI agents, and AI factories ship in containers
Three things landed within a day of each other: a small open-weight coding model that runs offline on a 48GB laptop, Walmart's decision to let approved AI agents search its inventory and buy things with spending caps, and Nvidia packing whole AI data-centre pods into shipping containers. Each one moves AI a step closer to being plumbing rather than a product — and each opens work for people who can install, govern or benchmark that plumbing.
Key takeaways
- Recursive's Flint puts strong agentic coding on a single laptop under Apache 2.0, but every headline benchmark number is the company's own.
- Walmart is the first big US retailer to publish rules and spending caps for AI shopping agents, creating a real integration surface for developers.
- Nvidia's DSX POD claims 14-day on-site deployment for Vera Rubin AI factories, but only after the customer has already prepared power, cooling and network.
Recursive open-sources Flint, a 40B coding model that runs offline on a 48GB laptop
On 21 October, London-based Recursive released Flint, a mixture-of-experts coding model with 40 billion total parameters but only about 2.5 billion active per token, under the permissive Apache 2.0 licence. Recursive says it runs at more than 125 tokens per second on an M4 Pro MacBook Pro.
Recursive published Flint on 21 October as open weights on Hugging Face under the Apache 2.0 licence, which allows commercial use without paying or asking permission. Flint is a mixture-of-experts model: the Hugging Face card lists 39.8 billion total parameters, of which roughly 2.5 billion are active for any given token. Each MoE layer holds 256 experts, and a router selects six of them per token plus one shared expert. The documented context window is 262,144 tokens shared between prompt and output, and Recursive advises staying inside 256,000 for best results. The model is text-only, and its knowledge stops in June 2026.
The point of the design is speed on small machines. Because compute scales with the 2.5 billion active parameters rather than the full 40 billion, Recursive reports more than 125 tokens per second on an M4 Pro MacBook Pro and more than 150 tokens per second on a 64GB Nvidia RTX Spark at short contexts. Four-bit builds come to roughly 23GB, and Recursive targets machines with 48GB of memory so there is headroom for a long context. The full BF16 checkpoint is about 80GB and runs on a single Nvidia B300 or H200 per replica. Flint works with Ollama, LM Studio, llama.cpp, vLLM and SGLang, and there is a free hosted endpoint on OpenRouter.
On benchmarks, Recursive reports 54.9% on Terminal-Bench 2.1, 89.7% on what it calls SWE-bench Pro v2, and 74.2% on SWE-bench Verified. The company's comparison table puts Flint ahead of other sub-50-billion-parameter MoE models — it lists Qwen 3.6 at 73.8% and Poolside's Laguna XS 2.1 at 38.6% on the same SWE-bench Pro v2 measurement. Recursive's own claim is narrower than the headline suggests: that Flint leads MoE models under 50 billion total parameters on agentic coding and 'rivals' dense models of 25 to 40 billion parameters while running more than five times faster.
Flint is also a claim about how models get built. Recursive says an internal automated research system it calls the Eureka Machine proposed ideas, ran experiments and chose next steps across data, optimisers, training recipes, infrastructure and inference, and that a small team of humans and agents built Flint from scratch in under four months. Recursive credits it with four specific findings, including settling on a 40B/2.5B-active shape, a 4-bit NVFP4 output layer that scores within 0.7 points of the 16-bit model, and a single Metal megakernel covering the whole decode step on Apple M4 and M5 chips. Humans supervised throughout and could stop the process.
The caveats are real. Every benchmark figure above is Recursive's own, averaged over at least five attempts with sampling at temperature 1.0, and 'SWE-bench Pro v2' is Recursive's own measurement, which the company says cannot be compared with the public SWE-bench Pro leaderboard. By Recursive's own table a dense Qwen 3.8 beats Flint on all three tests, and Terminal-Bench is Flint's weakest result. Recursive itself warns the model 'may need more guidance than the larger closed-source coding models'. Recursive emerged from stealth in May 2026 with more than $650 million at a $4.65 billion valuation, led by GV and Greycroft with Nvidia and AMD participating, and is run by Richard Socher and Tim Rocktäschel.
Why it mattersA permissively licensed coding model that runs offline on a high-end laptop removes both the per-token bill and the data-leaves-the-building objection that keeps many firms from using AI on their code.
👀 What to watch
Whether independent runs on the public SWE-bench Pro and Terminal-Bench leaderboards land anywhere near Recursive's numbers, and whether the free OpenRouter endpoint stays free.
3 opportunities from this story
Offline AI coding setups for firms that can't send code to the cloud
Law firms, hospitals, banks, government contractors and anyone under a strict data clause often ban cloud coding assistants outright. Flint changes the answer from 'no' to 'on this machine, with nothing leaving the building'. Sell a fixed-scope installation: pick the hardware, install the runtime and model, wire it into the team's editor, and hand over a short written note the compliance officer can file. The deliverable is a working setup plus proof that no code leaves the network.
- Best for
- Freelance developers and small IT consultancies with clients in regulated industries
- First step this week
- Install Flint with Ollama or LM Studio on one 48GB machine this week, run it against a real repository you know well, and write down the setup time, tokens per second and what it got wrong.
Open the full playbook
Launch steps
- Build and document one reference setup on hardware you own
- Write a two-page 'no data leaves your network' explainer for non-technical compliance staff
- Price three tiers: single workstation, small team server, and department rollout
- Run two free pilots with firms in your network in exchange for written feedback
- Package the result as a named service with a fixed price and a defined scope
Tools
Risks
Flint is weaker than frontier hosted models, especially on terminal tasks, so overselling it will end badly — demo on the client's real code before quoting. Hardware costs sit with the client, and open-weight models move fast, so date your recommendations and plan for a swap within months.
Independent benchmark reports for open-weight coding models
Flint's headline scores are self-reported on a benchmark variant the company measures itself, and buyers have no neutral number to compare. There is room for a small, careful testing service: run a handful of open models against a client's own codebase and tasks, measure accuracy, speed and cost on their actual hardware, and publish a short report. Doing this in public builds an audience; doing it privately for one client pays better.
- Best for
- Developers who enjoy evaluation work, technical writers, small research consultancies
- First step this week
- Pick three open coding models, run them on ten real tasks from one repository, and publish the method and results with the raw logs attached.
Open the full playbook
Launch steps
- Define a repeatable test harness and write down every setting, including temperature
- Publish one free report to establish the method
- Offer private runs against a client's own repository and hardware
- Re-run the suite each time a major open model ships
- Keep an archive so buyers can see trends over time
Tools
Risks
Benchmarking is easy to get subtly wrong, and a bad methodology will be picked apart in public — show your logs and settings. Vendors may dispute unflattering results, so stay factual and avoid grand claims.
A 'which model, which machine' buying guide service
Small teams asking whether to buy a 48GB laptop, a 64GB desktop box or rent a GPU have no good source to ask. A short paid consultation that maps their workload to concrete hardware and a specific model, with real numbers, saves them thousands and a month of trial and error. Charge for the call plus a written recommendation; the research compounds because you reuse it with every client.
- Best for
- Technical consultants, hardware resellers, developer-advocate types with a small audience
- First step this week
- Write up one honest cost comparison — a 48GB laptop running Flint versus a hosted API — using your own measured tokens per second and your local electricity price.
Open the full playbook
Launch steps
- Collect measured throughput figures for two or three model-and-machine pairs
- Build a simple spreadsheet that converts usage into monthly cost either way
- Offer the first ten calls cheaply to collect testimonials
- Turn the recurring questions into a public FAQ that feeds new enquiries
- Revisit the numbers whenever a new model or machine changes them
Tools
Risks
Hardware and model prices move monthly, so stale advice is worse than none — date every recommendation. If you take reseller margin, disclose it, or the advice stops being trusted.
Walmart opens checkout to AI shopping agents, with per-agent spending limits
On 21 October Walmart announced Agent Profiles, a Walmart Agent Gateway built on the Model Context Protocol, and a published set of rules for AI agents. Customers will be able to give an agent its own profile with a spending cap — Walmart's examples are $50, $100 and $200 — and delete it at any time.
Walmart published the announcement on 21 October. The core idea is that an AI agent gets its own identity inside a customer's Walmart account rather than borrowing the customer's. Walmart creates an Agent Profile automatically the first time an agent shops through the gateway; the customer then signs in to link it, sets a spending limit, and can delete it whenever they want. Walmart's own analogy is adding a cardholder to a credit card. Purchases made by that agent show up separately from the customer's other orders. Walmart says Agent Profiles arrive 'in the next month', which puts them around late November.
The second piece is the Walmart Agent Gateway, an interface built on the Model Context Protocol — the open standard for connecting AI models to external tools — so that agents query live product and fulfilment data instead of clicking through web pages, which Walmart calls slow and error-prone. The gateway carries verified agent identities, controlled permissions, category restrictions and rate limits. It is launching as an invitation-only beta for companies and developers at walmart.com/agents, and Walmart warns that access may be suspended and features may change. Agents can find a customer's usual items without receiving their broader purchase history.
Walmart also published rules. By default customers must approve agent purchases, and Walmart says it may require extra approval even for purchases that sit inside an agent's spending limit. Agents must not take actions beyond what the shopper intends. They do not receive payment-card information and cannot add or change a payment method. They may access only the information a task needs and the customer allows, and they must identify themselves as agents rather than pass as human. Agents that break the terms get blocked from the site. On price, Walmart's line is that agents see the same prices a person would, with offers and fees shown before purchase.
The context is a land grab over who controls agent-driven shopping. Walmart already has conversational commerce integrations with Meta's Muse, OpenAI's ChatGPT and Google's Gemini, alongside its own assistant Sparky, and the gateway extends agent shopping to Sam's Club as well. Amazon has taken the opposite line, blocking Meta's Muse agent from its store in September according to coverage of the announcement. Walmart's calculation appears to be that if customers are going to shop through assistants anyway, it would rather be the retailer with a supported, rule-bound path than the one being scraped.
Several things remain unclear. Walmart has not said who gets into the beta or how long invitations take, and the terms are one-sided by design: Walmart can suspend access, change features and block agents at its discretion. There are no published figures yet on how many customers use conversational commerce or what agent-placed orders look like, so the commercial size of this is unknown. Walmart's own post also misexpands MCP as 'model text protocol', a small sign of how new this plumbing still is. And returns remain Walmart's normal process, including when an agent does something the customer did not intend.
Why it mattersThis is the first big US retailer to publish identity, permission and spending rules for AI agents rather than block them, which gives developers a legitimate surface to build shopping tools against.
👀 What to watch
Who actually gets gateway invitations and how fast, whether Agent Profiles ship on time in late November, and whether Amazon shifts from blocking agents to licensing them.
3 opportunities from this story
Build a narrow shopping agent for one specific buyer
General shopping assistants are crowded, but narrow ones are not: restocking a small café's consumables, a cleaning company's supplies, a school's stationery, a clinic's disposables. The gateway plus per-agent spending caps makes this buildable without holding anyone's card details. Start by applying for the beta and building for one business you already know, then sell the same workflow to the twenty businesses like it.
- Best for
- Indie developers and small software shops with a foothold in one trade or vertical
- First step this week
- Apply for the Agent Gateway beta at walmart.com/agents this week and write down the exact restocking workflow of one business you can call today.
Open the full playbook
Launch steps
- Apply for the beta and read the agent terms in full before writing code
- Map one business's reorder list, cadence and approval rules
- Build the smallest version that proposes an order and waits for a human yes
- Run it for one site for a month and measure time saved and mistakes caught
- Only then sell to similar businesses in the same trade
Tools
Risks
Beta access is invitation-only and Walmart can suspend it or change features at any time, so do not build a business that only works on this one gateway. Buying mistakes erode trust fast — keep a human approval step even when the spending cap would allow the purchase, and be clear who eats a wrong order.
Agent governance setup for small businesses letting AI spend money
Any business about to let an assistant place orders needs decisions written down: which agent, whose account, what cap, what needs human sign-off, who reviews the statement, how access gets revoked when someone leaves. Almost none of them have this. Sell a short engagement that produces a one-page policy, the configured profiles and caps, and a monthly review routine. It is unglamorous and highly repeatable.
- Best for
- Bookkeepers, virtual assistants, operations consultants and IT generalists serving small firms
- First step this week
- Draft a one-page agent spending policy template with fields for agent name, cap, approval rule, reviewer and revocation steps, and walk one client through it.
Open the full playbook
Launch steps
- Write the policy template and a matching monthly review checklist
- Configure profiles and caps for two clients and note what confused them
- Fold the monthly review into existing bookkeeping work
- Add a quarterly access audit covering staff changes
- Package it as a named service with a clear price
Tools
Risks
Agent Profiles were announced, not shipped — the stated timing is 'in the next month', so do not promise a date. Keep the service about process and controls rather than guaranteeing no bad purchases happens, and make clear that returns follow the retailer's normal rules.
Make a product catalogue agent-readable before competitors do
Walmart is building a path for agents to query live inventory. Smaller retailers and distributors have product data scattered across spreadsheets, a website and a point-of-sale system, in no shape for any agent to read. Offer to clean it up: one canonical product list with stable identifiers, accurate stock and fulfilment fields, and a small MCP server or documented API over it. This is data plumbing work with a clear business reason attached.
- Best for
- Freelance developers and data consultants working with retailers, distributors and wholesalers
- First step this week
- Take one small retailer's product spreadsheet, normalise it into a clean schema with stable IDs, and stand up a read-only MCP server over it as a demo.
Open the full playbook
Launch steps
- Audit where product, price and stock data actually live today
- Agree one canonical schema with stable product identifiers
- Write the sync jobs that keep it current from the source systems
- Expose a read-only MCP server or documented API over the clean data
- Sell the same pipeline to the next retailer in the same category
Tools
Risks
Agent-driven buying is early, so frame this as data hygiene that pays off regardless rather than a bet on agent traffic. Legacy POS systems and bad source data make timelines slip — scope the audit separately and price it before committing to the build.
Nvidia puts whole AI factories in shipping containers, claiming 14-day on-site deployment
At GTC Berlin on 21 October, Nvidia introduced DSX POD: a reference design that lets partners build and test complete Vera Rubin AI factories inside containers before shipping them. Nvidia says on-site deployment drops from six months to as little as 14 days at a prepared site, with deliveries planned worldwide in early 2027.
Nvidia announced DSX POD at GTC Berlin on 21 October. Rather than assembling an AI data centre on site, partners build it inside containers in a factory: computing, networking, rack-to-rack cabling, rack-level power distribution and liquid-cooling piping are all installed and functionally tested before the container ships. On arrival the pod connects to the site's power, cooling and network. Nvidia's claim is that this cuts on-site deployment 'from six months to as little as 14 days'. Chief executive Jensen Huang framed it in terms of revenue timing, saying an AI factory creates value when it starts producing tokens, not when construction is complete.
The pods are built around Vera Rubin, Nvidia's current platform, whose NVL72 configuration pairs 36 Vera CPUs with 72 Rubin GPUs. Tech Times reports the platform is in full production across more than 350 factories in 30 countries, and that DSX cooling supports fully liquid-cooled operation at coolant temperatures up to 45°C. Nvidia named 17 delivery partners, including Dell Technologies, HPE, Lenovo, Schneider Electric, Vertiv, Bull, Foxconn's Ingrasys, GIGABYTE, Quanta, Pegatron, Wistron, Eaton, Delta, Crusoe, DayOne, Armada and Anduril. Partners plan worldwide deliveries in early 2027.
The problem this targets is electricity, not silicon. Nvidia's own write-up on the DSX platform says more than $300 billion in equipment is backlogged and more than 200 gigawatts of projects sit in US interconnection queues. The DSX software stack is aimed squarely at squeezing more compute out of a fixed power budget: DSX MaxLPS reallocates power dynamically, DSX Flex matches workload demand to grid conditions, DSX Sim builds a digital twin of the facility, and DSX Exchange links compute to building systems. Nvidia cites partner results such as Nscale reporting 49% higher inference throughput within a 264kW budget — a vendor-reported figure, not an independent test.
The 14-day number deserves care. It covers connecting a pod at a site that is already prepared, and Nvidia is explicit that site preparation — power, cooling, networking and the rest — happens separately. Securing a grid connection is routinely the slowest part of building a data centre, and containerising the racks does nothing to speed that up. Nvidia also did not publish a per-pod rack count, GPU count, power draw or price, so the pods cannot yet be compared on cost or density with conventional builds. Coverage noted that one supplier expansion Nvidia announced the same week, IBIDEN's substrate plant, only ramps in the first quarter of 2028.
Taken with the rest of the week's GTC Berlin announcements — substrate capacity targets, a doubling of testing capacity, co-packaged optics expansion — the direction is industrial rather than scientific. Nvidia is trying to turn AI data centres into a manufactured product with a predictable lead time, and to make the grid, the building and the racks behave as one system. For everyone downstream, the practical consequence is that compute capacity may arrive in new places faster than local skills, planning permission or electricity supply can keep up.
Why it mattersIf AI data centres ship as validated containers, capacity becomes a procurement decision with a known lead time, and the bottleneck moves almost entirely to power and people.
👀 What to watch
Whether early-2027 deliveries hold given substrate capacity that only ramps in 2028, and whether any customer publishes a real deployment timeline against the 14-day claim.
3 opportunities from this story
Site-readiness assessments for organisations buying AI capacity
The 14-day promise only applies once power, cooling and network are in place, and most buyers underestimate that part badly. A short, structured assessment — available power and what it would take to upgrade, cooling and water, floor loading, network routes, permits and realistic lead times — is genuinely useful to any university, hospital group, telco or regional operator considering AI hardware. The output is a written readiness report with a cost and time range per gap.
- Best for
- Electrical and mechanical engineers, facilities consultants, data-centre generalists
- First step this week
- Build a site-readiness checklist covering incoming power capacity, cooling, floor loading, network routes and permit lead times, and test it on one building you can walk through this week.
Open the full playbook
Launch steps
- Build the checklist from published liquid-cooling and rack-power requirements
- Interview two local electrical contractors about real grid-connection timelines in your area
- Do one assessment at cost to produce a reference report
- Publish an anonymised version to demonstrate the method
- Offer the assessment to regional operators, universities and large employers
Tools
Risks
This needs real engineering competence — do not offer it without the relevant qualifications or a licensed partner, because getting power or cooling wrong is dangerous and uninsurable. Grid timelines vary enormously by region, so give ranges and name your assumptions rather than single numbers.
Plain-English briefings on AI infrastructure for non-technical decision makers
Boards, councils, pension funds and regional development bodies are being asked to approve or oppose data-centre projects without understanding them. There is steady demand for someone who can explain, in an hour and without jargon, what an AI factory is, what it needs from the grid, what the vendor claims actually mean and which questions to ask. This is paid explanation work, not consulting on the deal itself.
- Best for
- Technical writers, analysts, journalists and consultants comfortable presenting to non-specialists
- First step this week
- Write a 1,500-word explainer on what a containerised AI factory needs from a site, with every vendor claim clearly labelled as vendor-reported, and send it to three people who sit on relevant boards.
Open the full playbook
Launch steps
- Read the primary vendor announcements rather than coverage of them
- Build one slide deck that separates facts, vendor claims and open questions
- Deliver it free once to a local business or civic group for feedback
- Turn the questions you get asked into a standing FAQ
- Offer paid briefings to boards, councils and investor groups
Tools
Risks
Credibility is the whole product, so never repeat a vendor claim as fact and say plainly when something is unknown. Avoid taking a side in local planning disputes if you want to keep selling to both sides.
Power-aware scheduling for teams renting GPUs
Nvidia's DSX software is about fitting more work into a fixed power budget, and the same logic applies one level up: most teams renting GPU time run jobs whenever, at whatever price, on whatever region. A small optimisation service — batch what can wait, move jobs to cheaper regions or hours, right-size instances, kill idle ones — can cut a bill meaningfully without touching the model. Charge a fixed monthly fee rather than a share of savings, which is hard to verify.
- Best for
- DevOps and MLOps freelancers, small cloud consultancies
- First step this week
- Pull one month of a client's or your own GPU billing data, classify jobs into urgent and deferrable, and calculate what rescheduling the deferrable half would have saved.
Open the full playbook
Launch steps
- Build a billing analysis script that groups spend by job type and idle time
- Produce one before-and-after report using your own workloads
- Offer a paid audit with a written set of changes
- Implement queueing and autoscaling changes under a retainer
- Report monthly in money saved, not percentages
Tools
Risks
Deferring jobs trades latency for cost, and some teams will not accept that — agree what is deferrable in writing first. Spot capacity can be reclaimed mid-job, so checkpointing has to be in place before you move anything important.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.