mcp
4 items · chronological order
Can coding agents relicense open source through a "clean room" implementation of code?
Coding agents can now reimplement GPL codebases against test suites in hours, making copyleft economically unenforceable. The chardet LGPL→MIT relicensing dispute is the first clean test case, but the real bomb is training data contamination: if the model was trained on the original code, no "clean room" claim holds. Generalizes to any governance mechanism that relies on cost-of-reimplementation as friction.
Agent Browser Protocol: Chromium Fork That Makes Browsing a Step Machine for LLM Agents
ABP solves the fundamental impedance mismatch between async browser state and synchronous LLM reasoning by forking Chromium itself — freezing JS execution and virtual time between agent steps so the page literally waits for the model. At 90.5% on Mind2Web, this is the strongest signal yet that browser agents need engine-level integration, not another CDP wrapper. The MCP-native interface (REST + MCP baked into the browser process) is the right abstraction layer, but the Chromium fork dependency is a distribution bottleneck that will matter at scale.
NVIDIA NemoClaw: Open-Source Enterprise Agent Platform
NVIDIA's NemoClaw applies the CUDA playbook to agents: make the orchestration layer free and hardware-agnostic, then let silicon pull-through follow. The decisive question isn't capability but MCP compatibility — if NemoClaw speaks MCP, NVIDIA becomes the enterprise runtime for the existing ecosystem; if not, they're forking the standard.
Extreme Harness Engineering for Token Billionaires: 1M LOC, 0% Human Code, 0% Human Review
OpenAI's Frontier team built a 1M-line Electron app with zero human-authored code: the competitive advantage wasn't the model, it was six skills encoding what "good" looks like as text. The real shift here isn't AI writing code; it's AI inheriting engineering culture. Ghost libraries (distributing specs instead of code) and Symphony (an Elixir orchestrator the model chose for its process supervision primitives) point to a future where the scarce resource is institutional knowledge distillation, not developer headcount.