Skip to main content

The Agentic Shift: 5 Things That Reshaped Programming This Month

 

The intersection of software engineering and artificial intelligence has reached a boiling point this month. We are seeing a definitive shift from "AI as a feature" to "AI as the primary actor," alongside the infrastructure needed to govern that shift.

1. The OpenClaw Foundation & Security Hardening

Following a period of rapid growth and significant security challenges—including the ClawHavoc campaign that saw hundreds of malicious skills targeting developer credentials—OpenClaw has officially transitioned to an independent open-source foundation.

  • Governance: The project is now sponsored by OpenAI but managed by a foundation to ensure neutrality.

  • Security: New updates like v2026.2.14 introduce mandatory vetting for ClawHub skills and hardened Docker-first isolation to prevent unauthorized data exfiltration.

2. The Anthropic "100% Code" Milestone

At the recent Cisco AI Summit, Anthropic leadership confirmed that Claude is now writing 100% of the code for its own internal products. This milestone highlights a massive industry trend: the "implementation bottleneck" is vanishing, shifting the developer's role toward architectural articulation and system review.

3. "Entire": Version Control for AI Agents

Launched by former GitHub leadership, Entire is a new platform designed to solve the "black box" problem of agentic workflows. It provides a CLI that creates Checkpoints for every agent action, capturing the full context of prompts, tool calls, and reasoning steps. This allows developers to review AI-driven changes with the same granularity as traditional Git commits.

4. GPT-5.3-Codex-Spark (Real-Time Coding)

OpenAI released GPT-5.3-Codex-Spark, a specialized model optimized for ultra-low latency. Unlike previous models that were better for batch processing, "Spark" is designed for real-time pair programming, allowing developers to interact with the AI mid-stream without the typical processing delays.

5. Multi-Agent Orchestration (GitHub Agent HQ)

GitHub has introduced Agent HQ, a development environment specifically for orchestrating multiple specialized agents. Instead of using one model for everything, developers can now deploy specialized agents (e.g., one for unit testing, one for security auditing, and one for UI) to work on the same codebase simultaneously using the Model Context Protocol.


Quick Comparison: Agentic Coding Tools

FeatureOpenClawClaude CodeGitHub Agent HQ
PhilosophyLocal-first / PrivacyHigh-speed AutonomyMulti-Agent Orchestration
GovernanceOpen FoundationProprietaryProprietary (GitHub/MS)
ProtocolNative MCP SupportNativeMulti-Protocol


Comments

Popular posts from this blog

On sleep deprivation and Incan Monkey Gods

From: Dilbert comic strip for 08/03/1992 from the official Dilbert comic strips archive. I was trying to show this strip to a coworker who is dangerously toying with the harsh mistress that is Insomnia. What shocked me is how quickly I was able to look up the strip, which was published when he was just 11 years old, and two weeks before my just-out-of-college ass shipped out to US Army Basic Training.

Add custom speed settings to your ifit map workout

Ifit.com allows you to build a workout walk/race/bike route simply by clicking on a Google Maps interface. You can then use a compatible ifit-enabled workout machine to recreate the route automatically. The problem is that the user interface still isn't final, so there are features in place that aren't exactly obvious. For example, if you create a workout your machine starts at 1 MPH, because that's the default. But how to set it to start at say, 3 MPH? Easy, just switch from map view to graph view: That button switches from the Google Maps interface to a chart that allows you to visualize and control effort: You can't change the elevation, this is fixed due to the geography that you selected. But you can drag the yellow (speed line) to change the speed of your device.  What if you want to have segments at different speeds? Easy, just click and drag and it will break the line, and you can drag each segment of the line independently: ...

Software Entropy and the Strangler Fig: Surviving a 20-Year-Old Codebase

Right now, I find myself fighting a three-front war. Front one is keeping a 20-year-old behemoth of a B2B application alive. We are talking about decades of legacy ASP.NET and VB.NET where two decades of tweaks, patches, and "temporary fixes" have become permanent, load-bearing pillars of the architecture. Every time I touch it, it feels like playing Operation with oven mitts on—spending 90% of my week untangling logic just so a simple bug fix doesn’t cause a ripple effect that crashes a critical service. Front two is modernizing the architecture. I am actively trying to implement a rudimentary Strangler Fig pattern—slowly carving out legacy functionality and pushing it into a clean, testable shared library project so we can actually run proper unit tests and stop the bleeding. Front three is modernizing the team. While keeping the lights on and quietly rebuilding the engine, I am also pushing a retraining effort to get my peers up to current framework versions and embracing ...