The article argues that giving AI agents access to flexible command-line interfaces is more efficient than using many specialized MCP servers because it reduces context window bloat and enables powerful tool composition through piping.
* Specialized tools often clutter the model's context, while a single CLI allows data to flow directly between processes without increasing token costs.
* Terminal access facilitates complex workflows like multi-environment tasks and cross-tool automation that are cumbersome with individual MCP servers.
* Although providing terminal access increases security risks, these can be managed through sandboxing and restricted user permissions.
* Specialized tools often clutter the model's context, while a single CLI allows data to flow directly between processes without increasing token costs.
* Terminal access facilitates complex workflows like multi-environment tasks and cross-tool automation that are cumbersome with individual MCP servers.
* Although providing terminal access increases security risks, these can be managed through sandboxing and restricted user permissions.
The author proposes a 5-layer framework to standardize "harness engineering":
1. **Constraint (Architecture):** Deterministic rules (linters, API contracts).
2. **Context (Dev):** Memory and knowledge injection.
3. **Execution (Platform):** Tool orchestration and sandboxing.
4. **Verification (Dev/QA):** Output validation and error loops.
5. **Lifecycle (SRE):** Monitoring, cost tracking, and recovery.
**Strategic Insight:** While platforms like Anthropic are increasingly absorbing the Context, Execution, and Lifecycle layers, developers must still own **Constraint** and **Verification**. To maximize efficiency on managed platforms, teams should prioritize deterministic constraints (Layer 1) to reduce token waste and improve reliability.
1. **Constraint (Architecture):** Deterministic rules (linters, API contracts).
2. **Context (Dev):** Memory and knowledge injection.
3. **Execution (Platform):** Tool orchestration and sandboxing.
4. **Verification (Dev/QA):** Output validation and error loops.
5. **Lifecycle (SRE):** Monitoring, cost tracking, and recovery.
**Strategic Insight:** While platforms like Anthropic are increasingly absorbing the Context, Execution, and Lifecycle layers, developers must still own **Constraint** and **Verification**. To maximize efficiency on managed platforms, teams should prioritize deterministic constraints (Layer 1) to reduce token waste and improve reliability.
This paper introduces Natural-Language Agent Harnesses (NLAHs) – a new approach to AI agent harness design. NLAHs use editable natural language, improving portability and study, unlike traditional code-embedded harnesses. The authors also present the Intelligent Harness Runtime (IHR) and demonstrate viability through coding/computer-use benchmarks.
