js-harness

js-harness sets up Claude Code and Codex for AI-assisted development in a project, on top of a stack it does not rebuild: gentle-ai owns the workflow, task documents and TDD, engram owns memory, codegraph owns code structure. js-harness adds the thin layer those leave open: a short AGENTS.md, a pre-commit gate that runs the project’s checks, the two reviews every slice gets (Codex’s, codex-review, and the Claude lenses’, lens-review), task contracts whose end is a set of commands that exit 0, and a record of everything it writes, so that it can be removed exactly.

New here? Start with the user guide: install, the menu, the first run, a typical day and uninstall. This page is the reference of every command.

It is plain Node with no dependencies. It needs Node 24 or newer and git.

Install

The repository is public on GitHub; the install reads it from there.

npm i -g --allow-git=all github:jsaristi/js-harness
js-harness install
cd my-project
js-harness init

1. npm i -g puts the js-harness command on the path; npm 12 fetches a package from git only with --allow-git, and npm 11.12 refuses this one under root, so all. With pnpm: pnpm add -g github:jsaristi/js-harness.
2. js-harness install writes its skills and hooks for Claude Code and Codex under your home, once per machine.
3. js-harness init, in a git repository, writes harness.json (the pin, "code", the project’s identifier its sessions’ titles start with, offered from the initials of its name, and "reply": true, which turns the reply check on), AGENTS.md, an empty failures register (docs/FAILURES.md) and the pre-commit gate of that project.
4. js-harness doctor tells you which tools of the stack are missing and the command that sets up each one.

js-harness --version (or -v, or version) prints the version of the copy on the path, alone on one line. js-harness --help (or -h) prints that command’s usage and runs nothing.

Remove

cd my-project
js-harness uninstall            # what init wrote in this project
js-harness uninstall --global   # what install wrote in the home; the program stays
pnpm remove -g js-harness       # the program; npm rm -g js-harness for an npm install

The last line uses the package manager that installed the program. uninstall --global --everything does the last two in one step and goes further, below.

uninstall --global keeps the snapshots of memory passes, the only copy of what a pass changed, and names them; uninstall --global --full removes them too. Files you modified and the memory notes themselves are kept either way. uninstall --global --everything removes all that js-harness keeps on the machine and then the program itself, so no pnpm remove -g or npm rm -g is needed after it. Projects’ files are kept. Each kind has a name too (uninstall project, machine, snapshots,