AIAny
AI Agent2025
Icon for item

Claude Code Harness

Provides a Plan→Work→Review→Release harness for Claude Code agent workflows that enforces spec-driven tasks, TDD-backed implementation, independent review, and packaged evidence for PRs/releases. Exposes plugin/CLI commands and a Go-native guardrail engine to keep agent-driven code delivery reproducible and auditable.

Visit Website

Introduction

Agent-driven coding often drifts: plans live only in chat, tests become optional, reviews happen too late, and release evidence is rebuilt from memory. That hidden entropy makes agent outputs hard to trust for production work. Claude Code Harness flips the starting point from “ask the agent to code” to “approve a narrow, observable contract” so automation stays verifiable.

What Sets It Apart
  • Spec-first operating loop: Harness generates and treats spec.md and Plans.md as the source of truth, so unknowns remain explicit and the agent cannot silently invent data. This reduces drift and makes acceptance criteria machine-checkable.
  • Enforced implement/review gates: /harness-work runs focused tasks with TDD and verification while /harness-review separates independent review from implementation. That division reduces bias and catches integration issues earlier.
  • Evidence packaging for release: /harness-release and the release preflight collect verifiable artifacts (tests, verification output, changelog boundaries) so PR-ready work can be validated for release readiness without reconstructing state later.
  • Tool & runtime alignment: Designed as a Claude Code plugin path (Claude Code v2.1+), with Go-native guardrails and compatibility paths for Codex/OpenCode, so it integrates into agent-first toolchains rather than replacing them.
Who it's for + Trade-offs

Great fit if you run agent-assisted engineering at scale and need reproducible, auditable delivery—teams using Claude Code who want to enforce TDD, independent review, and clear acceptance gates. It presumes a repository with write access, an established agent runtime (Claude Code v2.1+), and a willingness to move from ad-hoc prompts to an approved plan-and-slice workflow.

Look elsewhere if you need a lightweight prompt helper for ad-hoc exploration (Harness adds process overhead), if you cannot provide repository write access, or if your environment cannot run the required Claude Code plugin paths. The design favors provability and gateability over speed of one-off experimentation.

Back

Information

  • Websitegithub.com
  • AuthorsChachamaru127
  • Published date2025/12/12

Categories

Tags

More Items

AI Agent Papers2026
Icon for item

SearchOS-V1: Towards Robust Open-Domain Information-Seeking Agent Collaboration

Yuyao Zhang, Junjie Gao +12

Turns fragile, implicit search progress into explicit, persistent, shared state for multi-agent information seeking — externalizes progress as Frontier Task, Evidence Graph, Coverage Map and Failure Memory, and uses pipeline-parallel scheduling plus a middleware harness to avoid repeated failed searches and improve utilization and throughput.

LLMai-agentagent-skillsnlppaper+3
GitHub
AI Agent2026
Icon for item

OpenHarness

HKUDS

Provides a lightweight Python harness that turns LLMs into working agents with tool-use, skills, persistent memory, permission controls and multi-agent coordination. Ships with a CLI/React TUI, 43+ built-in tools, a plugin/skill system and the ohmo personal-agent for chat gateways. Best for developers prototyping agent workflows and multi-agent experiments.

agent-skillsmcpmcp-clientai-agentcli+10
GitHub
AI Client2025
Icon for item

BrowserOS

Nithin Sonti, Nikhil Sonti +1Felafax, Inc., browseros-ai (GitHub)

Turns Chromium into a local-first AI browser with an embedded assistant that can summarise pages, extract structured data, automate web tasks, and run scheduled agents. Built as an open-source Chromium fork with 53+ built-in browser tools, 40+ app integrations, and support for BYO AI keys or fully local models (Ollama / LM Studio).

mcpmcp-servermcp-clientai-agentai-client+8