@nativeharness/core

The parts with no model in them: path scope, identifiers, the text/blob decision, error codes, the event bus, and BashTool — the one tool.

npm install @nativeharness/core

import { BashTool, Events } from "@nativeharness/core";

const events = new Events(store);
const bash = new BashTool({ store, sandbox, events });

One tool, one write path. There is no read, write, edit or grep tool — bash already does those, and routing every change through a single path is what lets versioning, size caps, the delete-ratio guard, path scope and approval each apply once, in one place.

A command's result reports what it did, not just what it printed:

result.exit_code;      // 0
result.files.changed;  // ["/dist/bundle.js"]

The harness cannot tell a read from a write by a tool's name. It knows because collection is a diff.

Part of nativeharness — the agent harness native to your app. Apache-2.0 · docs · source