Use native API formats and compaction endpoints, don't lock into one vendor's harness
pvncher · x · 2026-10-06
In a debate over whether coding harnesses matter, the author argues that with codemode and specialized multi-agent tooling, the harness is far from irrelevant. Practically, regardless of vendor, you should use the native API format and compaction endpoint, abstracting them inside your own harness and bundling the model picker with these implementation details.
The tradeoff: you can't switch models mid-chat across providers, but your product can still support multiple providers. The counterpart counters that no one builds on a single vendor anyway, compaction APIs aren't universal, and harness-irrelevance plus the compaction API are both overreach today.
More from coding & agent
- Laya: Open-Source Model Returns Calibrated Probabilities in 33ms Across 100+ Languages — victormustar · 2026-10-06
- Proactivity-Gym: 23-agent study shows correct work alone can't sustain user trust — minnesotanlp · 2026-10-06
- OpenRUA: off-the-shelf Claude Code drives robots via ROS 2 at 99% success, zero training — Zhaoyang Chu · 2026-10-06
- SearchJev makes search-agent decisions 5x faster with 41-74% lower calibration error — Congfeng Cao · 2026-10-06
- LangChain pitches Managed Deep Agents as a way to monetize personal agent workflows — hwchase17 · 2026-10-06
- Dev envisions local agent 'rooms' no company owns and no server can read — RileyRalmuto · 2026-10-06