Some posts arrive at exactly the right moment. Just Talk To It by Peter Steinberger landed when the field was still arguing about whether agentic coding was real or hype. Steinberger was already running 3–8 parallel agents in a terminal grid on a 300k LOC TypeScript codebase and writing about what actually works. This is that document annotated against current practice — specifically with OpenClaw as the harness and the multi-agent workflows we run at PromptEngines.
Blast radius: the most useful mental model in the post
Steinberger introduced the term "blast radius" to describe the scope of a change before you commit to it. Small blast radius: touches 2–3 files, reversible in minutes. Large blast radius: crosses module boundaries, requires migrations, hard to untangle if wrong. His rule is to run many small blasts in parallel rather than one fat one serially.
This is not just a git hygiene tip. It is a fundamental reorientation of how to think about delegating work to an agent. The question is not "can this agent do this task?" — it almost certainly can. The question is "what's the worst case if it does it wrong, and how quickly can I recover?" Small blast radius means fast recovery. That changes which tasks you delegate freely versus which ones you supervise closely.
In OpenClaw terms: scope your tasks before spawning subagents. One logical change per session. Commit before starting anything adjacent. This is why atomic commits are non-negotiable — they are the mechanism that keeps blast radius contained after the fact.
Stop freely. Pick up mid-task.
One of the most practically valuable points in the post: "Don't be afraid of stopping models mid-way, file changes are atomic and they are really good at picking up where they stopped." This was counterintuitive to many engineers in 2025 who treated agent runs as precious, all-or-nothing processes. Steinberger's point is that the model's ability to resume from partial state is a feature you should use, not a failure mode to avoid.
The interrupt-and-query pattern — stopping the agent mid-run to ask "what's the status" before deciding whether to continue, redirect, or abort — is now a standard technique in OpenClaw workflows. Sessions carry context. You can steer mid-flight. The skill is recognizing when something is drifting versus when it's just slow.
Skip the elaborate plan files
Steinberger's sharpest take: "I rarely use big plan files now with codex... I can just write 'let's discuss' or 'give me options' and it will diligently wait until I approve it. No harness charade needed. Just talk to it."
This deserves careful reading. He is not saying planning is useless. He is saying that elaborate scaffolding documents — agent personas, multi-step prompt chains, structured reasoning templates — are often compensating for model weakness rather than adding genuine value. When the model is good enough at reading a codebase and inferring intent, the overhead of maintaining a complex system prompt exceeds its benefit.
The implication for OpenClaw: SOUL.md and AGENTS.md are useful. A 400-line SYSTEM.md that tries to pre-specify every possible situation is probably context poison. Write the minimum that actually changes behavior. Prove it before adding more.
Where the post shows its age
The post was written in the Codex vs Claude Code era, and some of the harness-specific opinions are already dated. Steinberger's preference for Codex over Claude Code is partly about 2026-era Claude Code's verbosity and compaction behavior — both of which OpenClaw and current Claude builds have improved significantly. The underlying point about model language and cognitive overhead remains valid even if the specific model preferences have shifted.
His skepticism about third-party harnesses ("I don't see them surviving long-term") has partially played out, but OpenClaw occupies a different position than the harnesses he was evaluating — it is an always-on local agent, not a code-generation wrapper. The category distinction matters.
The subagent critique — that spinning off subagents reduces visibility and control compared to separate terminal panes — is a real tradeoff that OpenClaw acknowledges. The solution is not avoiding subagents but building good observability into how you spawn and monitor them. Steinberger's instinct for control is correct; the mechanism he prefers is a style choice, not a technical requirement.
What this post is
It is a practitioner's manual written at an inflection point, when the question shifted from "does agentic coding work?" to "how do you actually run it at scale?" The answers Steinberger gives are grounded, specific, and honest about tradeoffs. That is rare in a field that defaults to either breathless promotion or reflexive skepticism.
Read it. Then read it again when you find yourself building elaborate scaffolding that your agents seem to ignore. The title is the thesis: just talk to it. The rest is operational detail about what that actually requires.
Original post: steipete.me/posts/just-talk-to-it — Peter Steinberger, 2026.