Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @osfactory/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add osfactory-har -- npx -y @osfactory/har@1.25.1รันในเทอร์มินัล
{ "mcpServers": { "osfactory-har": { "command": "npx", "args": [ "-y", "@osfactory/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
HAR is an open-source for AI coding workflows you can trust and verify. It runs every coding agent in its own isolated, consistent , with deterministic validation, verifiable proof, and full observability. Run one agent or a whole fleet, with the same quality and control. It wraps the tools, tests, and CI you already use, and stays yours to customize.
HAR: open agent harness CLI and MCP server for coding agents, isolated worktrees, and software-factory workflows
Works with Claude Code · Cursor · Codex · any MCP agent.
npm install -g @osfactory/har
cd my-app
har onboard # scaffold .har/ and print a prompt for your coding agent
har env launch 1 # isolated worktree + running stack for agent slot 1
har env verify 1 --full # run the project's real checks, record what passed
Full walkthrough: Quickstart.
Running a coding agent is easy. Trusting what it produced, without re-checking every change by hand, is the hard part, and it only gets harder as tasks grow more complex and you run more agents at once. HAR was built to close those gaps:
No standard way to run or verify a repo. That knowledge is scattered across a README, a CLAUDE.md, Cursor rules, and CI yaml today, drifting out of sync with each other and the actual codebase. HAR replaces all of that with one machine-readable contract (.har/) that Claude Code, Cursor, Codex, or any MCP agent reads the same way.
Multiple agents on one repo collide. Shared dev server, shared database, shared ports, conflicting git state. HAR gives each agent its own worktree, ports, and database per slot, so a fleet can genuinely run concurrently.
Trusting an agent's change means re-verifying it yourself. Every task runs the same deterministic verify step and leaves an evidence trail, logs, artifacts, a validated tree hash, so a reviewer can check proof of what ran instead of relying on the agent's self-report.
One platform's sandbox locks you in. If the contract lives inside a vendor's hosted dashboard, switching coding agents later means rebuilding the whole verification setup. HAR's contract is an open standard living in the repo itself, portable across whichever agent or tool you adopt.
Hand-rolled scripts rot as the stack changes. A new dependency, a new service, a new env var, and nobody updates the script until an agent's run fails for a confusing reason. har env maintain diffs your installed harness against current templates and flags drift before it causes a silent failure.
HAR coordinates the work around the model, so agents can focus on the code and reviewers can trust the result.
flowchart LR
D["Discover<br/>reads the harness contract"] --> I["Isolate<br/>one slot per agent"]
I --> A1["Agent 1<br/>own worktree, branch, ports, DB"] --> B1["Build"] --> V1["Verify"]
I --> A2["Agent 2<br/>own worktree, branch, ports, DB"] --> B2["Build"] --> V2["Verify"]
V1 --> H["Hand off<br/>branch + evidence"]
V2 --> H
Discover. The agent asks the harness what this project looks like, including its stack, its scripts, and what checks are available.
Isolate. Every task gets its own slot. That means a fresh copy of the repo on its own branch, with its own ports and, where the project needs it, its own database. Nothing is shared with the main checkout or with any other agent's slot.
Build. The agent edits and tests its work entirely inside that isolated copy. The main checkout stays untouched the whole time.
Verify. The project's own checks, whatever they are, run through the same pipeline every time and produce a consistent result. A full verification goes further and captures the state of the entire codebase at that moment, so a pass is tied to the exact code that was checked.
Hand off. Once verification passes, the session is torn down, but the branch and the proof of what ran are kept. A reviewer gets the code plus the evidence that it was checked.
Everything beyond install and first commands lives at harproject.dev.
har executable exposes.See CONTRIBUTING.md for local setup, the dogfood harness loop, and architecture. Coding agents working on this repo should start with AGENTS.md. Maintainer release process: RELEASING.md.
HAR is sponsored by Kerno, runtime code and security tester for coding agents.
Licensed under the Apache License 2.0.
Report vulnerabilities via SECURITY.md.
HAR: open agent harness CLI and MCP server for coding agents, isolated worktrees, and software-factory workflows
{ "mcpServers": { "osfactory-har": { "command": "npx", "args": [ "-y", "@osfactory/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@osfactory/har ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 HAR: open agent harness CLI and MCP server for coding agents, isolated worktrees, and software-factory workflows