If you blinked in the last six months, you might have missed the moment AI stopped being a fancy chatbot and started actually doing things for you. Not just answering questions. We're talking about AI tapping through apps, writing full codebases, managing tasks, and spinning up other AI agents to handle subtasks. All while you grab a coffee.
Welcome to the age of AI agents. Things are moving fast from every direction: hardware, software, coding, and startups alike.
Let's start with something physical, because that's unusual in a world of pure software announcements.
Blue, a Y Combinator Summer 2025 startup, is building what might be the first voice assistant that can actually control every app on your iPhone. Not just answer questions about them. The idea is deceptively simple: you talk to it, and it taps, types, and swipes through your real apps on your behalf. No special integrations needed for each app. No rewriting the whole ecosystem.
The magic lies in a tiny USB-C dongle called the "Bud" that plugs into your phone and gives the AI precise input control. Think of it as the AI's hand. People are already using it to clear inboxes, pay bills directly from email, share files, and handle repetitive phone flows, all while their own hands are occupied.
The team behind Blue isn't a bunch of fresh graduates either. Omar Abdelaziz, the co-founder and CEO, led Google Assistant's transition to large language models and holds one of the earliest patents in LLM-based computer control. His co-founders include a former Google DeepMind design lead and the engineer who helped ship Apple Vision Pro. These are people who've built systems used by billions, now going all-in on the idea that your phone's AI should do things, not just say things.
Omar was so committed to getting the product into real hands that he personally hand-delivered 10 free Blue devices to early users. That's the kind of founder energy that signals a team which genuinely believes in what they're building. The best feedback, after all, comes from watching someone actually use it.
On the software side, a tool called SlayZone quietly launched and started picking up steam among developers who run multiple AI coding agents at once.
Here's the problem it solves: if you're a developer using AI agents like Claude Code, Codex, or Gemini to write code, you quickly realize managing them is chaotic. Which one is working on what? Where's the code? Did it run the tests?
SlayZone is essentially mission control for your agents. Every task card in its Kanban board hides a live terminal, a browser, git management, and more. You create a task, open the card, and your agent is already inside working in a real terminal session, not a sandboxed demo. SlayZone watches your agents and automatically tracks each task's status: idle, working, or waiting for your input. Each task lives on its own isolated code branch, so there are no messy conflicts from agents tripping over each other's work.
It's a small but telling product. The fact that a dedicated "AI agent management dashboard" now exists, and that developers actually need one, says everything about where the industry is headed.
Here's a quote that landed hard in the tech world recently. Elvis Saravia, an AI researcher and founder of DAIR.AI who publishes one of the most widely-read AI agent newsletters around, posted something that resonated with a lot of people:
"I am at the point where my AI agents have become so good and fast at various complex tasks that I've become the bottleneck. Hard to make use of and keep track of all the insane value my AI agents are creating. AI agent managers are going to be in high demand soon."
Read that again. A leading AI researcher is saying he is now the slow part of the system. His agents are outpacing his ability to direct and review their work.
That's not a fear about the future. That's a live description of right now. And it points to a new kind of role that barely has a name yet: the AI agent manager. Someone who doesn't write code or run research directly, but who coordinates, reviews, and steers a team of AI agents working in parallel. Elvis's newsletter, AI Agents Weekly, tracks this space every week, covering everything from new model releases to cutting-edge papers on how agents handle memory, context, and long-running tasks.
His latest research dig explores a very practical question: do AGENTS.md files (instruction files developers place at the root of a project to guide coding agents) actually improve agent performance? The answer is nuanced. Human-written ones help a little, LLM-generated ones actually hurt slightly, and all of them add over 20% to inference costs. Even small, practical questions like this are now worth studying carefully. That's how serious the field has gotten.
Speaking of coding agents, Addy Osmani, an engineering leader at Google and one of the most thoughtful voices on AI and software development, has been writing extensively about how the developer role is changing.
His core argument: AI coding assistants have moved from novelty to necessity. Up to 90% of software engineers now use some kind of AI for coding. But the more important shift isn't about adoption numbers. It's about what the job actually is now.
As Osmani describes it, a new paradigm is emerging where engineers leverage fleets of autonomous coding agents. The role is evolving from implementer to manager, from coder to conductor, and ultimately to orchestrator. Senior engineers, he says, are seeing the writing on the wall: the job is shifting from "How do I code this?" to "How do I get the right code built?" It's a subtle but profound change.
The tools already reflect this. GitHub's Copilot agent lets one engineer supervise many AI "juniors" working in parallel. Google's Jules is a fully autonomous coding agent that reads your codebase, formulates a plan, gets your approval, and then executes changes on its own. Claude Squad is an open-source terminal tool that spins up several Claude Code instances running side by side, essentially multiplying output by running tasks in parallel.
Osmani also highlights the risks. At Anthropic, engineers adopted Claude Code so heavily that around 90% of the code for Claude Code is now written by Claude Code itself. The AI is literally building itself. That level of output creates a new challenge: individual productivity surges but review workload spikes too. One study found that individual output jumped 98% in high-adoption teams, while pull request review time increased by as much as 91%. More code gets written, but someone still has to read it, understand it, and catch what the AI got wrong.
The engineers thriving are those who've shifted to architectural oversight and quality control. Those struggling are the ones treating AI like a faster keyboard. The work is the same in spirit: build good software. But the path to get there looks completely different now.
Put all of this together and a clear picture emerges.
AI agents aren't a future technology. They're products people are paying for, shipping on, and building companies around right now. There's a physical device that lets an agent control your phone. There's a dashboard built specifically for managing teams of coding agents. There's a leading AI researcher saying his agents are outpacing his ability to keep up. And there's a generation of software engineers being told by people with decades of experience that their core job description just changed.
The startups in Y Combinator's Summer 2025 batch reflect this shift: over 60% explicitly reference AI in their pitch, and the biggest cluster is agentic AI, meaning autonomous systems that perform tasks rather than just provide information. Roughly half the companies in the S25 batch are building agents or AI copilots that do things. As observers of the cohort have noted, if Winter 2025 was the rise of the AI agent, Summer 2025 was the entrenchment of AI agents across every vertical.
Tools like SyncMyTime are already helping the humans behind these agent teams stay coordinated across timezones, a small but essential piece of the remote-first workflows that AI is accelerating.
What changes for regular people? The apps you use are going to start doing more without being asked. Your tools are going to feel less like software and more like a quiet team working in the background. One that never takes a break.
What changes for developers and tech workers? The job isn't disappearing. It's transforming into something that requires less typing and more thinking. The question isn't "will AI take my job?" It's "am I learning to direct agents, or am I waiting to be replaced by someone who already does?"
The agents are here. The only remaining question is who's going to be the conductor.
