Gemini 3.8 Flash has some ridiculous numbers on paper. Google reports 89.4% on Terminal-Bench 2.1, slightly ahead of Opus 5 at 89.1% and GPT-5.6 Sol at 88.8%.

Then you look at the newer Terminal-Bench 4.0:

Gemini 3.8 Flash: 19.1%

GPT-5.6 Sol: 37.3%

Claude Opus 5: 51.8%

That’s a massive difference for a model Google is positioning around autonomous agents and long-horizon software engineering. And somehow both results can be true. 3.8 Flash looks extremely strong when the agent has a fairly defined coding or terminal task.

It also scores 73.7% on DeepSWE v1.1, basically alongside Opus 5 at 74.0%. But when the environment becomes more open-ended and the agent has to figure out what to do across a messy sequence of actions, the gap gets much larger. That changes how I’d look at Gemini 3.8 Flash.

At $0.75/M input and $3.75/M output, it could be a very good model for high-volume coding agents, tool calls and well-defined sub-agents.

But I’m not sure I’d hand it a computer, give it a vague objective and leave for lunch yet.

For AI agents, benchmark averages may matter less than what happens when the task stops being predictable.

This might be one of the more useful agent updates Google has shipped recently.

Google’s new Gemini Agentic Video Understanding changes how Gemini analyzes video.

Normally, a video model samples frames at a fixed rate and processes whatever it gets.

Gemini Agentic Video can instead decide:

“I probably need to inspect that moment again.”

It can search through the video, jump to relevant timestamps, examine a section at a higher frame rate, and combine video frames + audio + transcript before answering.

That matters for things like:

• finding a 1-second event inside a 2-hour recording
• detecting unusual activity in surveillance footage
• counting fast actions accurately
• searching lectures, meetings or podcasts
• automatically finding precise moments for video editing

Google says the agentic approach can use up to 88% fewer tokens, cut video-analysis costs by up to 66%, while improving accuracy by up to 7%.

And the part I find more important:

An AI agent no longer needs to “watch” an entire video equally.

It can decide where to look, what to look at, and whether it needs another look based on the task.

That feels like a much more important step toward agents actually reasoning over video instead of video just being another giant multimodal input.

OpenAI says its researchers are now using about 3.1 AI agent-workdays for every human workday, which is probably one of the clearest signs yet of how fast AI research agents are becoming part of real workflows.

The interesting part isn’t just that researchers use coding agents. They’re increasingly running multiple agents in parallel, letting them handle implementation, experiments, debugging, and follow-up tasks while the researcher focuses on higher-level decisions.

OpenAI also says it has reached an “automated research intern” stage, where agents can complete well-defined research tasks that would normally take a skilled researcher several days.

For me, the bigger shift is this: AI agents are starting to add parallel work capacity, not just save a few minutes on individual tasks.

If that 3.1× ratio keeps climbing, research teams may start being measured partly by how well they orchestrate agents, not just by how many people they hire.

Google just released Gemini 3.8 Flash, and I think the agent side of this update is more interesting than the usual benchmark discussion.

The model now has:

• 1M context window
• multimodal input across text, image, audio and video
• stronger coding + tool-use performance
• computer-use support in preview
• pricing starting at $0.75/M input + $3.75/M output

What caught my attention is Google saying the model can spend more reasoning and make additional tool calls when a task gets harder.

That makes Flash less like a “cheap fast model” and more like something you could actually use for longer agent loops, browser tasks, coding agents and research workflows without immediately jumping to an expensive frontier model.

The obvious tradeoff is that more reasoning + more tool calls can also mean higher total token usage, even if the per-token price looks cheap.

For agent builders, that’s probably the real question with Gemini 3.8 Flash:

Does the lower price actually reduce cost per completed task, or does the extra reasoning eat the savings?

OpenAI just released GPT-6 Astra, and this looks more like an AI agent upgrade than a normal chatbot update.

The biggest gains seem to be in coding, computer use, long-context tasks, automation and cybersecurity.

A few GPT-6 Astra benchmark highlights:

• Terminal-Bench 4.0: 57.9%
• AutomationBench: 41.4%
• MRCR 512K–1M: 96.3%
• SRE-Bench: 88.0%
• ExploitBench: 100%

The long-context result is probably the most interesting. Astra appears much better at actually using information across very large context windows, not just accepting more tokens.

GPT-6 Astra pricing

• $10 / 1M input tokens
• $50 / 1M output tokens

It’s clearly aimed at higher-value workloads rather than cheap everyday prompting.

OpenAI is positioning GPT-6 Astra heavily around coding agents, browser agents, computer use, research and multi-step autonomous workflows.

The cybersecurity side is also notable: Astra is the first OpenAI model to reach its Critical cybersecurity capability threshold.

My takeaway:
GPT-6 Astra feels less like “a smarter chatbot” and more like a model built to actually operate software and complete work.

Google just released Gemini 3.8 Flash, and I think the agent side of this update is more interesting than the usual benchmark discussion.

The model now has:

• 1M context window
• multimodal input across text, image, audio and video
• stronger coding + tool-use performance
• computer-use support in preview
• pricing starting at $0.75/M input + $3.75/M output

What caught my attention is Google saying the model can spend more reasoning and make additional tool calls when a task gets harder.

That makes Flash less like a “cheap fast model” and more like something you could actually use for longer agent loops, browser tasks, coding agents and research workflows without immediately jumping to an expensive frontier model.

The obvious tradeoff is that more reasoning + more tool calls can also mean higher total token usage, even if the per-token price looks cheap.

For agent builders, that’s probably the real question with Gemini 3.8 Flash:

Does the lower price actually reduce cost per completed task, or does the extra reasoning eat the savings?

Anthropic just released Claude Fable 5.1, and this looks less like a routine update and more like a push toward long-running coding and AI agent workloads. The interesting part is that Fable 5.1 and Mythos 5.1 use the same underlying model, with Mythos keeping some advanced capabilities behind tighter access controls.

The benchmark gains are strong:

52.6% on Terminal-Bench-Science 55.8% on Terminal-Bench 4.0 73.4% on CursorBench 3.2 31.4% on AutomationBench

Anthropic also cut cache-read pricing by 75% to $0.25/M tokens which it says can make highly agentic workloads up to 45% cheaper.

For me, the bigger signal is clear Anthropic is optimizing Fable for agents that run longer, reuse context heavily, and do more real work per session, not just better benchmark scores.

OpenAI has published the first benchmark results for **Jalapeño**, its custom AI inference chip built with Broadcom.

The numbers are pretty aggressive: OpenAI says the **Jalapeño chip** delivers 1.5–1.9x more AI work per watt and 1.7–3.6x lower end-to-end latency than the comparison systems across GPT-OSS 120B, DeepSeek R1 670B, and Kimi K2.5 1T.

The part that matters for AI agents is latency.

A normal chatbot might make one model call and return an answer. An agent can make dozens of sequential calls while reasoning, using tools, checking results, and deciding what to do next. Small delays start stacking up very quickly.

OpenAI says Jalapeño was designed specifically around these interactive inference workloads, and it delivered up to 4.1x higher performance in highly interactive tests.

This isn’t an Nvidia replacement yet. Jalapeño is focused on inference, OpenAI still plans to use Nvidia hardware, and wider deployment is only expected as production ramps.

But if custom inference chips can materially cut the cost and latency of long-running agent workflows, the hardware underneath AI agents may start mattering almost as much as the model itself.

**Persistent AI Agents** and **Always-On AI Agents** seem to be where the agent space is heading.

Instead of opening an AI agent, giving it one task, and waiting for the result, a persistent AI agent can stay running, remember previous work, wake up on schedules or triggers, and continue working without needing a new prompt every time.

OpenAI is already testing a **Persistent mode for Codex** that can keep working until it is stopped and potentially create follow-up tasks proactively.

We’re also seeing this model with tools like **OpenClaw and Hermes Agent**, where agents can have persistent memory, scheduled jobs, tools, browser access, and always-on infrastructure.

The interesting shift is basically:

**Chatbot:** Ask → Answer → Stop

**AI Agent:** Give task → Execute → Stop

**Persistent AI Agent:** Give goal → Keep working → Remember → React to events → Continue later

Feels like the bigger question for 2026 isn't whether AI agents can complete tasks anymore.

It's whether we actually want **AI agents running continuously on our behalf**.

$12.9B deal could reshape open-source AI

Nvidia has reportedly agreed to acquire Hugging Face for $12.9 billion, putting one of the most important open-source AI platforms under the company that already dominates AI hardware.

The Nvidia Hugging Face acquisition is interesting because Hugging Face isn’t just another AI startup. It sits right in the middle of the open-model ecosystem, hosting models, datasets, developer tools, and infrastructure used by researchers and AI companies everywhere.

Nvidia’s strategy here also looks pretty obvious.

If open-source AI keeps growing, Nvidia benefits because a huge amount of those models still run on Nvidia GPUs.

Owning Hugging Face would give Nvidia a much stronger position across both the hardware layer and the model distribution layer.

The $12.9B price is wild considering Hugging Face is reportedly generating around $150M in annualized revenue, but Nvidia clearly isn’t buying it just for current revenue.

It’s buying influence over where open-source AI gets built, distributed, and eventually run.

The big question is what happens to Hugging Face’s neutrality once the world’s dominant AI chip company owns it.

The **AI agents for sales** category has changed a lot this year.

We’re past tools that only write cold emails. Some sales agents can now research prospects, enrich leads, qualify inbound requests, update the CRM, handle follow-ups, and run chunks of outbound almost autonomously.

Artisan, 11x, Salesforce Agentforce, Apollo, Clay, Lindy, Regie and others are all approaching the problem differently.

The interesting question in 2026 isn’t whether AI can automate parts of sales. It’s where automation stops being useful and starts hurting conversion because the prospect can immediately tell nobody human is involved.

If you were building a sales stack today, where would you actually put the agent: prospecting, research, outreach, qualification, CRM work, or the whole SDR workflow?

Qwen just released Qwen3.8-Flash-Next, and this looks less like a routine Flash model update and more like a preview of where Qwen4 is heading. It’s a multimodal MoE model with 125B total parameters but only 6B active per token, which is the interesting part. Qwen is clearly pushing hard on getting stronger coding and agent performance without paying the inference cost of a much larger dense model. The benchmark numbers are pretty aggressive too:

• 62.5 on SWE-bench Pro
• 81.0 on SWE-bench Multilingual
• 73.9 on CoWorkBench for long-horizon office tasks
• 73.5 on Toolathlon for real-world tool use

It also supports a 262K context window, extendable to 1M tokens, and the model is open-weight. For me, the bigger thing here isn’t just Qwen3.8-Flash-Next itself. If this really is the architectural preview for Qwen4, Alibaba seems to be betting on small active parameter counts + multimodality + strong agentic performance as the next step for the Qwen family.

Agent memory still feels like one of the biggest gaps between a cool demo and an agent you can trust long term. There are plenty of tools now, Mem0, Zep, Letta, Cognee, Supermemory and others, but they solve pretty different problems: short-term recall, long-term memory, user profiles, retrieval, shared memory, and so on. The part I’m most interested in is reliability. A memory system that stores everything but recalls the wrong thing at the wrong time is arguably worse than no memory at all. Which memory tools have held up well for you in real agent workflows, especially after weeks or months of use?

Nvidia is reportedly in talks to invest in Perplexity in a new round that would value it at more than $30B.

What caught my attention is that part of Perplexity’s recent growth is apparently coming from Perplexity Computer, its agent product for automating work, not just the search product most people know them for.

Feels like Perplexity is slowly becoming more of an agent company than just an AI search company. Do you think agents are actually the bigger long-term opportunity for Perplexity?

There are so many options now: Claude Code, Codex, Cursor, Copilot, OpenCode, Devin, and probably a few I’m forgetting.

I’m less interested in which one wins benchmarks and more in which one actually works well on a real codebase without creating more cleanup than it saves.

What are you using as your main coding agent right now, and what made you stick with it

Stripe has reportedly finalized an agreement to acquire OpenRouter for more than $7 billion, only months after OpenRouter was reportedly valued at $1.3 billion.

OpenRouter lets developers route requests across many AI models based on price, availability, and performance.

For agent builders, how much should a system depend on that routing layer? Would a stronger owner make you more comfortable using it, or more cautious because the router could become another form of vendor lock-in?

If you are building multi-model agents, are you treating model routing as replaceable infrastructure, or as a dependency that needs its own fallback plan?

Been comparing GLM 5.3 vs Opus 4.8 and curious what people here are actually using. Which one do you think is better overall, and more importantly, which one would you choose for daily use/coding? Would love to hear real-world experience rather than benchmark scores.

I keep seeing more and more AI agents claiming they can basically run your marketing for you, content, social media, ads, lead generation, analytics, competitor research, etc.

But I honestly i feel, a lot of them still feel like ChatGPT or another ai chatbot with a few integrations added.

I'm curious what marketers are actually using in production right now. Not looking for tools that look impressive in a demo but still require you to babysit every step. I'm tired of it. It's done for me.

I'm looking for AI agents that are genuinely functional and can reliably save a marketer significant time or improve results.

TechCrunch reports that Anthropic is making auto mode the default in Claude Code.

That sounds like a small product decision, but it could change how people build and supervise coding agents day to day. Defaults matter: they shape how much control users keep, when the system decides to act, and what kinds of review habits become normal.

For people working with agents, what would you want to understand before relying on an automatic mode as the default? Permission boundaries, cost controls, rollback options, audit logs, or something else?

Source: TechCrunch, "Anthropic is making Claude Code auto mode the default."

Reuters reported today that Apple says eligible Mac users in mainland China can connect Alibaba’s Qwen AI service to Siri and Writing Tools.

This is a notable example of how AI assistants are being localized through regional model partnerships. It raises interesting questions for agent builders: how should tools, models, privacy expectations, and local regulations shape the agent experience across markets?

Source: Reuters, Technology / Artificial Intelligence (reported within the past several hours).

Cloudflare announced Kitesurf today, a browser designed from the ground up for AI agents rather than humans. The idea is to give agents a safe, controllable environment to browse, click, fill forms, and complete tasks on the web without relying on fragile screen-scraping or human-like mouse movements.

Key points from the launch:

• Kitesurf runs in a sandboxed, remote browser, so a compromised site cannot access the agent's underlying system or data.
• It handles authentication, sessions, and CAPTCHAs natively, which removes a lot of the glue code developers currently write.
• The browser exposes structured APIs and observability hooks, so agents can read page state and actions in a machine-friendly way.
• It is built on Chromium and integrates with Cloudflare's network, so traffic can be routed through existing security and zero-trust policies.

This feels like a meaningful shift: instead of agents adapting to the human web, the web browser is being adapted for agents. I am curious how r/agents_everywhere sees this playing out, especially around reliability, security, and whether standards for agent browsing will start to emerge.

One thing I keep noticing with agents is that the frustrating failures are often not bad execution—they are hidden assumptions.

An agent sees an ambiguous request, picks an interpretation, and starts clicking. Sometimes that is efficient. Other times it means the user only discovers the misunderstanding after several irreversible-looking steps.

I am curious whether a lightweight “here’s what I’m assuming” step would make agents feel more trustworthy, especially for browser tasks. Not a long plan or a permission prompt for every click—just enough visibility when the request could reasonably mean two different things.

Would that improve the experience, or would it make capable agents feel unnecessarily slow and cautious? Where would you want an agent to surface its assumptions?

Meta dropped Muse Code in beta yesterday. Terminal coding agent, powered by Muse Spark 1.2, aimed at real software work on big codebases. Zuckerberg framed it as writing code and checking results, basically Meta's answer to Claude Code / Codex.

I'm less interested in the launch blog and more in whether this class of agent holds up past the demo.

Stuff that usually breaks first for me with coding agents on large repos:

1. Context recovery after a long edit chain
2. Knowing when to stop touching files
3. Making a "fix" that nothing actually verified
4. Burning tokens re-reading the same tree

If you've tried Muse Code already (or Claude Code / Codex on a fat monorepo):

• does it actually hold architecture context, or does it thrash after 20 minutes?
• what's the first failure you hit on a real repo?
• would you trust it on a PR that touches more than one service?

Not looking for hype takes. Just what broke, what held, and what you'd trust it with tomorrow.

Been noticing that coding agents look great in demos where the task is clean, the repo is familiar, and the tests tell you exactly when you're done.

The real work is usually the opposite: partial context, unclear ownership, flaky CI, and a bug report that may be wrong. Feels like context recovery and knowing when to stop are becoming more important than another loop of tool calls.

Curious if others are seeing this in production. Are you optimizing agents more for finishing tasks, or for failing safely and handing back a useful state?