Dru Knox is head of product and design at Tessl, where he develops AI-native tools for software teams. His work focuses on the context, checks and feedback loops that make coding agents useful beyond a single generated patch.[1]
Start with The Tessl Agent: Build Your Software Factory on Autopilot →
Links
Head of Product & Design · Tessl
Career
Knox’s employer biography describes earlier product work at Google and Airtable, followed by machine-learning and generative-AI work at Grammarly, his own startup and Cantina. At Tessl, he leads tools built specifically for developers. His public GitHub account also preserves earlier work on browser APIs, including proposals for higher-level APIs and running document operations on worker threads.[1][3]
Contributions
The Tessl Agent discussion introduces an interface for building and improving those loops. Its practical emphasis is on capturing repeated problems and turning them into changes to the development process. For a software team, that shifts some work from supervising every generated edit toward maintaining the machinery that catches errors, supplies current instructions and tests whether an improvement actually holds.[2]
Ideas
In his Tessl Agent interview, Knox describes software development as a set of feedback loops. Instead of repeatedly correcting an agent’s immediate answer, a team can change reusable context, checks and review mechanisms so the same failure becomes less likely next time. The agent is one part of that system; the accumulated procedures and evaluations determine how reliably the system operates.[2]
Tools, writing & talks
Writing, research & talks
Start here
A discussion of automated feedback loops, coding-agent context and development systems that improve through use.
Begin with the interview for the reasoning behind a software factory before looking at a specific tool. Experience reviewing code or maintaining a development workflow provides useful context.
Interview guest[2]Tessl's Dru Knox defines a software factory by autonomy, automation and quality. He breaks harness engineering into inner, outer and meta loops and three layers: control plane, agent-ready stack and improvement loops.
Catalog workOriginal source
Tools
- worker-node
github.comA public exploration of allowing document operations on worker threads.
Repository owner[3]