Ergonomic coding surfaces for agents (a.k.a Code Mode)
Code Mode isn't a strict upgrade on tools. It's a different point in the tradeoff space, and the real move isn't picking the surface - it's bootstrapping one.
Thoughts on building with AI agents, Claude Code, infrastructure, and the craft of software engineering. By Michael Livshits.
Code Mode isn't a strict upgrade on tools. It's a different point in the tradeoff space, and the real move isn't picking the surface - it's bootstrapping one.
How agents drive a browser in 2026: autonomous loops, hybrid primitives, computer-use, code mode. Frameworks, cloud infra, benchmarks, prompt injection.
A practical guide to every web search API available for agents in 2026 - pricing, data sources, benchmarks, SDKs, and what I picked for my own agent harness.
Claude Code has 37 hidden reactive messages that nudge the agent mid-conversation. Here's how they work and how to build your own.
A decade of information retrieval and three years of agent harness engineering, poured into a local-first knowledge system that avoids vector search entirely.
Extracting Anthropic's design system from a conversation export and rebuilding generative UI for the terminal.
Backlogs are dying. What replaces them isn't chaos - it's anarchy. Free market collaboration between competent people.
The Shift - a company, a movement, and a generation. Built for a world that rewrites itself every quarter.
I built a chart CLI and distilled aesthetic knowledge into a 213-line skill through a render-look-fix feedback loop. Here's the process.
From single-file HTML to full-stack vibe coding - mapping what LLMs can build for non-technical users, and where the real leverage is.
OpenClaw runs on Pi. NanoClaw wraps Claude Code. MimiClaw runs on a $5 chip. I tore apart 12 personal agents to find what's inside.
Claude Code, NanoClaw, and Pi take radically different approaches to harness extensibility. The tradeoff is always safety vs. agent agency.
Quality loops work because context stays intact. The moment you add a second agent, you get lossy handoffs. That's the real challenge.
Agent evals overfit prompts to small datasets and test nothing real. Dogfood your agent, test your harness, and stop lying to yourself.
RAG pipelines are broken by design. Why full-text search and BM25 beat vector embeddings when an LLM already understands your query.
Anthropic's agent teams experiment compiled Linux with 16 Claude instances. The hard lessons about coordination matter more than the result.
36 CLI coding agents compared: Claude Code, Codex CLI, Gemini CLI, OpenCode, and 32 more. Features, sandboxing, stars, and which to use.
Claude Code has an undocumented persistent memory system. A MEMORY.md file loads into every session. Here's how it works and why it matters.
There are a thousand ways to sandbox an agent. Okay, I lied. There are three: simulated, containers, and microVMs. Here's when to use each.
Every agent builder hits a wall with writes. Here's the structural reason why - and the escape hatch.
I red-teamed psst with Claude. It found a real vulnerability - file exfiltration bypasses masking. Then we fixed it with a PostToolUse hook.
Steve Yegge's Beads proved how agent memory should work. Now Anthropic is building it into Claude Code. One less dependency.
Everyone's adding llms.txt for AI discoverability. The data says no major AI actually reads it.
When agents write your code, production is easy. Understanding becomes the bottleneck. An attempt to not lose grip.
Building retrieval for Claude Code's command history. Why BM25 beats embeddings when there's already an LLM interpreting queries.
The new LLM interoperability spec tackles response normalization. The real pain is stream error handling, and nobody's solving it.
I built an RPG-style companion that shows what Claude Code is doing. File reads cast spells. Bash commands swing swords. Errors take damage.
Everyone's adopting Anthropic's agent skills. But the file format isn't what matters. Progressive disclosure is the real idea.
Secrets manager for agents now supports dev/prod environments, detects leaked secrets, and injects into any command.
Two companies, four sandboxing strategies, all correct. How to pick between gVisor, Firecracker, bubblewrap, and just-bash.
Claude Code forgets your bash commands after context resets. ran indexes them across sessions so you can search what worked.
The secrets manager for agents now redacts output, imports .env files, and locks your vault.
Using Claude to argue with itself. A surprisingly useful pattern for decisions.
I built a secrets manager where AI agents use secrets without seeing them. The secret never touches the context - it's injected at runtime.
A specification for agent behavior that LLM frameworks leave undefined: error handling, context management, tool execution, and state transitions.
A specification for what context engineering actually means - and a call to build it. We have the term but not the tools.
The insight that finally made my agents reliable: tools aren't utilities, they're waypoints. Design for flow, not function.
How Anthropic sandboxes Claude (spoiler: gVisor), and what I learned building a similar system for AI agents.
Building an Astro component to render real Claude Code chat sessions. This post uses the component it describes.
The basic ingredients of an agentic system: loops, tools, memory, and the levers we pull to control behavior without breaking autonomy.
First post. What this blog is and why it exists.