OpenAI open-sourced its Codex Security CLI in late July, and it emits SARIF — the same format GitHub's Code Scanning tab already reads. Here's the copy-paste pipeline that turns an AI scanner into a real, blocking PR gate, plus the one setting that stops it from crying wolf.
The gap between 'send' and the first visible token is where users decide your product feels fast or broken. Here's the end-to-end SSE path — backend to browser — and the buffering bug that silently un-streams it.
One command starts the server. The VRAM formula tells you which open models you can actually run on a founder budget — and the cost-per-million math tells you when self-hosting beats just paying the API.
Software approval gates stop the agent that asks nicely. They do nothing about the one that's been prompt-injected. Here's the hands-on way to require a physical key press — bound to one specific action — before your agent can spend money, ship a config, or sign a contract.
There are now ~60 tools for running Claude Code and Codex in parallel. The choice that matters isn't the tool — it's the control surface. Here's the decision.
Astra proved ten open math problems and handed over Lean 4 certificates a machine can check without trusting the model. You don't need a frontier lab to copy the pattern — here's the builder's version, with code, for making any long-running agent's output verifiable.
The transparency rules went live on August 2, 2026. If your product talks to users or generates media, you now owe two things: a disclosure users can see, and a mark machines can read. Here's the disclosure snippet, the C2PA signing command, and the deadline you can still miss.
DeepSeek retrained V4-Flash and shipped it under the same name and endpoint this week — zero migration, and zero warning that your production behavior just moved. Here's how to detect a swap you don't control, before your users do.
The store you pick today is the store you'll outgrow. Put a two-method interface in front of it now, and moving from a file to a service becomes a migration you run in an afternoon — not a rewrite you dread.
OpenAI turned ChatGPT into a login button on August 2. The decision pieces tell you whether to add it; none show you the wiring. Here is the whole flow — authorization-code + PKCE against auth.openai.com — with the redirect, the token exchange, and the exact three claims you get back, in one Node file.
Elicitation used to be a local-server luxury. The stateless core and Multi Round-Trip Requests finally let a remote server pause a tool call, ask the user for structured input, and resume — here's the code.
Both put an autonomous agent in your terminal. One is a free, model-agnostic, Linux Foundation project you point at any LLM; the other is a polished, opinionated agent wired to one lab's frontier models. Here's the decision, by what you actually optimize for.
Gemini CLI v0.53.0 landed an LLM triage orchestrator and a container build — but you don't need to wait for the built-in path. The headless flags to label, route, and comment on issues from a GitHub Action are already stable. Here's the whole loop, copy-paste.
Opus 5 gives you one model and a request-time effort knob. GPT-5.6 gives you three separate models at three prices. Same goal — spend less on easy work — but a dial economizes tokens while a menu cuts the per-token price, and that difference reshapes your caching, evals, and routing.
'Flash' used to be shorthand for the cheapest model. After last week's repricing it isn't — Gemini 3.6 Flash now costs about 10x the actual floor. Here's what a model's name stopped telling you about your bill.
One is a pytest for your prompts that runs on every PR; the other is where production traces go to be graded, annotated, and audited. Most teams eventually need both — the trick is knowing which loop each one closes.
Your provider invoice is one number. Cost per 1K tokens tells you nothing about which customer, feature, or job is bleeding money. Here's how to group per-call token spend into per-task cost with OpenTelemetry's GenAI conventions and Langfuse — with the exact attributes and code.
The overview posts told you 0.26 grew a memory hierarchy. This is the hands-on version — the real flags, a KV-bytes-per-token sizing rule, and the three metrics that prove offload is helping instead of hurting.
The first video model you can prototype on an API this afternoon and self-host later. Here's what it is, who made it, exactly how to get a clip out of it, and the license line that decides whether it's free for you.
Every agent-memory tutorial names a different set of things "memory." There are only two axes underneath, and once you can see them the vendor menu stops being confusing.
Supabase open-sourced a benchmark that runs Claude Code, Codex, and OpenCode against real containerized Supabase stacks. The launch numbers say the frontier models are close — and that skills, not model choice, close the last 20 points.
A rented H100 costs the same whether it runs flat-out or sits idle. A per-token API costs nothing when no one's calling it. That single difference — fixed vs variable — is the whole decision, and it has a number.
The moment you turn on prompt capture, your agent starts shipping user messages, API keys, and PII to a third party. Here are the three layers that let you keep the traces useful and keep the secrets out of them.
python-1.13.0 and dotnet-1.16.0 shipped July 30 with reusable session stores and full Foundry Responses persistence. The timing is the story: the protocol just pushed state out, and the framework is picking it up.
We told you to wait for the stable tag. It landed July 29. Here's the exact order of operations to migrate a self-hosted Langfuse instance across a destructive, one-way schema change without losing a trace.
The memory tool is now GA on the Messages API — no beta header. But it ships no database: Claude only *asks* to read and write files, and your code does the work. Here's the whole loop, plus the one line of validation that keeps it from reading your secrets.
The $3/M list price isn't what you actually pay. Kimi K3's cache-hit input is $0.30/M, and with the reported ~92% cache-hit rate the effective input cost lands near $0.52/M — but only if you structure prompts so the cache actually hits. Here's the copy-paste setup and the one ordering rule that decides your bill.
One agent run is dozens of billable spans, so tracing gets expensive fast. Head sampling saves money by throwing away the failures you most need. Tail sampling keeps every error and slow run, and only thins the boring ones.
Point the OpenAI SDK at localhost, load a tool-capable model, and your agent loop runs on your own hardware with zero code changes. Here's the whole path — plus the three gotchas that decide whether tool calls actually work.
Two-way GitHub sync makes it look like you already own the code. You mostly do — but the platform is still the source of truth, your secrets aren't in the repo, and your database might not leave with you. Here's the exact eight-step migration, in the order that doesn't break production.