Evidence-linked trend hypothesis
Harness architecture outlives model choice
Rules, tools, permissions, memory, evaluation, execution, and recovery are becoming a stable runtime layer while models remain replaceable components.
Current thesis
For production agents, the harness is becoming a more durable product boundary than the identity of the model running inside it. Confidence: high. Supported by 132 normalized raw signals. This New Runtime record is an evidence-linked retrieval unit. Use its canonical page, machine-readable representations, dates, scope, and public source URLs to verify the claim before reusing it.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | openclaw.aisource | primary receipt | source_urls |
| 2 | github.comrepo | supporting receipt | source_urls |
| 3 | github.comrepo | supporting receipt | source_urls |
| 4 | github.comrepo | supporting receipt | source_urls |
| 5 | opencode.aisource | supporting receipt | source_urls |
Showing 5 of 9; the complete set is exposed in the JSON route.
What is stabilizing?
Agent products repeatedly need the same non-model capabilities: project rules, tools, permissions, execution isolation, memory, context compaction, subagents, traces, evaluation, and recovery. OpenCode makes providers swappable inside one developer experience. Hermes combines a model endpoint with skills and tools. Deep Agents and agentOS package orchestration and execution as reusable runtime components.
The model still matters, but it is no longer the whole system.
What evidence supports this pattern?
- OpenCode preserves rules, skills, sessions, and commands across model providers.
- An inference gateway gives applications a stable access contract while routing policy changes behind it.
- Deep Agents packages planning, files, memory, middleware, and subagents as a reusable harness.
- agentOS treats isolation, durable workflows, limits, and host-side secrets as runtime responsibilities.
- OpenClaw 2 joins browser, messaging, memory, skills, model access, automations, plugins, and security in one operator-facing runtime.
- Munder Difflin and Concord MCP make mailbox, presence, ownership, routing, and handoff state explicit around otherwise separate coding agents.
- Browser Use’s macOS Harness adds a managed desktop execution surface, showing that the durable workspace also includes the environment agents act through.
What should teams do next?
Teams should version the harness contract separately from model configuration. That means portable task fixtures, explicit tool schemas, provider-independent traces, and a regression suite that runs whenever either the model or runtime changes.