AI Weekly Malaysia

MicroLLM Lab is a browser-based playground that runs 7 tiny language models (25M–360M parameters) fully on-device using WebGPU and Q4 quantization, caching them in IndexedDB with no accounts or server. Q4 shrinks weights from 16-bit to 4 bits per parameter (a claimed 75% memory reduction), so 100M+ models fit in roughly 50–84 MB of browser memory. It ships a benchmark tab that scores speed (tokens/s sustained over a 256-token decode) and accuracy via objective regex/exact-token checks rather than writing quality, and offers a 589 MB zip download; the Hacker News thread drew 272 points and 111 comments.

Why: If you currently pay per-token just to classify, filter spam, or extract intent before calling a frontier model, this gives you a free way to measure whether a 25M–360M Q4 model can do that triage step on the client instead — and its accuracy benchmark returns a pass-rate number on objective checks, not vibes. Two practical caveats from the page: the full model bundle is a 589 MB download and models cache into each user's browser IndexedDB, so bandwidth and first-load UX are real costs for your users. The claimed sub-10ms time-to-first-token is the author's own figure — verify it against your own hardware before designing a real-time autocomplete flow around it.

Cloudflare published a follow-up on Kitesurf, the browser it launched in August that runs entirely on Cloudflare Workers, and the headline change is WebMCP support: sites can expose callable tools (the post uses searchFlights() and Cloudflare Radar's navigate-to / set-location as examples) so agents call functions instead of simulating clicks. Kitesurf also added a batch of browser standards — CSS Layout, CSSOM, CSS Typed OM, custom elements, plus URL-based module resolution, JSON modules, and import map handling — aimed at rendering heavier JavaScript-chunked pages. You can try it in Cloudflare's public Kitesurf playground or point an agent at it via a chrome-devtools-mcp config using a wss:// browser-run devtools endpoint with browser=kitesurf and --category-experimental-webmcp.

Why: If you build or operate agents that touch websites, this gives you a concrete alternative to pixel-clicking: check the Application tab in DevTools on a target site to see whether it already publishes WebMCP tools, and if it does, wire your agent to call them. The MCP config in the post (chrome-devtools-mcp@latest pointed at the browser-run WebSocket endpoint with --category-experimental-webmcp) is copy-pasteable, so you can test tool-calling against Radar without running your own headless browser. Caveat: this is Cloudflare announcing its own product and the post claims Kitesurf is now 'more capable and more efficient' without publishing any benchmark numbers, so treat the efficiency claim as unverified.

Ars Technica published an interview with Mozilla's head of Firefox, framed around a redesign the interviewee hopes will win users away from Chrome, along with product priorities, AI skepticism, and browser choice. The text supplied here contains none of the interview content — only Ars Technica's Condé Nast cookie-consent boilerplate about targeted-advertising opt-outs for US states. No version numbers, dates, features, or quotes from the interview are available in this excerpt.

Why: There is nothing actionable in this excerpt: it lists US state privacy opt-out mechanics (Colorado, Connecticut, Virginia, Utah, Oregon, Texas, and others) rather than anything about Firefox. Anyone expecting a redesign timeline, a feature list, or an AI stance will not find it here, so do not build a segment or a decision around this text until the actual interview body is retrieved.