Agent Harness

Agent harness is not limited to OpenAI Codex or to an app server. In the broadest definition, it is everything around the model that makes agentic work possible: prompts, state, tool execution, permissions, memory, planning, environment access, feedback, evaluation, and handoff artifacts.

• Runtime harness: agent loop, tools, filesystem, browser, shell, sandbox, approvals, events, and persistence.
• Long-running harness: initializer agents, progress files, work decomposition, context-window handoff, and artifacts for the next session.
• User harness: AGENTS.md, repo docs, test matrices, linters, review agents, browser checks, logs, and domain-specific skills.
• Adapter harness: a unified interface over Codex, Claude Code, Cursor, OpenCode, Gemini CLI, or other agent executors.
• Evaluation harness: reproducible runs, traces, budget controls, model snapshots, scoring, and regression checks.

OpenAI emphasizes engineering environments and feedback loops around Codex. Anthropic emphasizes long-running work across many context windows. Martin Fowler emphasizes feedforward guides and feedback sensors that let coding agents self-correct before humans review the result. LangChain lists harness capabilities such as planning, virtual filesystem, permissions, subagents, context management, code execution, human-in-the-loop, skills, and memory. Rebyte and harness.lol use the term for swappable executors and unified interfaces across coding agents.

A framework is usually a developer library or SDK for composing agent logic. A harness can include a framework, but it also includes the runtime, environment, controls, feedback signals, and user-side operating system around the agent. This is why two agents using the same model can perform differently when their harnesses differ.

A harness that cannot emit useful traces is hard to improve. Agent traces show prompts, tool calls, observations, command output, failures, retries, and approvals, which makes it possible to turn one bad run into an eval or a harness change. Public trace datasets are useful for research and comparison, but private project traces need redaction and access control before sharing.

Claude Tag shows a team-channel version of the harness. The harness is not only terminal access or tool calls; it also includes who the agent is in the organization, which Slack channel grants context, which connectors it can reach, whether memory crosses channels, how credential use is logged, and when the agent must tag a human back for a decision. That boundary is why team agents need admin-scoped identity and audit evidence, not only better prompts.

Current HN and official-source checks show that the harness idea is becoming easier for readers to see in real tools. OpenCode puts planning, building, subagents, package installation, and desktop/terminal surfaces around a coding model. Claude Tag puts a team-facing identity, Slack thread context, connector scope, memory boundary, and review loop around Claude. Runtime turns the harness into team infrastructure with sandboxes, integrations, guardrails, observability, and self-hosting. Zot packages a terminal coding agent as one Go binary with built-in tools, provider routing, extensions, sessions, and background subagents. Forge sits inside an agentic loop as guardrails middleware for tool-call reliability. Zerostack shows the small-agent end of the spectrum. Reasonix adds a provider-native DeepSeek loop around prefix-cache stability. Superset orchestrates many CLI agents through worktrees and review. DevSpace shows the connector version of the same pattern: a self-hosted MCP server lets a chat host use local files, shell commands, project instructions, skills, and worktrees. InsForge exposes backend state and actions through MCP, CLI, and skills.