The AI arms race just got a $40 billion infusion, your next coworker might be a cluster of agents arguing in Slack, and HuggingFace open-sourced an ML engineer that works for free. Welcome to the tech news roundup for April 25, 2026 — where the line between "startup" and "science experiment" gets thinner every week.
The AI model wars just went nuclear. DeepSeek dropped v4, OpenAI countered with GPT-5.5, and HuggingFace open-sourced an AI intern that does your ML engineering for you. Meanwhile, a viral post about Claude's declining quality hit 550+ upvotes on Hacker News — a reminder that not everyone's winning in the AI gold rush. Here's your tech news roundup for April 24, 2026.
Meta description: Vercel released an open CLI that lets you install reusable "skills" into any AI coding agent — Claude Code, Cursor, Copilot, and 40+ more. Here's why it matters and how to use it.
If you've used more than one AI coding agent — Claude Code, Cursor, Copilot, Windsurf, Codex — you've probably noticed something annoying: each one needs its own setup. Your carefully crafted instructions, tool configurations, and workflow rules don't transfer. Switch agents, start over.
And if you're a team? Multiply that pain. Every developer configures their own agent differently. Consistency is a pipe dream.
This is the problem Vercel's skills CLI was built to solve.
Vercel Labs released an open-source CLI (15.5k ⭐ and climbing) that does for AI agents what npm did for JavaScript packages:
npx skills add vercel-labs/agent-skills
One command. That's it. The CLI pulls skill definitions from any GitHub repo and installs them into your coding agent's config directory.
A "skill" is just a SKILL.md file with YAML frontmatter — a name, a description, and instructions the agent follows when that skill is relevant. Think of it as a reusable prompt template that any supported agent can understand.
The CLI supports 43+ coding agents out of the box — Claude Code, Cursor, GitHub Copilot, OpenClaw, Gemini CLI, Windsurf, Codex, Cline, Amp, and dozens more. Each agent stores skills in a different directory (.claude/skills/, .cursor/skills/, .copilot/skills/, etc.). The CLI handles the mapping automatically.
Install once, use everywhere. Your team can standardize on specific skills regardless of which agent each developer prefers.
Skills follow the Agent Skills specification — a standardized format that any agent can adopt. This isn't a Vercel-only thing. It's an open ecosystem where:
The spec is deliberately simple: YAML frontmatter for metadata, Markdown for instructions. No build step, no compilation, no vendor lock-in.
The skills.sh directory already lists skills from Microsoft Azure (4.4M+ installs), marketing skill packs, Convex integration skills, and hundreds of community contributions. It's early, but the growth curve looks familiar — much like npm's early days.
# From a GitHub repo
npx skills add vercel-labs/agent-skills
# A specific skill from a repo
npx skills add vercel-labs/agent-skills --skill frontend-design
# Install globally (available across all projects)
npx skills add vercel-labs/agent-skills -g
# Target specific agents
npx skills add vercel-labs/agent-skills -a claude-code -a cursor
# List what's installed
npx skills list
# Search for skills
npx skills find typescript
# Update to latest
npx skills update
# Create your own
npx skills init my-skill
A skill is just a directory with a SKILL.md:
---
name: deploy-to-vercel
description: Deploys the current project to Vercel with proper env vars and preview URLs
---
# Deploy to Vercel
## When to Use
When the user asks to deploy or preview the project.
## Steps
1. Check for vercel.json or next.config
2. Run `vercel --prod` for production or `vercel` for preview
3. Share the deployment URL with the user
Push it to GitHub, and anyone can install it with npx skills add your-username/your-repo.
Vercel Skills isn't happening in isolation. It's part of a broader shift:
Together, these form the infrastructure layer that turns AI coding agents from "smart autocomplete" into "extensible development platforms."
The analogy to npm is intentional and instructive. npm didn't just make it easy to install packages — it created an ecosystem where small, composable modules could be shared, versioned, and combined. Agent skills are heading in the same direction.
If you're a solo developer: Stop rewriting the same agent instructions across projects. Package them as skills and install them everywhere.
If you're on a team: Create org-level skill repos. Standardize how your agents handle code review, deployment, testing, and documentation. New team members get consistent agent behavior from day one.
If you're building agent-powered tools: Adopt the Agent Skills spec. Your users can leverage the entire ecosystem instead of starting from scratch.
If you're a startup founder: Pay attention to how agent infrastructure is standardizing. The skills ecosystem is where the "plugin marketplaces" for AI agents will emerge. Being early means shaping the standards.
# Browse available skills
npx skills find
# Install Vercel's official skill pack
npx skills add vercel-labs/agent-skills --all
# Create your first skill
npx skills init
The CLI is open source (MIT license), lightweight, and works with zero config. If you're already using an AI coding agent, there's no reason not to try it.
Q: What's the difference between a skill and a system prompt? A: A system prompt is global and static — it applies to every interaction. A skill is modular, activatable based on context, and can be shared across agents and teams. Think of system prompts as your bash profile, and skills as npm packages you install as needed.
Q: Do skills work with all AI coding agents?
A: The CLI supports 43+ agents including Claude Code, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Codex, Cline, OpenClaw, and more. Basic skills (SKILL.md with instructions) work universally across all of them. Advanced features like allowed-tools and hooks are agent-specific.
Q: Can I create private skills for my team?
A: Yes. You can install skills from private GitHub repos (if you have access), local paths, or any Git URL. Use npx skills add ./my-team-skills for local-only skills, or point to your private repo.
Q: Is this only for coding agents? A: Right now, yes — the ecosystem is focused on coding agents. But the SKILL.md format is general-purpose. As AI agents expand beyond coding (research agents, data agents, creative agents), the same specification could apply. The infrastructure is agent-agnostic; the current adoption is dev-tool-centric.
Arkin Julijanto is a startup founder and developer building Orbits Studio. He writes about AI tools, developer productivity, and the evolving agent ecosystem at arkin-dev.com.
Meta description: Anthropic quietly removed Claude Code from its Pro plan pricing page, sparking developer outrage. Here's what happened, what it means, and why the communication matters.
On April 21, 2026, something changed on Anthropic's pricing page — and nobody got an email about it.
The phrase "includes Claude Code" vanished from the Pro plan description. In its place: an explicit X where a checkmark used to be. Meanwhile, the Claude Code product page still claimed Pro included it, and logging into Claude Code via CLI still showed "Claude Pro" in the terminal output.
It was inconsistent, unannounced, and immediately spotted. Ed Zitron flagged it on Bluesky. The Hacker News thread hit 578 points and 531 comments in under 24 hours. Reddit's r/Anthropic lit up with angry Pro subscribers asking if their $20/month plan just lost its most valuable feature.
Anthropic's head of growth, Amol Avasare, eventually posted on X to clarify:
His explanation made sense on paper. Since Max launched a year ago, Claude Code was bundled into it and exploded in popularity after the Opus 4 release. Features like Cowork, long-running async agents, and agentic workflows became everyday use cases. Engagement per subscriber surged. The current plans weren't designed for this level of usage.
The core economics problem: subscription plans charge far less than the book value of tokens consumed, sometimes by a factor of 10x or more.
Nobody's arguing that Anthropic shouldn't adjust its pricing. Running AI models at scale is expensive. Every major provider — Google, GitHub Copilot, OpenAI — has been tightening usage limits. This is the reality of the AI subscription economy in 2026.
The problem was how it was communicated — or rather, how it wasn't:
As The Register's Thomas Claburn noted: "What's striking about the transition is not so much that it happened but the lack of coherent communication to customers."
If you're building on any AI platform — Claude, GPT, Gemini, Copilot — this incident is a case study in platform risk:
1. Your tools can change pricing or access overnight. There's no SLA for consumer-tier AI subscriptions. Features you depend on for your daily workflow can disappear with zero notice.
2. "Tests" affect real people. A "small test on 2% of signups" still means real developers lost access to a tool they were evaluating. First impressions matter.
3. The economics of AI subscriptions are unsustainable at current prices. This isn't just Anthropic. Every provider is grappling with the gap between what power users consume and what they pay. Expect more limits, more tiers, and more "adjustments" across the board.
4. Vendor communication is a feature. In the AI gold rush, companies that treat their developer community with respect — clear changelogs, advance notice, honest roadmaps — will win long-term loyalty.
Avasare promised that when changes land, "you'll get plenty of notice before anything changes" and that customers "will hear it from us, not a screenshot on X or Reddit."
Good words. But they need to be backed by:
This incident is a symptom of a larger shift. The era of "$20/month unlimited AI" is ending. As models get more capable and usage patterns shift toward agentic workflows (where an AI might run for hours autonomously), the economics don't work at flat-rate consumer pricing.
We're seeing the same pattern everywhere:
The winners in this transition will be the companies that are transparent about costs, honest about limits, and generous with communication.
Claude Code isn't going away from Pro — at least not yet. But this incident reveals the fragility of the AI tool ecosystem. When your entire development workflow depends on a $20/month subscription to a single provider, you're one silent pricing page update away from disruption.
Diversify your tools. Read the changelogs. And always have a backup plan — because in the AI subscription economy, the only constant is change.
Q: Did Anthropic actually remove Claude Code from the Pro plan? A: No — at least not for existing subscribers. Anthropic stated it was a small test affecting ~2% of new signups. Existing Pro and Max subscribers retain access.
Q: Why would Anthropic remove Claude Code from Pro? A: The economics. Claude Code is extremely popular, and power users consume far more tokens than their $20/month subscription costs. Anthropic is exploring plan restructuring to address the gap.
Q: Should I switch away from Claude Code because of this? A: Not necessarily. But it's smart to diversify your toolchain. Having alternatives means you're not locked in if pricing or access changes. Many developers are already exploring Chinese models like Qwen, Kimi, and GLM as lower-cost alternatives.
Q: How can I stay informed about AI tool pricing changes? A: Follow official blogs and changelogs, join community forums (r/Anthropic, r/ChatGPT, Hacker News), and consider paying annually if pricing stability matters to your workflow.
This article was inspired by The Register's coverage and the Hacker News discussion.
The AI agent wars are officially here — and this time, they're showing up inside your editor, your CLI, and your Slack channels. Today's tech news roundup covers a wave of agent-centric launches from OpenAI, Zed, and Qwen, plus a privacy wake-up call from GitHub that every developer should read.
Six million fake GitHub stars. Forty-four percent of new music is AI-generated. And two open-source AI models are quietly outperforming closed-source giants on coding benchmarks. Today's tech news roundup reveals a theme: the AI industry is splitting into two camps — those building trust, and those gaming the system.
AI models are getting pricier to train and run — Stanford says compute capacity has grown 30x since 2021, and token costs for frontier models are heading in the wrong direction. Meanwhile, a Turkish dev shop just cut their cloud bill by 84% by switching to bare metal. This is your tech news roundup for April 18, 2026 — the week where the AI economics story got a lot more complicated.
Meta Description: Google launched Android CLI with agent-ready skills and a knowledge base, cutting LLM token usage by 70% and dev speed by 3x. Here's what founders and devs need to know.
Google just dropped something that should make every mobile-focused founder pay attention: a new Android CLI designed specifically for AI agents, paired with official "Android Skills" and a live knowledge base.
This isn't another VS Code extension or IDE plugin. This is Google acknowledging that a massive chunk of Android development is about to happen outside Android Studio — driven by agents like Claude Code, Codex, Gemini CLI, and whatever comes next.
The numbers from Google's internal testing are wild:
If you're building anything on mobile, this changes how you think about AI-assisted development.
Google didn't just ship a CLI. They shipped a three-part system:
The new android command gives agents a clean, programmatic way to interact with the entire Android SDK from the terminal:
android sdk install — lean SDK setup, only what you needandroid create — project scaffolding from official templates (recommended architecture baked in from line one)android emulator — spin up virtual devices on demandandroid run — build and deploy in one commandandroid update — stay current without the SDK Manager danceThis matters because agents work best with lightweight, predictable interfaces. Before this, agents had to navigate GUI-based workflows or cobble together Gradle commands with inconsistent documentation. Now they have a first-class API.
Here's the clever part. Google created a GitHub repo of modular SKILL.md files — markdown instruction sets that automatically trigger when a prompt matches the skill's metadata.
Think of it as agent-readable documentation. Not the conceptual, tutorial-style docs humans read — but precise, actionable specs for specific workflows.
Initial skills cover pain points every Android dev knows:
Install via android skills and they live alongside your own custom skills or community-created ones. This is the "grounding" problem being solved at the platform level.
The android docs command gives agents access to a frequently updated knowledge base sourced from Android developer docs, Firebase, Google Developers, and Kotlin docs.
Why this matters: most LLMs have training cutoffs that are months or years old. Without live grounding, agents suggest deprecated APIs and outdated patterns. The knowledge base ensures agents work with the latest guidance — not what was correct when their training data was frozen.
This launch is a signal, not just a tool drop. Three things every founder and developer should read into it:
Google is designing for agent-native development. Not "AI-assisted" where you still do most of the work. Agent-native, where an AI does the heavy lifting and you review and refine. The CLI is built for programs, not humans.
The skills pattern is going to spread. Google basically open-sourced a framework for "how to teach LLMs your platform." Expect Firebase skills, AWS skills, Stripe skills. Every platform with complex documentation should be thinking this way.
Mobile dev velocity is about to spike. If you're a startup deciding between web-first and mobile-first, the gap just got smaller. An agent that can scaffold, build, test, and deploy an Android app from the terminal means small teams can ship mobile faster than ever.
Getting started is straightforward:
android skills — pick the ones relevant to your projectThe workflow Google envisions: use an agent + CLI for scaffolding, boilerplate, and iteration, then move to Android Studio for the polish that requires visual tools and advanced profiling.
This isn't magic. The CLI and skills handle the mechanics of Android development — setup, scaffolding, migration patterns. They don't replace understanding UX, performance optimization, or platform-specific design patterns.
Agents with Android CLI will produce correct, best-practice code. But "correct" and "great" are still different things. The human in the loop matters more than ever — just at a higher level of abstraction.
Google's Android CLI isn't just a developer tool — it's a bet on how software gets built going forward. Agents as first-class developers. CLI as the primary interface. Skills as the bridge between LLM capabilities and platform-specific expertise.
Three takeaways:
The future of mobile dev isn't one developer and one IDE. It's one developer orchestrating multiple agents, each grounded in the latest platform knowledge, shipping at a pace that would've seemed impossible two years ago.
Google just made that future easier to reach.
Q: Do I need Android Studio to use the Android CLI? A: No. The Android CLI works independently from the terminal. You can prototype and build entirely with an agent + CLI, then optionally open the project in Android Studio for visual editing and advanced debugging.
Q: Which AI agents work with the Android CLI? A: Any agent that can execute terminal commands — Gemini CLI, Claude Code, Codex, Antigravity, and custom agents all work. The CLI is agent-agnostic by design.
Q: What are Android Skills exactly? A: Modular SKILL.md files containing precise, actionable instructions for specific Android development workflows. They auto-trigger based on your prompt, so agents automatically follow Google's recommended patterns without you manually attaching documentation.
Q: Is the Android CLI free to use? A: Yes. Download it from the official Android developer site at d.android.com/tools/agents. Skills are open-source and available on GitHub.
Q: Can I create my own Android Skills? A: Yes. Skills are markdown-based and designed to coexist with custom skills and community-created ones. Google provides a framework, not a closed system.
Meta Description: Cloudflare launched a unified AI inference platform with 70+ models from 12+ providers, one API, automatic failover, and edge-optimized latency. Here's why it matters for anyone building AI agents.
If you're building AI agents in 2026, you already know the pain. Your support agent needs a fast model for classification, a heavy reasoning model for planning, and a lightweight model for task execution. That's three different providers, three different APIs, three different billing dashboards, and three potential points of failure.
A chatbot makes one inference call per prompt. An agent chains ten or more. When one provider goes down, it's not a retry — it's a cascade of failures that kills the entire workflow. When one provider is slow, 50ms of latency becomes 500ms across the chain.
Cloudflare just shipped something that addresses all of this head-on.
On April 16, 2026, Cloudflare announced a unified AI inference layer built on top of AI Gateway and Workers AI. Here's what's in it:
The core pitch: one AI.run() call to access any model from any provider. Switching from a Cloudflare-hosted open-source model to Claude Opus 4.6 or GPT-5 is literally a one-line change.
const response = await env.AI.run('anthropic/claude-opus-4-6', {
input: 'Analyze this support ticket',
}, {
gateway: { id: "default" },
});
The catalog now includes models from Alibaba Cloud, AssemblyAI, ByteDance, Google, InWorld, MiniMax, OpenAI, Pixverse, Recraft, Runway, and Vidu — covering text, image, video, and speech. That's multimodal access through a single endpoint.
Here's the silent killer for AI startups: cost visibility. Most companies use an average of 3.5 models across multiple providers. No single provider can give you a holistic view of your AI spend.
Cloudflare fixes this by letting you attach custom metadata to requests. Want to see spend broken down by free vs. paid users? By individual customers? By specific workflows? It's built in.
const response = await env.AI.run('@cf/moonshotai/kimi-k2.5', {
prompt: 'What is AI Gateway?'
}, {
metadata: { "teamId": "AI", "userId": 12345 }
});
One billing dashboard. One set of credits. All your AI spend in one place.
This is the sleeper feature. Cloudflare is leveraging Replicate's Cog technology to let you containerize and deploy your own fine-tuned models on Workers AI.
Write a cog.yaml, define your predict function, run cog build, push to Cloudflare. They handle GPU provisioning, CUDA dependencies, and cold starts (with GPU snapshotting coming soon). Your custom model gets the same AI.run() interface as everything else.
For teams with domain-specific fine-tuned models, this is huge. No more managing your own GPU infrastructure.
Cloudflare operates in 330+ cities worldwide. When you call a Cloudflare-hosted model through AI Gateway, your code and inference run on the same global network. No extra hop over the public internet.
For agents, the metric that matters most is time to first token (TTFT). Even if total inference takes 3 seconds, getting the first token 50ms faster is the difference between an agent that feels snappy and one that feels broken. Cloudflare's edge network minimizes the network time before streaming begins.
When you're chaining 10 inference calls in an agent workflow, reliability isn't optional — it's existential. AI Gateway now includes automatic retries on upstream failures. One provider goes down? Traffic reroutes. Your agent keeps running.
This isn't just a developer convenience play. It's infrastructure that enables a specific architectural pattern: multi-model agent orchestration.
The most sophisticated agent systems in 2026 don't use one model for everything. They use a routing layer:
This pattern requires seamless switching between providers. Before Cloudflare's unified layer, you'd build this routing yourself — with custom error handling, billing aggregation, and latency optimization for each provider. Now it's one API.
Here's what makes this different from using AWS Bedrock or Azure AI: Cloudflare doesn't make the models. They're a neutral layer. Switching from GPT-5 to Claude Opus to Kimi K2.5 doesn't change your infrastructure — it changes one string in your code.
For startups, this is strategic. You're not locked into Anthropic's pricing or OpenAI's rate limits. You can optimize for cost, speed, or quality per-task without rewriting your agent logic.
REST API support is coming "in the coming weeks" — right now the unified endpoint is Workers-only. If you're not on Cloudflare's ecosystem, you'll need to wait or wrap it in a Worker.
BYOM is still in design partner phase. The vision is right, but the execution needs to catch up before it's generally available.
And while 70+ models sounds like a lot, the catalog is still missing some niche providers. Expect this to grow fast given Cloudflare's track record.
Cloudflare is positioning itself as the infrastructure layer for the agent era. Not the model maker. Not the agent framework. The plumbing that makes multi-model, multi-provider agent architectures actually work in production.
Three takeaways:
The agent economy needs infrastructure that's provider-agnostic, latency-optimized, and cost-transparent. Cloudflare just shipped all three. If you're building with AI agents, this should be in your stack.
Q: What is Cloudflare's AI Gateway? A: AI Gateway is Cloudflare's unified inference layer that lets developers call AI models from 70+ providers through a single API endpoint, with built-in failover, cost tracking, and edge-optimized latency.
Q: Do I need to use Cloudflare Workers to access the AI platform?
A: Currently, the unified AI.run() binding is Workers-only. Cloudflare has announced REST API support coming in the following weeks, which will enable access from any environment.
Q: How does Cloudflare handle model failover? A: AI Gateway includes automatic retries on upstream provider failures. If one model provider goes down, traffic is rerouted to alternative providers without your agent workflow breaking.
Q: Can I deploy my own fine-tuned models on Cloudflare?
A: Yes, through the Bring Your Own Model (BYOM) feature. You containerize your model using Replicate's Cog technology, push it to Workers AI, and access it through the same AI.run() interface. The feature is currently in design partner phase.
Q: How does this compare to AWS Bedrock or Azure AI? A: Unlike AWS or Azure, Cloudflare is provider-neutral — they don't make their own models. This means no vendor lock-in. Switching between models is a one-line code change, and the edge network (330+ cities) provides lower latency than centralized cloud regions.
Anthropic launched a visual design studio inside Claude, a self-evolving AI agent is eating GitHub's trending page, and NIST just admitted it can't keep up with CVEs anymore. Meanwhile, someone built VMs that cold-start in under a second. The tech news roundup this week is a masterclass in what happens when AI stops being a chat feature and starts being an operating system.