Your tool list is the fattest, most stable block in every agent request — and until now, changing it mid-run silently re-billed the entire cached prefix at full price. A new Claude beta lets you add and remove tools between turns while the cache survives. Here's the exact mechanic.
Context editing and compaction both fight a full window by damaging what's already in it. A subagent never lets the mess in — it gets a fresh window and hands back one clean result. Here's the line between them.
Four ways to require a human before an agent commits a consequential action — software step-up, hardware key, crypto signer, or nothing — and the single question that tells you which one each action needs.
Your RAG pipeline is only as good as the text you feed it, and a bad parser silently interleaves columns and mangles tables. Four leading options split into two camps — here's the one that fits your documents, your compliance line, and your budget.
They both live in your 'lower the agent's token bill' folder, so builders reach for them interchangeably. They aren't. One makes the tokens you keep re-sending cheaper; the other deletes tokens so you stop sending them — and they quietly fight over your cache.
Pinecone says the RAG era is ending and pitches a 'knowledge engine' that compiles context once instead of retrieving on every call. The real decision is what tax you'd rather pay.
The 2026-07-28 stateless core lets any request hit any instance — so drop ip_hash, add a /health probe, and move only your Tasks state to a shared store.
Crunchbase and Axonius both shipped MCP servers on the same day this week. The point isn't the integration — it's that your product becomes callable inside ChatGPT and Claude, where your buyer already is.
Kimi K3 is huge on paper and light on the meter — sparse MoE fires ~16 of 896 experts per token, Delta Attention bounds the long-context decode, and Attention Residuals is a training-time freebie.
HubSpot put its AI agents in a no-code console on July 23 — but the number a founder should read is the price tag: $1 per recommended lead, and you don't pay the support agent until it closes the ticket.
The decision piece told you they're a division of labor. This is the code: one request that clears stale tool results in the window and writes durable facts outside it — plus the four config lines that keep it from thrashing your prompt cache.
Anthropic's Code Review dispatches five specialized agents on every pull request, scores each finding 0–100, and posts only what clears the bar. Here's how to turn it on — and how the false-positive filter actually works.
The weights dropped today. The headline is 2.8 trillion parameters; the number that sets your bill is 50 billion. Here is the real hardware math, the serving shape, and the one line that decides whether you rent or own.
The loop every tutorial shows you is five lines. The loop that survives a real agent is defined by its edges — four message-shape rules the API enforces with a 400, and four stopping conditions that keep it from running forever.
Your loop checks for one stop_reason and assumes the rest never happen. Then max_tokens truncates a tool call mid-JSON, pause_turn strands a web search, and a refusal returns empty content — and your agent hangs or crashes. Here's what each of the six actually means and what to do about it.
Both landed this week, and their output tokens cost the same $15. One is a managed closed model, the other ships open weights you can host. Here is the decision that actually turns on it.
Two verified July 23 releases turn a solo founder's backlog into an agent workspace: assign a Linear issue to an async Copilot agent and get a draft PR back, and let GitHub Issues auto-triage inbound with a confidence dial you set.
The Autorité de la concurrence built its own agents, ran 550 shopping queries, and concluded OpenAI, Google, and Anthropic already hold 84% of the market. The remedies it proposes are the map of where a founder's real risk lives.
Anthropic ships three levers for a context window that fills with junk — clearing, compaction, and memory. OpenAI and LangGraph have the same three, under different names. Here's which to reach for, and where each vendor's version differs.
Two frontier-class models landed the same week — one closed and cheaper-to-start, one open-weight and yours to own. The choice isn't the benchmark; it's cost at scale, data control, and how much you trust an autonomous loop.
Both shipped this month, both cost $5 per million input tokens, and both sit at the top of the coding leaderboards. The decision isn't the benchmark — it's caching, the harness you already build in, and how you route down when the task is easy.
The 2026-07-28 spec deprecates the one auth step every remote MCP client relied on. Here is what Client ID Metadata Documents replace it with, and which one you should ship.
Since July 20, 2026, every new AgentCore agent streams its traces, prompts, structured logs, and stdout into a single per-agent CloudWatch log group — no config. Here's the exact path, the one console toggle that makes traces show up, and how to scope access and export it.
AgentCore now ships per-agent tracing by default, so the question changed from 'which observability tool' to 'do I still need one at all?' The honest answer: it depends on one thing — whether AgentCore is your whole stack. Here's the decision, and why it's not either/or.
Anthropic says context editing cut tokens 84% and memory-plus-editing lifted task success 39%. Both figures are real. Neither says the model got smarter — they measure escaping a wall your agent may never hit, or may hit in a shape the benchmark never tested.
The 2026-07-28 revision deletes the session, the handshake, and the session-id header. Here is exactly what a server author has to change — and what keeps working untouched for a year.
Five verified moves a team of one should act on: the MCP deadline finally arrives, a frontier model gets a 1M window at no price bump, a near-frontier open model you can self-host, and the EU disclosure rule that starts biting in six days.
Everyone's watching the spec date. The verified story for a team of one is quieter: four production SDKs, a live registry, and zero-touch enterprise auth all landed before the deadline. Here's what's real, what to test this weekend, and the three moves that matter before Tuesday.
Both inference engines shipped the same day again (July 25). The scheduler-overlap fight that defined the last round didn't get a sequel — so the real question moved to speculative decoding, prefix caching, and which new models you can serve day one.
The July 25 release adds fp32 lm_head via head_dtype, a different attention backend per KV-cache group, and an object-store tier for KV offload. If you self-host inference, here's what to flip and what it buys.