AI subscription risks, where programming time goes, and OpenAI's 40-person AI-first team structure. Plus the latest trending pieces and tools as usual.

View in browser | Past Issue | Subscribe / Unsubscribe

SitePoint Source

Welcome, Developers! đź‘‹

Learn why connecting third-party tools to subsidized AI plans risks account bans, reminder where programming time actually goes, and see how OpenAI's Codex team operates with AI throughout their workflow. Why Electron powers Claude Code and efficient JS tools written in Rust.

From our sponsor: WorkOS

Agents Need Authorization, Not Just Authentication

​Every AI agent demo looks magical, but most hit a wall in enterprise deployment. It's not model quality or latency. It's authorization. Authentication proves an agent's identity. Authorization defines its blast radius.

The winners in enterprise AI won't have the most features. They'll be the ones enterprises can safely trust. Learn how WorkOS FGA scopes that blast radius with resource-level permissions.

Read the deep dive

đź”– The Reading Room

Articles we have hand-picked for you:

Don't use AI subscriptions with OpenClaw 

Some users with Google's $250 AI plan had their accounts suspended after they connected AntiGravity (Google's IDE) to OpenClaw through an unofficial OAuth. Bans without warnings for paying customers are too harsh but these plans often come with subsidized token costs and disallow this behavior in their terms. Always use dedicated APIs to avoid getting your account suspended.

On Google Dev Forums →

How Programmers Spend Their Time

Malte's detailed account of fixing a tiny bug in flash-attention that took over 10 hours despite requiring only seconds to write the actual code. The journey involved debugging crashes, fighting build systems, upgrading CUDA versions, dealing with compiler segfaults, and repeatedly running the wrong version of code. The article reminds where programming time actually goes: navigating layers of abstraction, wrestling with dependencies, and troubleshooting tooling rather than writing code.

By Malte Skarupke →

How OpenAI's Codex Team Works and Leverages AI

​OpenAI's Codex team of 40 people operates with unprecedented autonomy and speed, using AI throughout their entire workflow. The team uses Codex for everything from onboarding new engineers to reviewing pull requests and prioritizing work. With minimal hierarchy, one product manager, and AI as a core teammate, they've reimagined how engineering organizations can function in an AI-native world.

By Gregor Ojstersek →

How to train your program verifier

Researchers used AI to create a3-python, a verification tool that analyzes Python code for bugs using formal methods. The system discovered real vulnerabilities in popular packages like requests and LLM2CLIP, proving 96%+ of flagged issues as false positives while identifying genuine crashes. Built through iterative AI prompting and testing, it combines barrier certificates with symbolic execution to verify code safety.

By Halley Young, Nikolaj Bjørner →

Why is Claude an Electron App?

Despite Anthropic's advanced AI coding capabilities, their desktop Claude app still uses Electron rather than native code. While coding agents excel at cross-platform implementations from specs, the "last 10%" of development and ongoing maintenance remains challenging. The support burden triples with native apps across Mac, Windows, and Linux, making Electron's single codebase approach still more practical than spec-driven, agent-powered native development.

By Drew Breunig →

⏳ Back in Time

Most clicks from last newsletter:

đź”— The Link Lounge 

Unordered finds from around the web:

Find something cool? You can send us links to feature here via email.

đź§° The Toolbox

Tools and products we're excited about today:

GitNexus

GitNexus indexes any codebase into a knowledge graph, tracking every dependency, call chain, and execution flow. It connects to AI agents via MCP, giving tools like Cursor and Claude Code deep architectural awareness so they stop breaking code.

Learn more →

keychains.dev

Keychains.dev is a secure credential proxy for AI agents. It replaces raw API keys with template variables like , injects real credentials server-side, and keeps secrets completely hidden from agents.

Learn more →

aqua

Aqua is a CLI tool for AI agent communication. It enables peer-to-peer, end-to-end encrypted messaging with durable storage. It supports cross-network connectivity via Circuit Relay.

Learn more →

Fresh File Explorer

Fresh File Explorer is a VS Code extension for navigating recent Git changes. It shows modified, deleted, and pending files. It also supports filtering, grouping, and search.

Learn more →

Agents Need Authorization, Not Just Authentication

​Every AI agent demo looks magical, but most hit a wall in enterprise deployment. It's not model quality or latency. It's authorization. Authentication proves an agent's identity. Authorization defines its blast radius.

The winners in enterprise AI won't have the most features. They'll be the ones enterprises can safely trust. Learn how
WorkOS FGA scopes that blast radius with resource-level permissions.

Read the deep dive →

🎤 Your Voice

Your feedback shapes what comes next! We read every email, so simply hit reply and tell us what's on your mind.