Detailed writeups on multi-agent orchestration, AI engineering patterns, and what actually works in production.
The printing press took 60 years to become economically sustainable. LLMs are on a similar diffusion path—broad adoption, shallow integration. The winners won't have model access—they'll have the complements: context, workflow, trust.
The clean way to use Claude Code with both your normal account and z.ai is one neutral config and two simple entry points.
Copyright does not disappear in the AI era, but it stops functioning as a meaningful scarcity mechanism for software. As reimplementation gets cheap, the real moats shift to trust, governance, provenance, maintenance, and operational legitimacy.
Give the agent a Steel CLI and SKILL.md contract, force a snapshot/click/fill loop, then turn the successful run into a rerunnable bash script.
There's a hidden layer between human questions and search results. AI tools translate messy prompts into precise queries - and you can see the evidence in Google Search Console.
The best coding agents aren't about smarter models. They're about harness design: minimal core, extension hooks, radical transparency, real sandboxing, session forking, and headless RPC.
AI agents are now power users of your CLI tools. If you want them to succeed, you need structured output, deterministic exit codes, explicit sessions, and recovery primitives. Here's the complete checklist.
A single AI session turned `scribe.sh` into `scriby`: a Go CLI with deterministic output, runtime bootstrap, and cross-platform releases.
LLMs are eager by nature. Give them an inch, they'll take 10 files. Here's how to scope agent work and prevent PR bloat.
Checked onboarding responses. Exactly 40% of new users in the last seven days found steel.dev through AI tools. Not Google. Not ads. Users told us this during signup.
Request an AI summary of this blog
