MiniMax H3 dropped today with open weights, and ComfyUI has native support on day zero. It’s MiniMax’s third-generation video model (after Hailuo 01 and 02) and the first released open-weights: feed it text, images, video, or audio and it generates video with real stereo sound — up to 2K, up to 15 seconds per clip. Modes include text-to-video, image-to-video, first-and-last-frame control, and reference-to-video, where a reference clip can carry a subject, a motion, or even a voice through the shot. Audio is generated in the same pass, not bolted on afterward. ...

Niklas Gruhn’s short, sharp essay against relaying AI output verbatim in human communication. When someone asks a question in Slack, leaves PR feedback, or argues in a WhatsApp group, the worst response is “Claude said: [giant verbatim output]” — the other person can prompt Claude themselves, faster, with their own context; they don’t need a meat proxy in between. Reading AI output is extra effort: it’s verbose, full of all-too-plausible nonsense, and increasingly jargon-dense (his example: “NATS control-plane events: stream leader election / R3 quorum re-form during pod churn” — he had to look up nearly every word). The rule: prompt AI freely, but read it, understand it, validate it, then write the response in your own words — your own-words version is a “decent certificate” you actually did those steps. The sharpest edge is code review: you can ship code with near-zero effort by copy/pasting tickets into Claude Code and never reading what it wrote — but then who did the implementation? The reviewers did, using Claude Code, and you were the meat proxy. ...

Strong day, anchored by one big release: Qwen3.8-Max is the first open-weight Max-class model, and it’s a coding/cowork flagship — 2.4T params (95B active) with weights due next week. arXiv is also back after the weekend skip (618 papers; 4 kept). Agent frameworks & tooling OpenClaw and Ollama in Agentic AI: Toward Fully Autonomous and Scalable AI Agent Systems (arXiv 2607.28629) — A full-stack agent architecture that treats Ollama (local inference) + OpenClaw (orchestration) as a single system; argues agent capabilities emerge from system-level integration, with code/models released. Model or Harness? An Interaction-Centric Taxonomy for Localizing Agent Failures (arXiv 2607.28802) — 41 agent failure modes mapped to model/harness/environment edges so you know which side to fix; grounded across coding agents and multi-agent systems. Tool Specifications Matter: Uncovering and Mitigating Safety Risks in AI Agents (arXiv 2607.29254) — Schema-formatted tool specs measurably weaken refusal; the open-source SafeKeep safeguard lifts refusal 23.8%→70.6% and cuts prompt-injection success 25.6%→2.5% at inference time. Zero-Mem: Zero-Token Memory Operations for LLM Agents (arXiv 2607.29377) — Agent memory without LLM calls for store/retrieve: entity-context graph + temporal hierarchy, −57.6% memory-op time vs the fastest baseline; code promised post-review. Models & research Qwen3.8-Max: A New Bar for Coding and Cowork (qwen.ai) — Official release: 2.4T-param (95B active) MoE, first open-weight Max-class model (weights next week), API at $2/$6 per 1M tokens; Qwen3.8-27B reported to run in ~17GB VRAM (r/LocalLLaMA). BM25 Wins at Scale: A Scaling Study of Retrieval-Augmented Generation Paradigms (arXiv 2607.26497) — Controlled 28-tier corpus scaling study: agentic file-search burns ~39× query tokens and BM25 overtakes it past ~10M corpus tokens; argues for ranked discovery before agentic reasoning. Why we write our own C and C++ inference engines (LocalAI) — vllm.cpp ships a 66 MiB binary that ties vLLM’s throughput, with a parity-gated porting methodology (weights → graph → optimize → C ABI) worth copying for self-hosted serving. Industry DeepSeek’s new AI model is by far the cheapest well-known model, research firm says (Reuters) — Artificial Analysis: V4-Flash at $0.14/$0.28 per 1M tokens (~$0.03/test) vs Kimi K3’s $0.86 and GPT-5.6 Sol’s $1.86 — concrete cost data for API routing. (Link blocked by Reuters antibot; collector-sourced, not live-verified.) The race to build an American alternative to cheap AI from China (WSJ) — VCs question the revenue potential of open-weight startups (Arcee, Reflection AI, Poolside) — the economics behind the open-weight ecosystem the self-host stack depends on. EU: AI-generated media and deepfakes must be labelled; chatbots must state they aren’t human (Bluesky @ec.europa.eu) — Official EU account on transparency obligations (deepfake labels, bot disclosure, biometric-analysis notice) — a compliance checklist for anyone shipping agents/chatbots in Europe. (Link not live-fetchable; Bluesky blocks scrapers, collector-sourced.) Compiled from the morning digest — X, HN, Reddit, Techmeme, Bluesky, arXiv. Hype cut, links kept. ...

David Crawshaw (Tailscale co-founder, now building exe.dev) argues the open-source-everything era of devtools has arrived not as ideology but as a consequence of AI agents. Five years ago, custom software rarely made sense — the cost of maintaining and learning a codebase dwarfed its benefit, so we amortized customization through config files, plugin systems, and extension APIs. Agents change both sides of the ROI: the setup prompt (“download the source, build it for local use, record why in version control”) makes personalizing trivial, and the maintenance prompt — a nightly cron that fetches upstream and rebases local changes on top, checking the software still works — makes staying in sync automatic. The thesis: for personal or small-team software, the source code is the extension system. He demonstrates it by wiring his own diff-minimizing tool (meat.dev) into his agent Shelley with a single prompt, and contrasts it with Claude Code, which is closed-source — “you don’t get to personalize it.” The practical pattern for agent users: record the why of local changes in version control, rebase onto upstream nightly, and codify the workflow as a skill. ...

A quiet-ish weekend in AI, but the big one is real: DeepSeek V4-Flash 0731 is out as open weights, with V4-Pro said to follow soon. Models & research DeepSeek V4-Flash 0731 released open-weights — official org repo is live (Hugging Face). Community threads report dirt-cheap API pricing (~18x cheaper input pricing vs Claude per one r/Anthropic post) — pricing and “matches Opus 4.8” claims are community-reported, not independently verified. Running Kimi K3 on MI355X at better performance-per-dollar than B300 — vendor benchmark (wafer.ai) claiming AMD’s MI355X beats the B300 on inference $/token for Kimi K3. Take the numbers as vendor claims, but it’s the kind of data that decides self-host GPU buys. SKILL-KD: skill distillation for frozen LLM agents (arXiv 2607.28048) — surfaced but unverified this run: claims a framework that turns teacher-student discrepancies into reusable skills for frozen agents. Check the abs page before citing. Agent frameworks & tooling Diagrid Catalyst 2.0 adds durable recovery to LangGraph — crash-safe durable recovery and signed execution histories for LangGraph via Dapr workflows (Bluesky). Relevant if you need restart-safe, auditable agent runs in production. Industry China pushes open-source AI at the UN summit — a large Chinese delegation at the UN AI for Good summit argued Chinese open models are the future for most of the world (Semafor). Fields Medal winner Jacob Tsimerman to join OpenAI for AI-safety work — the Toronto mathematician takes a leave to work on AI safety (WSJ). Apple caps bug-report submissions citing a deluge of AI-assisted reports — a 30-day cool-off with quota exceptions for researchers (FT). A real-world signal that AI-generated issue volume is forcing policy changes. Compiled from the morning digest — X, HN, Reddit, Techmeme, Bluesky, arXiv. Hype cut, links kept. ...

Shreya Shankar (UC Berkeley PhD) presents DAB — the Data Agent Benchmark (“Can AI agents answer your data questions?”), from her PhD work at Berkeley. ~27 minutes on Hamel Husain’s channel. Why data agents matter Huge real use case: AI answering business questions — much office work is this Enterprises struggle to use Claude Code / Codex off-the-shelf for BI tasks, so they build their own data agents: Uber’s Query GPT (1.2M queries/month at launch), OpenAI’s in-house agent, Databricks, Snowflake Existing benchmarks fall short: Text-to-SQL — assumes clean data in one Postgres/Snowflake; real enterprises have fragmented data; SQL alone isn’t enough (need domain knowledge, reasoning over outputs) Table QA — context table + question; doesn’t scale to enterprise data volume The formative study — 4 real-world challenges Interviews with enterprises + Hasura (PromptQL) surfaced four properties missing from existing benchmarks: ...

Hamel Husain demos a Codex capability most people don’t know about: Codex can control itself — spawning parallel threads, letting them coordinate, and driving computer use. ~5 minutes on his own channel. The demo setup Working project: AEO — optimizing one of his websites for AI discovery (making it findable by AI search engines) Codex listed 16 high-value tasks from the project file (aeo-to-do.md) — the fuel for the orchestration demo Spawning threads Prompt: “Open a new thread for each task and explain how you’d tackle it, along with prerequisite steps” — Codex spawns 16 parallel threads in the sidebar Codex can also rename and delete threads itself Value: manage separate tasks completely independently, no window-jumping Threads talking to threads Inside any thread you can query another: “What is AEO 1 doing? Does it need any help?” Great for orchestrating when things get stuck, or starting a supervisor thread that manages others and unblocks them Steering and queues Ask for a status table when threads finish: which can run in parallel, which need human intervention or input Broadcast guidance to all threads: “Direct threads that can work independently with computer use to start — don’t start work if you need other threads to finish first” One thread inventories the active threads and coordinates the rest — “this starts to become super powerful” Computer use A thread opens the browser itself: checks Bing Webmaster Tools, Google Search Console, etc. It tells Hamel what it needs (accepting a verification), keeps going, and reports when it gets stuck Mobile Same thread list appears on your phone — manage all parallel threads remotely, even away from the computer “You can have Codex control Codex and become a power user to do a lot of things faster and parallelize your work.” ...

Joe Barrow (ex-Amazon/Adobe, ML lead at Pattern Data, now Adobe Research’s Document Intelligence Lab) on choosing an OCR model for AI document processing. 24 minutes on Hamel Husain’s channel. Why OCR matters Your app sits downstream of OCR quality — garbage in, garbage out, no matter what the LLM does after It’s not solved — Anthropic shipped bad PDF handling for a year because it was pulling text, not doing OCR; users noticed OCR is sticky — once you build on a vendor, swapping models is painful (Pattern learned this the hard way) Documents are evil — multi-column layouts, rotated scans, no reading order; TeX-compiled PDFs have no spaces (glyph glue), so naive text extraction gives you one run of characters The decision grid: two axes Text blocks vs. document structure Text blocks: word/line bounding boxes → grounding, evidence highlighting, cheapest Structure: headings, reading order, grouped paragraphs, tables, figure alt text, chart de-rendering → much better LLM input (LLMs are trained on markdown-like structure; raw line runs look like garbage to them) API vs. self-host API: ease of use, vendor support (startups retrain on your bad docs), minimal time — right for ~95% of teams Self-host: control throughput/concurrency (APIs cap concurrent docs — a real bottleneck), stable weights, domain fine-tuning, no lock-in, cheaper at bulk — but only if your time ≈ $0 or you run huge batches The four quadrants Big cloud APIs (AWS Textract, Google Cloud Vision, Azure) — $0.60–1.50 / 1k pages; word+line boxes only; tables/forms a la carte at $10–15 / 1k Document startups (Reducto, Data Lab, Extend, LlamaIndex) — $5–20 / 1k pages, “fast” vs “accurate” tiers; structure included (markdown/HTML, tables, figure boxes) Open pipelines (PaddleOCR, Nemo Tron, Tesseract) — 10–100M params, nearly free, edge-deployable (PaddleOCR runs on phones/e-ink); text lines only, post-process with layout models Open VLMs (LightOn OCR 2, GLM OCR, GOT-OCR, Chandra/Surya) — 600M–8B params, native document structure, ~$0.20–0.30 / 1k pages on a saturated H100; hallucination risk exists but clouds hallucinate on crusty scans too How to actually choose Ignore benchmarks (OmniDocBench, CR Bench) — they’re not run on your data Build a 50–100 page sample of your own representative PDFs Run a few candidates, diff the returned text (catches junk-on-handwriting fast), visualize the boxes ~a day of effort total — then pick Watch the license Chandra/Surya (Data Lab): free only if org < $2M revenue AND not competing with Data Lab LightOn OCR: Apache. GLM OCR: MIT (but relies on PaddlePaddle’s Doc Layout model — Apache — both apply) Self-hosting, for the ~5% who should Inference engines: VL (default, OpenAI-style client) or SGLang; infra: Modal (request-queue scaling beats SageMaker), BaseTen, or big cloud for one-off batches 1B-param models (LightOn, GLM) on H100 → ~10k pages/hr, 20–30¢ / 1k pages; 4×3090 ≈ one H100 → 3–4 pages/sec His 7M-page local-laws dataset: ran over a weekend at ~30¢ / 1k all-in “You can process 1,000 pages per second, but it doesn’t matter if they’re all wrong — then your entire app’s output is going to be garbage.” ...

Jeff Su’s counter to the default “jump in, pick a template, start prompting” tutorials — that path gives you generic output and burns tokens fixing unusable slides. His fix: three files prepared ahead of time, demonstrated with the actual deck he used for a paid workshop. ...

Futurepedia’s full-platform guide to Claude Design after its big upgrade — the host skipped covering it at launch because usage limits made it barely usable; that’s fixed (usage now bundles into your existing Claude credits). The overview: 15+ template types (mobile apps, slides, documents, wireframes, animations, UI mockups, resumes, 3D objects, HTML email, flyers), and the design-system workflow that stops output from looking like generic AI slop. ...