How to code with AI agents - Advice from OpenClaw creator | Peter Steinberger and Lex Fridman

Terminal-First Workflow

Transitioned from IDE-heavy work to running 7+ Cloud Code terminal windows side-by-side, using the IDE only as a diff viewer and rarely reading code directly.

Selective Code Review

Stops reading 'boring' boilerplate (data transformation, Tailwind alignment) and focuses human review only on critical architecture, database logic, and security-sensitive PRs.

Voice-Native Input

Uses voice-to-text extensively for agent prompting (reserving hands for terminal commands), having temporarily lost his voice from overuse, finding spoken language more natural than typing.

The Complexity Curve

Engineers progress from simple prompts to over-engineered multi-agent orchestration with custom workflows, then reach 'zen' by returning to short, simple prompts like 'look at these files and make these changes.'

Agentic Engineering vs Vibe Coding

Rejects 'vibe coding' as a slur implying carelessness; 'agentic engineering' requires practiced skill, treating AI like a capable junior developer who sometimes needs guidance but often has better ideas than the human.

Empathy for the Agent

Success requires understanding that agents start each session with zero context and limited context windows, necessitating guidance on where to look rather than assuming full codebase knowledge.

Always Commit Forward

Never reverts code; instead fixes issues forward with agents, maintaining a 'YOLO' approach where main is always shippable and refactors are cheap enough to do on demand.

Conversational Debugging

Treats interactions as discussions with agents, asking 'do you understand the intent?' before implementation, and stopping long-running tasks to reassess architectural friction rather than forcing solutions.

Local-First Validation

Runs CI locally before pushing rather than relying primarily on GitHub CI, prioritizing speed and iteration over traditional branch protection models.

Letting Go of Perfection

Accepts that agents produce 'good enough' code that differs from personal style, comparing it to managing human engineers where micromanagement destroys velocity and morale.

Codebase Design for Agents

Structures projects using obvious, searchable naming conventions that agents can discover, rather than optimizing for human aesthetic preferences that confuse AI search patterns.

Against Full Automation

Opposes orchestrators like GitTown that attempt to automate the entire loop, comparing them to failed waterfall models; believes human vision and style require iterative, hands-on involvement.