A glaring divide is emerging in the AI coding industry as developers increasingly weigh the convenience of fully managed coding platforms against the flexibility of open-source alternatives designed to avoid dependence on a single provider.
The debate intensified this week after Anthropic used its first “Code with Claude” developer conference to showcase major upgrades across its Claude Code ecosystem. The company announced that rate limits for Claude Code users on Pro, Max, Team, and Enterprise plans would be significantly expanded, while peak-hour usage restrictions were removed entirely. Anthropic also raised usage limits for its Opus API and disclosed a major infrastructure agreement with SpaceX involving the Colossus 1 data center.
According to the company, the agreement will provide access to more than 300 megawatts of computing power and approximately 220,000 Nvidia GPUs expected to come online within weeks. The move reflects the broader AI industry race to secure high-performance computing infrastructure as demand for generative AI services continues to increase.
Anthropic also introduced several updates aimed at turning Claude Code into a more advanced managed development environment. These included expanded Managed Agents capabilities, support for coordinating multiple AI agents simultaneously, a public beta feature called Outcomes, and an experimental memory system internally referred to as “dreaming,” which is intended to help AI systems retain and improve contextual understanding over time.
During the event, Anthropic executive Boris Cherny demonstrated remote agents and automated routines capable of running coding tasks asynchronously, effectively allowing Claude Code to function more like a workflow orchestration platform rather than a traditional coding assistant.
At the same time, a separate trend has been accelerating across the open-source community. OpenCode, an independent coding harness project associated with SST, has experienced a dramatic rise in popularity after positioning itself as an alternative to vendor-controlled AI development environments.
The project’s GitHub repository has now surpassed 157,000 stars, overtaking the roughly 122,000 stars associated with Anthropic’s own Claude Code repository at the time of reporting. While GitHub stars do not necessarily represent active users or production deployments, they are often viewed as indicators of developer awareness, interest, and community support.
The roots of OpenCode’s instant growth trace back to January 2026, when Anthropic introduced server-side authentication checks that prevented third-party tools from accessing Claude Pro and Max subscriptions through OAuth-based authentication methods.
Several projects, including OpenCode, Cline, and RooCode, were affected by the policy change. Prior to the restrictions, these tools allowed developers to run autonomous coding workflows through fixed-price Claude subscriptions rather than paying significantly higher API-based usage fees tied to token consumption.
From Anthropic’s perspective, the restriction addressed a business and infrastructure problem. Subscription plans were designed to support usage within the company’s own ecosystem, while third-party tools were effectively redirecting high-volume workloads through pricing structures never intended for external automation platforms.
Discussions across developer forums, including lengthy conversations on Hacker News, showed that many users understood Anthropic’s reasoning. However, criticism quickly emerged over the manner in which the restrictions were enforced. Developers reported that the changes were introduced without advance notice, disrupting workflows in active sessions. Some users also claimed that automated abuse-detection systems temporarily restricted accounts during the transition period.
OpenCode responded rapidly after the restrictions took effect. The project added support for ChatGPT Plus integrations within hours and began expanding compatibility across multiple AI providers. Anthropic later formalized its position in updated Terms of Service published in February, clarifying that subscription OAuth tokens were not intended for third-party routing or automation tools.
The dispute escalated further in March after OpenCode reportedly received legal requests related to Claude subscription authentication. Shortly afterward, the project merged an update removing references to Claude Pro and Max authentication from its codebase. By April 4, Anthropic’s enforcement measures had expanded to additional third-party harnesses, including OpenClaw and NanoClaw, pushing developers toward pay-as-you-go API billing structures.
Interest in OpenCode accelerated during this period. On March 21, a Hacker News discussion surrounding the project gained more than 1,200 points and hundreds of comments, driving additional visibility across the developer community. By early April, the repository had already crossed 120,000 GitHub stars.
As of May 8, project activity data showed approximately 156,904 stars, 18,259 forks, 4,788 issues, and more than 1,600 open pull requests. OpenCode’s website also claimed participation from over 850 contributors and estimated usage among roughly 6.5 million monthly developers.
Industry observers note that the OAuth dispute alone likely does not explain OpenCode’s growth. Instead, the incident appears to have accelerated an existing movement toward model-agnostic development tools. OpenCode gradually shifted its messaging away from low-cost Claude access and toward provider neutrality, emphasizing that developers should be able to switch between AI models as pricing, performance, and capabilities evolve.
That distinction is increasingly important as competition intensifies between major AI providers. A developer using a model-agnostic harness can move between Anthropic, OpenAI, or other models with relatively minor configuration changes. In contrast, developers operating entirely within a vertically integrated ecosystem may face higher switching costs if pricing structures, usage limits, or platform policies change unexpectedly.
The debate mirrors earlier divisions within the software infrastructure industry. Some analysts have compared the current situation to Docker and Podman, where one platform focused heavily on integrated services and managed workflows while the other prioritized portability, operational control, and independence from platform lock-in.
OpenCode’s rise has also drawn criticism from parts of the developer community. Users in public discussions have raised concerns about high memory usage, the growing complexity of the project’s TypeScript codebase, inconsistent release stability, and the broader security implications of integrating multiple AI providers into a single framework.
Security considerations remain particularly relevant because every additional provider connection potentially expands the software’s attack surface. OpenCode also faced backlash after removing Claude subscription authentication support following reported legal pressure, with some developers expressing frustration over how the project handled the situation.
Still, the overall ndustry direction appears increasingly clear. Anthropic is investing heavily in a future built around tightly managed AI coding ecosystems that combine infrastructure, orchestration, memory systems, and coding assistance within a single platform.
At the same time, open-source projects such as OpenCode, Cline, Aider, and OpenClaw continue to attract developers seeking portability and reduced dependency on individual AI vendors.
For many software teams, the central issue is no longer choosing between Claude Code and OpenCode alone. Instead, developers are beginning to decide whether critical AI-assisted workflows should remain under the control of a single provider or operate through more flexible systems capable of adapting as the AI landscape continues to shift.
Microsoft is intensifying its push toward passwordless security, warning that traditional passwords and older forms of two-factor authentication are becoming increasingly ineffective against modern phishing attacks powered by artificial intelligence.
In a statement released during World Passkey Day, Microsoft said the cybersecurity industry must reduce dependence on passwords and other “phishable” login methods by accelerating the adoption of passkeys.
For years, technology companies encouraged users to strengthen account security by enabling two-factor authentication (2FA) or multi-factor authentication (MFA). Microsoft itself previously stated that MFA could block more than 99% of password-based attacks. However, cybercriminals have steadily adapted their tactics, particularly targeting SMS-based authentication systems through phishing pages, SIM-swapping schemes, session hijacking, and social engineering attacks.
The company now argues that passwords, even when paired with weak MFA methods like text-message verification codes, continue to leave accounts vulnerable. Microsoft described these older protections as “legacy” authentication methods that can still become entry points for attackers.
Instead, Microsoft is promoting passkeys, which rely on cryptographic authentication rather than memorized passwords. A passkey stores a private digital key directly on a user’s device and only works on the legitimate website or application where it was created. Access is then confirmed through biometric verification, such as fingerprints or facial recognition, or through a device PIN.
Security experts say this approach makes phishing significantly harder because passkeys cannot be reused on fake websites designed to imitate legitimate login pages. Unlike passwords or SMS codes, the authentication process is tied directly to the original domain.
Microsoft also stressed that enabling passkeys alone is not enough if passwords and fallback authentication methods remain active on accounts. According to the company, weak backup options can still be exploited even after stronger protections are introduced. Microsoft has therefore continued removing older authentication systems across its ecosystem, including plans to eliminate security questions from password reset flows beginning in 2027.
The urgency surrounding this transition has increased alongside the rapid growth of AI-generated phishing campaigns. Microsoft cited internal findings showing that AI-assisted phishing operations can achieve click-through rates as high as 54%, meaning more than half of targeted users may interact with malicious messages.
Industry-wide adoption of passkeys is also accelerating. The FIDO Alliance estimates that more than five billion passkeys are already in use globally. Microsoft said hundreds of millions of users now sign into services such as OneDrive, Xbox, and Copilot using passkeys every day.
Internally, Microsoft claims that over 99% of users within its environment now have access to phishing-resistant authentication methods. The company added that account recovery systems remain a critical security challenge because attackers increasingly target recovery processes instead of direct logins.
Researchers and government agencies are broadly supporting the move toward passwordless security. The United Kingdom’s National Cyber Security Centre recently encouraged organizations and consumers to adopt passkeys, citing growing risks from AI-driven phishing and phishing-as-a-service platforms.
Still, cybersecurity researchers caution that passkeys are not completely immune to attack. Recent academic research examining FIDO2 authentication methods found that while passkeys substantially raise the difficulty for attackers, sophisticated compromise techniques involving infected devices, session theft, or manipulated browser environments may still pose risks under certain conditions.
Microsoft maintains that removing passwords and other phishable credentials remains essential as AI systems increasingly act on behalf of users across enterprise environments. If a single digital identity is compromised, attackers could potentially exploit connected AI agents to access systems, trigger workflows, and operate with existing permissions at machine speed.
Artificial intelligence tools are increasingly allowing non-technical users to build software and automate tasks that previously required programming knowledge, and a new open-source AI agent called Hermes is becoming a major example of that shift.
The discussion gained momentum this week after reports circulated about a 78-year-old marketing executive with no coding background successfully creating a robotics application using only natural-language instructions. The application was reportedly built through the Reachy Mini ecosystem developed by Hugging Face, whose robot app marketplace has surpassed 300 live applications and approximately 10,000 deployed robots worldwide.
According to the shared account, the individual did not use Python programming or specialized robotics software during development. Supporters of AI-assisted development tools pointed to the example as evidence that conversational AI systems are reducing technical barriers that traditionally slowed software creation.
The development also reflects a broader trend across the AI industry. Newer AI agents are increasingly designed to retain information from previous interactions, improve their own workflows, and adapt to user behavior over time. Earlier this week, Anthropic introduced a feature called “Dreaming,” which allows AI agents to process earlier sessions in the background and generate new memory structures automatically. Meanwhile, Hermes Agent from Nous Research is pursuing a similar idea through persistent task learning and automated skill generation.
Hermes Agent, first released in February 2026, has quickly gained traction within the open-source AI community. The project reportedly has more than 135,000 GitHub stars and is distributed under the MIT license. It also includes over 40 built-in skills, which function as reusable instruction modules that help the system repeat previously learned workflows more efficiently.
One of Hermes’ defining features is its self-improving learning architecture. After completing a difficult or multi-step task, the agent enters what developers call a “Reflective Phase.” During this process, the system reviews its own actions, identifies successful execution patterns, and converts those patterns into reusable skill files. When a related task appears later, Hermes can retrieve the previously learned solution instead of generating a new workflow from the beginning.
The platform also uses a layered memory structure consisting of temporary session memory, long-term episodic memory stored through SQLite databases, and procedural memory tied to learned skills. Developers say the software can operate on low-cost virtual private servers, large GPU clusters, or serverless cloud environments. Hermes is also model-agnostic, allowing users to connect the framework to providers such as OpenAI, Anthropic, OpenRouter, Kimi, MiniMax, GLM, Nous Portal, or privately hosted AI endpoints.
Users can access the agent through Telegram, Discord, Slack, WhatsApp, Signal, email services, or command-line interfaces. The project’s latest update, v0.13.0, internally referred to as “The Tenacity Release,” reportedly introduced Google Chat integration as its twentieth supported platform. The update also added durable multi-agent coordination tools, automatic task recovery systems, retry budgeting controls, hallucination filtering mechanisms, persistent goal tracking for long-running tasks, automatic linting after file edits, and session recovery after unexpected gateway interruptions.
According to project details shared by contributors, the release included 864 code commits from 295 contributors in a single week and resolved eight critical security issues. One patched vulnerability reportedly involved a Discord-related flaw that could allow bots to message users across servers outside their intended access scope.
The installation process has also been simplified significantly. Hermes now uses a one-line curl installer that automatically configures dependencies such as Python 3.11, Node.js, ripgrep, and ffmpeg. During setup, the software can automatically detect existing OpenClaw environments and offer to import prior settings, memories, skills, and API credentials.
The growing comparison between Hermes and OpenClaw highlights a design shift occurring within the AI assistant ecosystem. OpenClaw originally gained attention by focusing heavily on messaging integrations and centralized orchestration across communication platforms. Hermes, by contrast, places continuous learning and automated self-improvement at the center of its architecture.
In practical terms, OpenClaw skills are generally predefined instruction sets written manually by users or generated beforehand through prompting. Hermes instead attempts to build those reusable workflows automatically by analyzing completed tasks after roughly every 15 tool interactions or after especially complex operations. Supporters argue this creates a compounding learning effect where the agent gradually improves with repeated use.
Despite the growing interest around Hermes, some developers caution against viewing it as a complete replacement for OpenClaw. OpenClaw still supports more than 24 messaging integrations, offers greater transparency through inspectable file-based memory systems, and has undergone broader public security review. Community discussions suggest that many advanced users currently operate both systems together, using OpenClaw for orchestration while relying on Hermes for adaptive learning capabilities.
Researchers tracking the rapid development of AI agents believe these systems are moving beyond traditional chatbot behavior and evolving into persistent digital assistants capable of handling long-running, multi-step workflows. However, cybersecurity analysts also warn that systems with autonomous memory creation and broad platform access may introduce additional security and privacy risks if governance and safeguards fail to evolve alongside the technology.
The first bug is tracked as CVE-2026-23863, a Windows specific problem. This bug was maliciously crafted with hidden “NUL BYTES” hidden within the filename, to trick WhatsApp into showing it as one filetype such as an authorized PDF while pretending to be running as an executable once opened. Meta fixed this patch in April on both platforms.
The second vulnerability, tracked as CVE-2026-23866 impacted both android and iOS users. The attack tactic involved partial authorization of AI rich response texts for Instagram Reels shared within Whatsapp. A threat actor could possible launch another user’s device to access media content through an arbitrary URL, such as launching OS level custom URL scheme handles. This flaw was patched in April on both platforms.
The two bugs were given medium severity by researchers. WhatsApp has verified that no bug was abused.
Both were rated medium severity, and WhatsApp confirmed there's no evidence either was actually abused.
These kind of reporting get sidelined by glossy and infamous threat. For instance the recent SMS pumpoing attacks increasing phone bills, or phishing campaigns that used messaging apps as entry points, and lastly the attack on educational institutes that compromised Canvas and Instructure, leaking hundreds of GBs of data.
But Whatsapp did a good job in finding and fixing the flaw before cybercriminals could exploit them and cause harm. The bug bounty program of WhatsApp has been going on for fifteen yesr, and the recent patches show it it is still reliable.
Simple advice: always keep your phones and app updated.
There has never been a better moment to use secure communications services like WhatsApp or Signal. The truth is that Meta does a great job of keeping the app and its users safe and secure, despite some security concerns of its own, such as the recently reported phishing attempts using the encrypted messenger as part of the exploit chain and a spyware threat targeting iOS users.