Observed Signal · May 22, 2026 · Technical Guidance · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Harnesses Use Guides and Sensors for AI Agents
Birgitta Böckeler (Thoughtworks) describes a practical distinction for engineering AI agent harnesses: guides and sensors. Guides are pre-output constraints—rules files, example code, style guides and repository patterns—that bias an agent toward desired behavior. Sensors are post-output checks—linters, tests, CI gates and audits—that detect failures after the agent produces output. Each approach has predictable failure modes: guides can produce rule fatigue and non-binding suggestions; sensors provide durable enforcement but create slow, expensive feedback loops. Böckeler explains simple diagnostics to identify which side a team underinvests in and recommends a rule of thumb: introduce new constraints as sensors first, then add guides to make correct behavior natural. The piece argues that balanced investment in both guides and sensors is the minimal effective architecture for reliable, scalable agent workflows.
Practical engineering guidance for agent harness design helps teams avoid common failure modes (rule fatigue, slow feedback loops) and reduce operational costs, making it useful for teams deploying agentic AI—but it is not a platform-level or industry-shifting announcement.
Track Thoughtworks Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Author: Birgitta Böckeler (writing about harness engineering at Thoughtworks).
- Article distinguishes two harness components for AI agents: 'guides' (pre-output constraints) and 'sensors' (post-output checks).
- Guides include rules files, example code, style guides and repository code; sensors include linters, tests, CI checks and audits.
- Guides are cheap to add but can lead to rule fatigue; sensors are costlier but enforce constraints mechanically and can slow iteration.
- Recommended rule of thumb: add a new constraint as a sensor first, then a guide second.
Connected Companies & Entities
1 Entity mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Harness Engineering: From Prompts to System Design
This essay argues that the focus in AI system-building is shifting from prompt quality and model strength to the broader organization of the system — termed "harness engineering." It traces a timeline in which execution‑oriented systems (post‑Codex), Anthropic's long‑running agent guidance, Mitchell Hashimoto's operational framing, and OpenAI's internal practices collectively drove attention toward environment, verification, handoffs, repository structure, observability, and continuous improvement. The piece defines and distinguishes layered practices (prompt, context, agent, workflow, harness), documents common misjudgments (attributing system failures to prompts, equating more tools with maturity, overgeneralizing frontier successes, and dismissing harness as rebranded best practices), and presents evidence that system capability can materially change production outcomes even with the same model.
Harness Engineering: Agent-Ready Development Playbook
The article maps an emerging engineering discipline—called "harness engineering"—where teams reorganize around agentic LLM workflows. Drawing on examples from OpenAI, Stripe, OpenClaw and Anthropic, the piece describes two core engineer roles: building the harness (constraints, linters, tooling, devboxes, AGENTS.md) and managing agent execution (planning, review, accountability, parallelization). It details concrete practices—strict layered architectures, sandboxed pre-warmed devboxes, tool-access via MCP/CLIs, custom linters with remediation messages, and AGENTS.md as a living agent README—and highlights open problems such as maintenance entropy, large-scale verification, retrofitting legacy codebases, and cultural adoption. The author frames the shift as a productivity and process change that moves senior engineers toward architecture and management while agents handle implementation.
Harness Engineering via Markdown for Non‑Coding Agents
A developer describes “harness engineering” practices for non‑coding AI agents, showing how persistent Markdown files (instruction files placed in Project Knowledge / Custom Instructions) can form enforcement layers—prohibited actions, mandatory end‑of‑session actions, and forced knowledge‑accumulation checks—so agents behave more reliably when integrated with business tools like Slack, Confluence and Google Calendar. The post traces the term’s recent codification (Mitchell Hashimoto’s Feb 2026 blog and an OpenAI practice report) and provides repository structure templates and ready‑to‑use examples that let operators build agent harnesses without writing code.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.
