The danger is losing sight of what happens next. Nemeris keeps Claude Code on plan.
The
Nemeris plugin.
Keeps Claude Code
inside your plan.
Windows today, macOS and Linux on the way.
One payment. One machine. Yours to keep. Updates to this version.
What it is
Nemeris is a plugin that makes Claude Code prove its work at every step.
On your own machine. Against its own bands of verification, or against a plan you signed: change it after signing, and the band refuses the work until you sign again.
How it works
Claude Code can write thousands of lines before you know something went wrong.
And if you don’t understand the code, finding the mistake yourself is not much of a safety system.
Skipping a step is the cheapest thing an agent can do, and the hardest thing to notice afterwards. Here the band refuses it: the fourth stage is refused on work the third never did.
It settles what will be touched, and what will not.
Show the evidence - the stage the work is waiting at proves what it did. That is the only thing that opens the next gate.
Watch it again - sends the work back to the start and runs the route again. Gates you have already opened stay open.
- The Preparer✓ scope, written down
- The Librarian✓ sources, listed
- The Solver✓ the change, bounded
- The Tester✓ output, compared
The prompt
You’re approving what you don’t understand.
One wrong click can let Claude Code change more than you meant to.
npx tsx scripts/rename-fields.ts --write src/ --force
- In the plan
- Unknown
- Touches
- Unknown
- Outside the plan
- Unknown
- If it strays
- Unknown
npx tsx scripts/rename-fields.ts --write src/ --force
- In the plan
- Yes, signed before the work started
- Touches
- 3 files under src/db/
- Outside the plan
- Everything else in the repo
- If it strays
- The stray is caught; the commit is refused.
The plan was signed before the work started. Edit it afterwards to fit what happened, and the band refuses the work; changing course means signing a new plan.
Approval is not control. Context is.
The 3 outlined ones are the times somebody said no.
You don’t trust Claude Code. You still click approve.
You say yes 97 times out of 100.*
Source: Anthropic, August 2026
* Anthropic’s figure: users approve 97% of permission prompts under manual review. In Auto mode, a second model reviews actions instead of you; Anthropic says the mode reduces prompts but does not guarantee safety.
Ask somebody often enough and saying yes becomes a habit. Anthropic writes that many users click through reflexively.
This is the gap Nemeris is built for
01Approve the plan
You say what should be built, what may change, and what has to prove it works. Then you sign it, with a signature only you control.
02Nemeris holds the boundary
The work is held against the signed plan as it runs. What falls outside it is refused, and the reason is shown.
03You get proof
The finished work leaves a record of what happened and whether the agreed requirements were actually demonstrated.
Four moments, and the one you skip.
Not a watcher and not a scan on a schedule. Four positions in a session you already recognise, arranged around the one that is easy to skip.
You ask
A prompt, and a plan comes back.
signs the plan
You read
The part that is easy to skip.
Not a moment Nemeris has. The one it was built around.
It writes
Inside the plan, or refused with the reason shown.
holds the boundary
It runs
One phase closes before the next opens.
closes the phase
You commit
The record ships with the code.
writes the record
Built on
- Claude Code
- Python
- OpenSSH
- Git
- PowerShell
- SHA-256
No npm. No Node. No packages.
Python standard library only. Nothing from your code is sent to us. See what is sent
Claude Code
The agent that writes the code. Nemeris installs into it and runs inside it.
Python
The language the whole of it is written in. Standard library only, so there is nothing else to install.
OpenSSH
The key toolkit already on every developer machine. Keys instead of passwords.
Git
Where the code already lives. The record ships with it, not to a dashboard somewhere else.
PowerShell
Windows' own shell. Where the work is already happening, and where Nemeris installs from.
SHA-256
A fingerprint for data. Change one character anywhere and the whole fingerprint changes.
What you get
Four linesinstead of four hundred.
The same change, twice. Nothing about the work is different, only what lands in front of whoever has to check it.
18 changed lines across 3 files
read all of it, then decide whether it was tested
one line, next to the same commit
record2026-08-23upload rate limit4 of 45e9c3c7dc8e3
- read
- 14 files, 2 configs
- filed
- 6 notes
- written
- 3 files, 148 added, 22 removed
- ran
- 41 tests, all green
read four lines, and you know
What the licence installs
12areas
audited.
1 price. 2 tools.
No monthly subscriptions.
Fixes and security updates included.
Nemeris Audit comes with every licence. Ask Claude, and it goes through your code 12 ways. It works on its own, with or without the 4 stages.
1 critical1 major2 minor8 pass
You see 4. Your report names all 12, on your own code.
Nemeris and Nemeris Audit. 1 licence, paid once.
Evidence, not opinions.
Each finding in the report says what was checked and what was found.
Audit first, then commit.
When Claude runs a commit command, it is refused until an audit of that code has been done and recorded. After the first audit in a project, git also checks ordinary commits from scripts and from you, if your project's git settings allow it. It is not a guarantee: a script or a git command can still get around it. When you need to, you can still commit without it.
A report you keep.
Written into your project, ranked critical, major and minor.
Founder licence
Own the tool.
Not another subscription.
€89once.
Nemeris is yours on 1 machine, with both modes unlocked from day one. Nemeris Audit is included.
Windows today, macOS and Linux on the way.
Source visible, commercial licence.
If your card is in another currency, your bank converts it.
Questions before you buy? Read the FAQ.
No more monthly fees, feature tiers, cloud dependency, or surprise paywalls.