Short Leash AI Coding Method: Beat Fable by Keeping Control

Greg Slepak, maintainer of security-critical software, distills over a year of research into AI coding agents into the short leash method. It's designed for expert developers who want AI to boost output without sacrificing quality — and claims to beat Fable 5 results even without frontier models.
The core problem Slepak identifies: AI agents regularly "go off the rails," produce ugly/inefficient code, or require YouTuber-style orchestration systems that remove the developer from the loop. His method keeps you in control at every step.
Short Leash Rules
- Plan the task, optionally using something like
tasks skillto break large tasks into steps. - Never use "YOLO" mode (aka "dangerously skip permissions").
- The AI only works while you are watching — no "vibe coding" while you play video games.
- Use a coding agent that displays a diff in the permissions prompt before making changes.
- Analyze each proposed diff — deny permissions whenever the AI is about to do something you don't want.
- Keep yourself in the loop to maintain up-to-date understanding of the codebase.
- Intervene frequently to prevent the AI from going off the rails.
- Commit after every subtask to protect against the AI deleting previous work (Slepak has seen Opus do this).
AI Reviews
Slepak recommends treating AI as a linter for PR reviews. The AI catches common mistakes, the human catches high-level issues. Both together outperform either alone. The AI needs sufficient context (issue, PR description).
He also notes that he built custom AI review tools performing as well as multi-billion-dollar systems, and maintains a fork of an agent called Crush.
📖 Read the full source: HN AI Agents
👀 See Also

12 OpenClaw Power User Tips for Efficient AI Agent Workflows
A Reddit post outlines practical strategies for optimizing OpenClaw usage, including splitting conversations into topic-specific threads, using voice memos for input, matching models to tasks, delegating work to sub-agents, and implementing security layers.

Five Common OpenClaw Configuration Issues That Inflate API Costs
A Reddit post identifies five configuration problems in OpenClaw setups that lead to excessive API credit consumption, including using expensive models for routine tasks, missing budget limits, open gateways, unmanaged memory, and unaudited skills.

Trellis 2 Successfully Running on ROCm 7.11 with AMD RX 9070 XT
A developer got Trellis 2 working on Linux Mint 22.3 with an AMD RX 9070 XT using ROCm 7.11, fixing two key issues: ROCm instability with high N tensors and a broken hipMemcpy2D in CuMesh.

Building 9 Claude Skills for Solo Studio: Stacking Instructions for Real Work
A solo developer built nine Claude skills for video production, analytics, SEO, financial modeling, and more. Key insight: write skills as instructions to an experienced colleague, not as documentation. Skills auto-trigger and stack when tasks overlap.