It's racing across X this week under the banner "Google just dropped a free 1-hour course." Two things are true: the curriculum is genuinely good, and we could not confirm it's an official Google release. Here's what's in the hour — and what a team of one should actually take from it.
A year ago we compared two ways to bolt a quality check onto RAG. There is a third, and it checks a different thing entirely — not the answer, not the documents, but the question. Here is which one fixes which failure.
If your agent reads screenshots, documents, or video at volume, one of these is roughly 50x cheaper per token — and it isn't the one with the famous logo.
Project Perception enters public preview August 3 with red/blue/green agent teams. Ignore the enterprise packaging — the real lesson for a team of one is the 90/10 model split underneath it: a small specialized model does the bulk, a frontier model handles only the hard tail, and the reported bill drops 50%.
The 'Pacing the Frontier' letter — signed by Dario Amodei, OpenAI's Jakub Pachocki and Mark Chen, and hundreds more, and endorsed by OpenAI and Anthropic as companies — isn't a pause. It's a bet on where model access is heading, and it's a leading indicator you can plan against.
Three ways to keep an OpenAI conversation going, and they are not interchangeable. One of them silently forgets everything after 30 days — pick the wrong one and your users lose their history.
On August 1, OpenAI confirmed the 'Astra' name the hard way: a report claiming an internal model produced machine-checkable solutions to ten previously-open problems in math, quantum complexity, and theoretical CS — for about $2,000 of compute. Astra isn't a product you can call. But the pattern it demonstrates — an agent that works for hours and hands back output a machine can verify — is one a team of one should copy now.
Free frontier credits for scientists today are a distribution play, not a grant: they pre-seed the vendor defaults on the companies those researchers found in two-to-four years.
Cohere's North Mini Code is a 30B/3B model that fits on one H100 in FP8 with no quantization gymnastics. It gives up a couple of SWE-bench points to Qwen and GLM — and buys back the simplest self-host on the board.
Three of the most-cited ways to see inside an LLM app, and they split on two questions that decide everything: what you're allowed to self-host for free, and whether your traces are portable. Here's the decision, with real licenses, prices, and star counts.
Your agent is only as dangerous as the widest token it carries. Here's the hands-on way to cut each one to least privilege — scopes, per-tool allowlists, short-lived exchange, and an MCP handle pattern — before a buyer's security review asks.
Three different mechanisms hide behind 'run my agent every morning' — a session-scoped /loop, a cloud Routine, and a Desktop task. They have different failure modes. Here's which one to reach for, with the cron and expiry gotchas that bite unattended jobs.
As of Claude Code 2.1.218, a skill with context: fork runs in the background by default — you keep working while it does. Here's when to detach a skill, when to set background: false, and the tool-set gotcha that bites people who don't.
A budget model 'beats the flagship on nine benchmarks' about once a week now. Here's the five-question checklist a founder runs on any vendor's agent scores — worked live on DeepSeek's July 31 V4-Flash table — so you switch models on evidence, not on a press release.
Ship a new version while an agent is three tool-calls deep and the default outcome is a dropped run. LangGraph 1.2's graceful drain stops at a clean boundary and leaves a checkpoint you can resume — but only if you wire the SIGTERM path yourself.
Three platforms every founder shipping image, video, or voice AI ends up comparing — and the real axis isn't price per hour. It's how much of the stack each one hands you, which quietly decides your bill, your cold starts, and how much code you own.
The Digital Omnibus delayed the Act's hardest rules to 2027. Article 50 was not one of them: if your product generates images, audio, video, or text, you must now mark it so a machine can detect it was AI-made. Here's the obligation, the December grace you might still have, and the one standard the Commission has already blessed.
These two rock-bottom models aren't fighting for one slot — one is the cheap text-and-tool workhorse, the other is the first cheap-enough pair of eyes, and the deciding question is whether your loop reads pixels.
No new architecture, no bigger model — just another round of post-training. DeepSeek says its $0.14/M budget model now beats its flagship preview on all nine agent benchmarks. Every number is vendor-stated. Here's what a founder should actually do with that.
Qwen3.7 Flash lists a 1M-token window at ~$0.03/$0.13 per million tokens. The tempting conclusion — stop compacting, just dump everything in — is half right. Cheap context fixes the bill. It does nothing for the rot.
The AI-agent research at Black Hat this week rhymes on one point: the guardrail you wrapped around the model isn't where you get owned. Three verified briefings, and the founder fix each one implies.
On August 6, AWS moves Agent Registry out of preview and out of the bedrock-agentcore namespace into a dedicated agent-registry namespace — quietly making agent discovery a hyperscaler default.
A registry tells you what agents and tools exist; a gateway controls how traffic to them is routed, authed, and governed. Buy the wrong one and you solve a problem you don't have.
Five verified moves a team of one should act on this week: a token bill that just dropped 5×, a compliance deadline that lands on you and not your model vendor, a billion-dollar bet on governing what your agents can touch, Nvidia turning compute into equity, and where the agent money is actually going.
Last week the headlines were specs and model weights. This week the signal is capital and access — a record raise into an open-weight lab, the frontier lab widening who gets in, and the cheap-multimodal floor dropping again. For a team of one, your inputs got cheaper and your competition got better funded.
You turned on speculative decoding and your endpoint got slower. That's not a bug — it's the design. Spec decode trades spare compute for lower latency, and above a certain batch size you've run out of spare compute. Here's where the line is and how to measure yours.
The reason your enterprise deal stalls at 'we can't send customer data to an LLM' isn't the model — it's that you can only promise the host never sees the prompt. Tinfoil runs the model inside a hardware enclave with remote attestation, so you can prove it instead.
What Test Companion is, who it's for, how to start (it's in free Alpha), and the honest catch — BrowserStack put a test-writing, failure-diagnosing, self-healing agent inside your editor, wired to a 30,000-device real cloud.
The deal is verbal-yes until their security team sends the questionnaire. Here's the exact list of artifacts that unblocks it — SOC 2, a DPA, a subprocessor register, and the AI-specific answers that are new in 2026 — and the order to get them in without torching six weeks.
The generative-agents researcher behind 'Smallville' just closed a $200M Series B, five months after a $100M A. Simulated users are now a funded category. The founder question isn't whether to use them — it's which decision you let them near.