TurboFieldfare runs a 26B MoE LLM on an 8GB MacBook Air at ~2GB RAM
Independent developer Andrey Mikhaylov’s Swift/Metal engine keeps a shared core in memory and streams idle experts from SSD so Gemma 4 26B-A4B fits machines that should not hold it.
Why it matters: As open models shift to mixture-of-experts, the binding constraint is RAM for rarely touched weights, not raw compute. Builders who want local stacks need to know when expert streaming helps, when plain llama.cpp already matches it, and what quality and energy tradeoffs the trick hides.
- TurboFieldfare is a model-specific Swift and Metal engine for Gemma 4 26B-A4B-it, not a general MLX or llama.cpp wrapper; it keeps a 1.35GB shared core plus KV cache resident and streams the other ~120 idle experts from SSD per token.
- Reported speeds: about 5.1–6.3 tokens/sec on an 8GB M2 MacBook Air using roughly 2GB RAM, and 24–35 tok/s on a 24GB M5 Pro.
- Per token, an 8-bit router selects 8 of 128 experts plus one shared expert; a 16-slot least-frequently-used cache is used to keep SSD reads survivable, while the model’s 256K context window still competes for the same small RAM budget.
- An independent LM Studio coding benchmark scored this exact model 33.33% with all 21 test cases failed; a 2026 arXiv paper on SSD-offloaded MoE also found energy costs can jump nearly 10x.
- The same model already ran on 16GB Macs via plain llama.cpp at comparable speeds without a custom engine; Apple’s MLX-LM still lacks native expert-streaming support that this project reached after many failed experiments.
Local LLMsMoEApple SiliconTools
ARMS context framework: Applications, Routines, Memory, and Skills for Claude agents
A multi-video RoboNuggets roundup argues that organizing agent context as ARMS—plus progressive disclosure, thinner prompts, and judgment-friendly skills—beats stuffing everything into one giant Claude.md.
Why it matters: Agent quality increasingly depends on how you structure tools, schedules, artifacts, and invocable SOPs—not on longer system prompts. Builders running Claude Code can cut dead context, load the right files on demand, and get more consistent brand/design output from reusable skills.
- ARMS frames context as four layers: Applications connected via MCPs/APIs/CLIs, Routines (scheduled tasks/crons), Memory (artifacts, reports, documents), and Skills (SOPs invoked by skill commands that teach the agent a process on demand).
- Progressive disclosure replaces front-loading every rule: competent models load the right context when needed instead of carrying full code-review/verification detail in every session; sub-indexes by department/workspace help the agent navigate large file trees without a bloated Claude.md.
- Example skills shown include a “surprise me” skill.md that pushes frontend taste/artistic judgment, and a `/robo` brand skill tied to brand book.html (colors, voice, fonts, dot-matrix visual style) for consistent RoboNuggets materials.
- The “judgment rule” says over-strict legacy prompts (e.g., never write comments or multi-paragraph docstrings, hard file-deletion guards) can now limit stronger models; prefer letting the agent apply judgment where worst-case risk is lower.
- Claude Code’s `/doctor` skill checks broken/duplicate installs and path issues, finds dead weight in skills/MCP servers/Claude.md, and trims setup; Anthropic also shifted toward automatic memory saves rather than only manual `#` writes to Claude.md—still worth explicitly logging high-value session outcomes.
Agentic codingClaude CodeContext engineeringTools
GitHub ships stacked PRs; OpenAI Astra solves 10 open math problems with Lean proofs
Better Stack covers two releases: native stacked pull requests on GitHub, and OpenAI Astra producing compile-//-yourself Lean certificates for about $2,000 in tokens.
Why it matters: Stacked PRs make large or agent-generated changes reviewable as dependent branches instead of one giant diff. Astra’s harness and verifiable proofs show how to keep a model on one hard problem for days without trusting the output blindly.
- GitHub stacked pull requests are in public preview: a chain of smaller dependent branches that merge independently instead of one giant PR nobody wants to review.
- You can build a stack with the GitHub CLI, push multiple PRs in one command, or stack without the CLI; review and merge walk through the dependent chain.
- The format matters for shipping big changes and for letting an agent code for hours without forcing a single unreviewable diff.
- OpenAI’s Astra solved ten open problems in mathematics and theoretical computer science; every proof ships with a Lean certificate you can compile yourself.
- Reported token cost was roughly $2,000; the video flags what that claim leaves out and cites a prior GPT-5 Erdős embarrassment as trust context.
- Engineering takeaway: coherence breaks before intelligence—the harness keeps the model pointed at one problem for days; splitting problems is not free and this is not framed as replacing mathematicians.
Agentic codingToolsMathGitHub
AI Hero Skills v1.2 adds Wait What, Writing for Agents, Wizard, and Grill Me fixes
Matt Pocock’s Skills pack ships a docs site, Claude Code marketplace install, Codex compatibility work, and new agent workflow skills.
Why it matters: Reusable slash-skills give coding agents structured prompts for clarity, requirements grilling, agent-oriented writing, and infra provisioning—now easier to install and use across Claude Code and Codex.
- Skills v1.2.0 is out with a new documentation site at aihero.dev/skills.
- Adds Claude Code marketplace integration plus Codex compatibility improvements.
- New Wait What skill targets Opus verbosity and pushes the agent toward clarity.
- Grill Me is updated for multi-question rounds; new skills include Writing for Agents and Wizard for infrastructure provisioning.
- To Questionnaire supports collaboration workflows; an AI Coding Crash Course is announced as coming soon.
Agentic codingToolsSkills
LangChain engineer demos voice-agent tracing with Gemini Live and LangSmith
Caroline di Vittorio builds a terminal weather voice agent on Google ADK and Gemini Live, then wires LangSmith so full audio, tools, interruptions, and costs show up in one trace.
Why it matters: Speech-to-speech agents are hard to debug because most of the loop never becomes plain text. This walkthrough shows a concrete path to inspect what the user actually heard, which tools ran, and what each turn cost.
- Gemini Live is Google’s native audio model: it takes speech in and returns speech out without a separate transcription step, which the talk frames as lower latency and more natural, emotive voice.
- The demo agent is a terminal-based weather assistant with two tools, built on the Google ADK and run with a LangSmith Google ADK plugin registered on the runner.
- User and agent audio are recorded so the trace reflects only what the user actually heard, not intermediate pipeline noise.
- In LangSmith you can inspect the full trace: audio playback, transcripts, tool calls, interruption events, and token-level cost breakdowns.
- Setup path called out in the video: get a Gemini API key in Google AI Studio, then use the Gemini Live, Google ADK, and LangSmith docs linked from the description.
Voice agentsObservabilityAgentic codingTools
ChatGPT Side Chat in Chrome plus MiniMax H3 video model covered in dual upgrade roundup
Julian Goldie walks through ChatGPT’s new in-Chrome side chat that reads tabs, highlights, history, and YouTube, then covers MiniMax H3’s cheaper omnimodal video-with-audio generation.
Why it matters: If you live in browser tabs, in-page ChatGPT cuts copy-paste and context switching; if you ship short video, MiniMax H3’s claimed native audio and lower cost change the default tool math. Both are early/limited depending on access.
- ChatGPT Side Chat sits inside Chrome and can use open tabs, explain highlighted on-page text, compare across tabs, break down YouTube videos, and recall browser history without manual paste.
- The video positions this as AI as a browser layer rather than a separate destination, and contrasts it with prior standalone-browser approaches it says fell short.
- Catch stated in the video: rollout is slow and the experience is Chrome-only for now.
- Second segment covers MiniMax H3, described as a Chinese omnimodal model that reads text, image, video, and audio and can generate 2K studio-style clips with a native soundtrack in one pass.
- Claims from the host: beats the older silent 1080p pattern, ranks #1 for AI editing and top 3 for text/image-to-video on the leaderboards he cites, supports one-prompt script-to-finished-video flow, is about 3x cheaper than Western tools he compares, keeps character/style consistency, and open weights are said to be coming soon.
- Evidence in the source is the creator’s demo/narration and ranking claims; no independent benchmarks or pricing tables are supplied in the notes.
ToolsBrowser agentsVideo generationChatGPT
Creator wires Claude Code to Mobbin via MCP to generate UI from real app designs
Sean Kochel demos a Mobbin MCP server with Claude so generated screens pull patterns from a large mobile/web design library.
Why it matters: Agent builders can ground UI generation in production app patterns instead of generic model priors. The demo is a concrete MCP pattern for attaching a design reference library to a coding agent.
- Workflow uses a Mobbin MCP server alongside Claude so the agent can reference Mobbin UI patterns while building screens.
- Video covers connecting Claude to Mobbin, then generating screens, an onboarding flow, and a time picker.
- Creator links a “PRD LITE” skill plus other UX skills on a Skool classroom for structured product-requirement input.
- Title claims feeding ~600,000 designs; the source is a process walkthrough and does not report quality scores, win rates, or failure cases.
- Resources named in-video: Mobbin and the Skool skill classroom.
Agentic codingToolsUX