- Author
- Scott Fryxell
- Published
- August 25, 2026
- Kind
- Personal blog post describing one developer's workflow
- Original
- scott-fryxell.github.io/blog/the-harness-is-the-thing/
- Subject
- Harnesses and agent loops
- Themes
- Handing over control
What it is
Scott Fryxell is a developer who writes about the workflow behind client and personal projects. The post sets out how a shared harness changed the author's work with agents.
What it says
- The author says the harness, not any model, is the key part.
- Cursor, Claude and Pi share skills and AGENTS.md. The author says this commodifies models.
- A cheap model handles routine work, and a frontier model is saved for serious features.
- Work runs through planner, worker, critic and promoter roles. The plan is a task DAG.
- The author reports a 75% drop in frontier model use.
- The author's camera app is scriptable through a driver the harness can use.
- Early skills were too prescriptive, and the author plans a more empirical approach.
What evidence it gives
The evidence is one developer's experience. The post gives a directory layout, a shell snippet and a skill list. The 75% figure is a personal estimate with no method. The author says impact checks still need to be empirical.
Interests and limits
The author has a camera app that the post promotes as a product link. No other setups were compared. The post credits other writers for prewalk and the planner, worker, critic split. The post says the concepts are still forming. It attributes a shift to other models to a government ban, with no sourcing given. The result may not carry over to team projects.