Cursor's pricing shakeup, OpenAI Codex internals, the famo.us postmortem, and when patterns betray you

Published on 19.03.2026

AI & AGENTS

Cursor's Silent Pricing Change Drives Enterprise Churn, Claude Opus 4.6 Gets 1M Context

TLDR: Cursor quietly moved most models behind its Max mode paywall, causing enterprise credits to evaporate in days instead of lasting the month. Meanwhile, Claude Opus 4.6 shipped a 1M token context window and a Compaction API for long-running agents, and the wider AI landscape saw Spotify's internal agent merging a thousand PRs every ten days.

Cursor's Silent Pricing Change Drives Enterprise Churn, Claude Opus 4.6 Gets 1M Context


How OpenAI Codex Works

TLDR: OpenAI Codex is a cloud-based coding agent built on codex-1, a fine-tuned variant of o3. The real engineering story is not the model itself but the three-layer orchestration system: an agent loop, prompt and context management with prefix caching, and a multi-surface architecture that runs everywhere from CLI to VS Code.

How OpenAI Codex Works


The Rise and Fall of famo.us

TLDR: Famo.us was a JavaScript rendering engine from 2012 that raised $30 million by promising native-like performance through GPU-accelerated CSS 3D matrix transforms. It collapsed when browsers caught up, React won the developer mindshare war, and the API demanded too much mathematical expertise from everyday developers.

The Rise and Fall of famo.us


A Proxy Manager, Self-Hostable Web Dashboard for Caddy/Traefik

TLDR: Proxydeck is an open-source, MIT-licensed web dashboard for managing Caddy and Traefik reverse proxies, built with Bun and React. It offers a single-pane-of-glass interface with Docker Compose deployment and optional bundled PostgreSQL.

A Proxy Manager, Self-Hostable Web Dashboard for Caddy/Traefik


When NOT to Use the Repository Pattern in EF Core

TLDR: EF Core's DbContext already implements the repository and unit-of-work patterns. Wrapping it in another repository layer often adds complexity without value, especially in CRUD apps, small projects, performance-critical systems, and microservices. The specification pattern is a lighter alternative when you need reusable query logic.

When NOT to Use the Repository Pattern in EF Core