From a new frontier coding model out of xAI to a sharp privacy investigation targeting OpenAI’s ad platform, today’s AI headlines span the frontier of model releases, agent infrastructure, and data-privacy scrutiny. Here are the five stories driving the conversation this morning.
xAI Ships Grok 4.7, Its Most Capable Coding and Knowledge-Work Model
SpaceXAI announced Grok 4.7 on September 21, describing it as its most powerful model yet for coding and knowledge work. The model is “twice as fast, at half the price of comparable models,” and is served at the same price and speed as Grok 4.6: $2 per million input tokens and $6 per million output tokens, with a fast variant at twice the output speed for twice the price.
Under the hood, Grok 4.7 uses a new, larger base model than 4.6 and was trained with a longer reinforcement-learning run weighted toward problems that take many hours to complete. It is better at verifying its own work, managing longer context, and natively understands the Grok Bot harness. On benchmark comparisons, Grok 4.7 hit 46.3% on CursorBench 4.0 (versus 40.4% for Grok 4.6), 71.0% on DeepSWE v1.1, and 64.0% on the electrical-engineering EEBench.
The release also debuts an entirely new safeguard stack, leading on refusal rates and jailbreak resistance — including the strongest score xAI has seen on LatchBio’s biosafety benchmark at 62.4%, and allowing just 3.3% of risky dual-use prompts through on HackerBench v0.3. Grok 4.7 is available today in Cursor and Grok Build, through the Grok API, and via model routers and cloud platforms.
Google’s AX: An Open Agentic Orchestrator for Scaling Agent Workloads
AX (agentexecutor.io) is an open-source agentic orchestrator built by Google engineers, and it climbed to the top of Hacker News this week with more than 640 points. Its pitch: “Declare an agentic task. AX runs it at scale,” sandboxing each task, wiring up its workspace, and fencing its network so you can run many agents per cluster.
The project centers on four declarative primitives — Task (isolated execution with CPU/memory limits), Workspace (easy Git/MCP/skills setup), and related constructs — so that untrusted agent code runs in a sandbox that is cheap to create, suspend, and throw away. Workflows are defined in plain YAML files and managed with the ax CLI.
Commenters noted the natural fit with Google’s broader agent tooling, such as Antigravity and Jules, and welcomed an open option for the growing stack of agent sandbox and orchestration startups. Others were quick to caution that while it was developed by Google employees, the project does not necessarily carry full official Google backing.
Investigation: OpenAI’s Ad Collector Ties Your Web Browsing to Your ChatGPT Account
A detailed investigation published this week alleges that OpenAI’s ad platform connects what you do on ordinary websites to your ChatGPT account via an identifier called __obi. The mechanism, documented at bzr.openai.com (OpenAI’s internal “bazaar” ads system), begins when ChatGPT generates a JWT that binds a stable identifier to your account, then sets the __obi cookie scoped to .openai.com.
Advertisers that run OpenAI ad pixels load a small SDK that transmits the cookie — along with page data such as products searched, articles read, and purchase behaviors — back to OpenAI’s servers. The author says they reproduced the full mechanism on their own phone, verifying it with two independent capture methods and cross-checking months of traffic spanning 936 distinct advertiser pixels across 1,029 hostnames, including Chewy, Wayfair, ThriftBooks, Eventbrite, HelloFresh, Coursera, and SeatGeek.
Even when logged out, an anonymous identifier per device was observed persisting at least 27 days. The report also notes the SDK harvests identity from form fields and tag-manager buses, hashing email and phone, while sending some geo data in the clear. OpenAI’s cookie policy lists __obi as an analytics cookie with a one-year lifespan. The story drew sharp community reaction over the precedent of running “standard adtech” inside an AI chat product.
Kev: Small, Self-Trainable Decision Models Built on Qwen3.5
Kev is a family of small “Jev-like” decision models you can train and run yourself. Released by Jared Palmer, the project provides 0.8B, 4B, and 9B models built on Qwen3.5 and based on the architecture described in “Jev’s Architecture Unmasked,” with full training code, frozen evaluation suites, and Apache-2.0 licensing.
Kev answers yes/no, multiple-choice, and rating questions in a single request, with questions sharing the input text but kept isolated from one another. It runs on CUDA, ROCm, and Apple Silicon — the 4B and 9B models fit a 32GB Mac using bf16 — and its API matches TypeSafe’s System One, so their Python SDK can point at your local server. A Hugging Face Spaces demo lets you try Kev-4B and Kev-0.8B in the browser with no install.
The project’s popularity reflects a wider community appetite for small, open, locally-run models, though commenters debated whether fine-tunes on RLHF-trained Qwen base models can truly be called “Jev-like,” given Jev’s own reliance on RLCD training.
macOS 27: Users Seek Workarounds to Avoid Downloading AI Models
Early macOS 27 testers are hitting a storage surprise: the OS downloads large foundational AI models locally to power the rebuilt Siri and other on-device features. A workaround posted to the macOS Beta subreddit — showing users how to prevent those downloads and reclaim disk space — drew more than 220 points on Hacker News and lightened a debate about user choice.
Commenters split between those eager for the new on-device Siri (noting it is handy for search and local actions) and those frustrated at the lack of an explicit opt-out, with several saying they will hold off upgrading until Apple offers a real choice. Worth noting: the foundational models can be used by more than Siri — apps, shortcuts, and other tools can call them for local inference — so the trade-off is between local capability and hundreds of megabytes of storage.
That’s today’s slice of the AI world — from frontier model benchmarks to a privacy deep-dive on OpenAI’s ad stack, small open models, and the storage realities of on-device AI.