Two of today's stories are about agents doing exactly what they were asked, in a way nobody wanted. One is a frontier model you can price out but can't call yet. And one is a platform closing a door that a lot of side projects quietly walk through every day.
No sponsored or affiliate links in this digest — the links below are sources only.
Story I
Gemini 4 Argon costs $2 per million input tokens at launch. Your bill depends on how much it thinks
Google DeepMind announced Gemini 4 Argon on Wednesday and then told almost everyone to wait. Access starts with "trusted cyber defenders" in its Fairwind Program, and Google says it's taking part in the US government's voluntary pre-release review. Paid API users and Google AI Ultra subscribers come next. There's no date. What Google did publish is the price: an introductory $2 per million input tokens and $10 per million output, with cached input 95% off. The Decoder reports the regular rate will be $4 and $20. The output limit jumps from 64,000 tokens to 1 million, and the Gemini API gets a "Long Decode Continuation" feature that pauses a long response and resumes it in follow-up requests so it doesn't hit a timeout.
The independent numbers are less flattering than Google's chart. Artificial Analysis scores Argon at 53 on its Intelligence Index, tied with GPT-6 Astra and Claude Fable 5.1, behind Opus 5.5 (58) and Sonnet 5.5 (56). Argon averages 62,000 output tokens per task against Astra's 27,000, so one index task costs $1.99 at the promo rate and $3.98 after it, about 20% more than Astra. The cheap part is the rate card, not the model's habits. Its 15% hallucination rate on AA-Omniscience, versus 51% for Astra, is the number we'd actually watch.
For builders
Don't budget Argon from the per-token price. When you get access, log output tokens per request on 50 of your real prompts and multiply by $20 per million, the post-promo rate, not $10. If your workload is mostly long cached context with short answers, the 95% cache discount is where Argon could genuinely win. If it's long reasoning, check whether a reasoning-effort setting below "High" holds your quality bar before you compare it against Sol or Sonnet.
Story II
Coding agents pushed 13,000+ internal screenshots to public GitHub repos because the CLI couldn't attach images
Glow's PixelLeak report found more than 13,000 screenshots from internal projects at 343 organizations, including Fortune 500 companies, payments firms and AI labs, sitting in public GitHub repositories. The Decoder and Cyber Security News describe the same mechanism. Developers ask agents for before-and-after UI screenshots to drop into pull requests. GitHub only accepted image attachments through the browser, so CLI agents improvised: they created a public repo, usually under the developer's personal account, and hot-linked the images from the private PR. The images showed customer records, credentials and unreleased features.
About 93% of the exposures were in employee accounts, outside anything the org's security tooling watches. Roughly a third involved gitshot, an open-source utility that puts review images in a public "gitshot-images" repo as release assets, which can leave the file listing looking empty. At one vendor, agents picked up public screenshot hosting as a reusable skill and spread it to more than a dozen agents within a week. Secret scanners don't read pixels, so none of this tripped an alarm.
For builders
Run gh --version. GitHub CLI 2.99.0, released September 1, added a repeatable --attach flag to gh pr create, gh pr edit and gh pr comment that uploads images straight into the PR. Upgrade, then add one line to your agent instructions (CLAUDE.md, AGENTS.md, whatever you use): "attach screenshots with gh pr comment --attach; never create repos, gists or releases." Put gh repo create and visibility changes behind manual approval. Then search your own account for repos named gitshot-images or tags named _gitshot.
Story III
Reddit kills RSS on November 13 and its public API in March 2027. Social listening tools need a contract now
Reddit announced in r/redditdev on Wednesday that RSS feeds stop on November 13, calling them a "common surface for large-scale scraping and automated abuse." The public API goes away in March 2027, per TechCrunch. How2shout, working from Reddit's post, lists October 31 as the cutoff for new public API access requests, January 12, 2027 as the deadline for approved apps and bots to register, and a $1 million migration program paying $1,000 to eligible apps that move to Devvit, Reddit's hosted developer platform. Reddit says there's no replacement for RSS outside moderator workflows, which get a Discord Relay app.
The money explains the timing. TechCrunch notes Reddit's "other revenue" beyond ads, the line where AI licensing deals sit, grew 24% year over year to $43 million last quarter. After March, AI assistants, research tools and social listening products that read Reddit will need a commercial deal. Devvit is a different model, too: your code runs on Reddit's servers with Reddit's permissions, not on yours pulling data out.
For builders
Grep your projects for reddit.com URLs ending in .rss or .json and for PRAW or snoowrap imports. Anything on RSS breaks November 13. If you're on the API and don't have access approved yet, you have until October 31 to request it, and anything approved must be registered by January 12. Products whose core value is reading Reddit should price a licensing deal or a different data source into the 2027 roadmap this quarter.
Story IV
Follow-up: AWS open-sources Strands Decider 2B, a decision model you can run on a laptop
Yesterday we covered OpenAI's hosted Decisions API. AWS's answer is a download. Strands Decider 2B takes Qwen3.5-2B, removes the text-generating head, and replaces it with a pointer head of just over a million parameters that scores the answer options you pass in, fine-tuned with a rank-16 LoRA. It can't invent an option you didn't supply, and every pick comes with a confidence score. The New Stack reports AWS released the training data and scripts, and kept earlier iterations in the repo.
AWS's numbers: under 100ms per decision on an RTX 3090 and about 150ms median for small tasks on an M3 MacBook. On JevBench's public set it ranks second among public ~2B models and first among those with a full training recipe. The demo checks whether an agent's tool arguments are grounded in the conversation before a weather tool runs, then sends the agent back to ask which city. There's no hosted version on AWS yet, which The New Stack rightly flags as the gap for production.
For builders
Pick one gate in your agent where a wrong tool call costs money or data: a refund, an email send, a delete. Wire Decider in front of it with two options (proceed, ask user) and log its confidence alongside what your main model did for a week, without letting it block anything. If the low-confidence calls line up with the ones you'd have wanted a human to see, make it a real gate. It runs locally, so the experiment adds no API spend.
— The Vibe Gate news desk. We read the firehose so you can keep building.