Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Changelog

## 0.1.0 — Prototype

First public prototype release.

- Inspect selected POSIX-shell file and Git operations before an integrated agent
runs them, including risky deletion/restoration of protected or locally changed
files and remote history rewrites.
- Integrations are available for Claude Code, Codex, and OpenCode. Live canary
results and tested client versions are recorded in
[compatibility](docs/COMPATIBILITY.md). Antigravity support remains experimental;
live enforcement has not been verified.
- Install with `npm install --global nomeatproxy` (Node.js 22+ and Git required),
then run `nomeatproxy install <agent>` and restart the agent. Codex users must
review and trust the hook through `/hooks`.

### Limitations

NoMeatProxy is a local accident guard, not a sandbox or a security boundary against
a malicious agent. It does not execute checked commands, and it does not inspect
all ways to change files or affect remote systems. Coverage is limited to selected
POSIX shell operations; arbitrary scripts, unsupported wrappers, PowerShell, and
cmd.exe operations may pass without inspection. A passing check means only that no
implemented rule blocked that command. See the [design](docs/DESIGN.md) and
[compatibility notes](docs/COMPATIBILITY.md) for scope and evidence.
3 changes: 2 additions & 1 deletion NOTICE
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
src/shell/tokenize.ts and src/shell/parse.ts are adapted from PlanSentry.
Copyright (c) 2026 plansentry contributors.
Source: https://github.com/RobeyBeswick/plansentry
Source: https://github.com/RobeyBeswick/plansentry (private repository; source is
not publicly available).

PlanSentry is distributed under the MIT License. The permission notice and
disclaimer in this project's LICENSE also apply to these files.
15 changes: 5 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,14 +52,10 @@ review when it’s time to step in.
Requires **Node.js 22+** and **Git**. No model subscription for the guard.
No Go compiler for the standard installation. Your finger may now leave the approval button.

An npm registry release is planned. Build and install from a checkout:
Install from npm:

```sh
git clone https://github.com/RobeyBeswick/nomeatproxy.git
cd nomeatproxy
npm ci
npm pack
npm install --global ./nomeatproxy-0.0.1.tgz
npm install --global nomeatproxy
nomeatproxy install claude
nomeatproxy doctor claude
```
Expand Down Expand Up @@ -107,8 +103,6 @@ faster hook transport. Homebrew distribution is not published yet.

## 🎬 Demo

https://github.com/user-attachments/assets/b013d012-d3b3-4b5c-8163-b9f8041cd38a

[Download the MOV](docs/assets/nomeatproxy-video.mov)

Run the repeatable walkthrough from a checkout:
Expand Down Expand Up @@ -227,7 +221,8 @@ permissions scoped to the work.

Yes. It builds on PlanSentry’s approach: inspect the consequences and show why an
operation needs a human. PlanSentry integration is planned; infrastructure protection
is not included in NoMeatProxy yet. The shell parser is adapted from PlanSentry.
is not included in NoMeatProxy yet. Some shell parsing code is adapted from PlanSentry;
its source repository is private and is not required to use NoMeatProxy. See [NOTICE](NOTICE).

<a id="contributing"></a>

Expand All @@ -244,7 +239,7 @@ npm run evaluate # labeled examples, including known coverage gaps
npm run bench # measure engine and hook overhead
```

[Design](docs/DESIGN.md) · [Roadmap](docs/ROADMAP.md) · [Developer setup](docs/SETUP.md#development) · [Publishing checklist](docs/PUBLISHING.md)
[Design](docs/DESIGN.md) · [Roadmap](docs/ROADMAP.md) · [Developer setup](docs/SETUP.md#development) · [Publishing checklist](https://github.com/RobeyBeswick/nomeatproxy/blob/main/docs/PUBLISHING.md)

## 📄 License

Expand Down
9 changes: 9 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Security policy

NoMeatProxy is a prototype accident guard, not a sandbox or a security boundary
against a malicious agent. Please keep permissions and credentials appropriately
scoped.

To report a suspected vulnerability, use
[GitHub's private vulnerability reporting form](https://github.com/RobeyBeswick/nomeatproxy/security/advisories/new).
Please do not disclose security reports in public issues.
28 changes: 17 additions & 11 deletions docs/COMPATIBILITY.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,18 @@
# Agent compatibility

Measured 2026-10-09. Raw sanitized results: [compatibility.local.json](compatibility.local.json).
Claude Code and Codex were measured 2026-10-09; OpenCode was retested
2026-10-29. Sanitized canary summaries:
[compatibility.local.json](compatibility.local.json).

| Agent | Version | Tested mode | Result |
| --- | --- | --- | --- |
| Claude Code | 2.1.295 | `--dangerously-skip-permissions` | Live canary verified |
| Codex | 0.162.0 | `--dangerously-bypass-approvals-and-sandbox`, with invocation-scoped hook trust bypass | Live canary verified |
| OpenCode | 1.18.30 | `--auto` | Live canary verified |
| Antigravity | Live version not checked | Documented `run_command` protocol | Adapter/configuration tests only |
| Agent | Version | Test date | Tested mode | Result |
| --- | --- | --- | --- | --- |
| Claude Code | 2.1.295 | 2026-10-09 | `--dangerously-skip-permissions` | Live canary verified |
| Codex | 0.162.0 | 2026-10-09 | `--dangerously-bypass-approvals-and-sandbox`, with invocation-scoped hook trust bypass | Live canary verified |
| OpenCode | 1.19.5 | 2026-10-29 | `--auto` | Live canary verified |
| Antigravity | Live version not checked | — | Documented `run_command` protocol | Adapter/configuration tests only |

Claude Code and Codex have not been retested since 2026-10-09. Their listed
versions are the older tested versions, not a claim about current releases.

## What the live result establishes

Expand All @@ -22,10 +27,11 @@ All three agents exited successfully without working around the block. The
recorded host tool names were `Bash` for Claude/Codex and `bash` for OpenCode.
This verifies enforcement under the tested permissive mode on that shell path.

The Claude and Codex canaries exercised the direct Node hook. The OpenCode canary
used its in-process plugin. The native resident path has separate parity and
failure-mode tests plus a benchmark; it has not yet been exercised through a
live agent in this run.
The Claude and Codex canaries exercised the direct Node hook. The OpenCode canaries
used its in-process plugin. The 2026-10-29 OpenCode run observed both the allowed
control and blocked disposable deletion, and preserved the sentinel. The native
resident path has separate parity and failure-mode tests plus a benchmark; it has
not yet been exercised through a live agent.

This is not certification for every native tool, code-mode call, background
process, shell continuation, remote tool, or future client version. The two
Expand Down
120 changes: 60 additions & 60 deletions docs/PUBLISHING.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,31 +8,31 @@ The handoff itself does not publish a package or change repository visibility.

| Area | Status |
| --- | --- |
| Source | `main`; implementation last changed before this documentation handoff |
| Package | `0.0.1`, with `"private": true`; publishing is disabled |
| GitHub | Repository is private; no release or version tag exists |
| npm | No package found when checked on 2026-10-27; recheck before release |
| CI | Latest `Check` run did not start its jobs because of a billing/spending-limit block |
| Live compatibility | Results dated 2026-10-09; refresh for the clients named in the launch |
| Public-content review | Basic text/history scan completed; dedicated secret scan, video, and Actions-log review remain |

Local verification on 2026-10-27 passed against commit `cdddb08`:

- Typecheck and all 86 tests.
- Packed-package installation test: 33 files, approximately 38 KiB compressed.
- All eight native-transport tests.
- Evaluation corpus, including its explicitly documented coverage gaps.
- npm audit: zero reported vulnerabilities.

These results are a baseline. Rerun verification after release changes and on the
personal laptop. The earlier pattern scan covered six commits and found no
obvious personal paths, internal domains, account IDs, or credential patterns;
it was not a complete secret or media review.
| Source | `chore/public-launch`, release-preparation changes based on `main` |
| Package | `0.1.0`, publishing enabled in the release branch |
| GitHub | Repository is public; no release or version tag exists |
| npm | Package returned 404 on 2026-10-29; npm authentication is now confirmed, but the package is not published |
| CI | All six PR matrix jobs passed on release head `be30fdc` on 2026-10-29 |
| Live compatibility | OpenCode 1.19.5 verified 2026-10-29; Claude Code 2.1.295 and Codex 0.162.0 remain tested 2026-10-09; Antigravity is adapter-only |
| Public-content review | Gitleaks and Actions-log scans clean; artifact inspected; visual sampling every 2 seconds and user audio review found no private demo content; signed-out link check found a broken attachment URL, removed in this branch |

Local verification on 2026-10-29 passed on `chore/public-launch` with Node.js
22.23.4/npm 10.9.9 and Node.js 24.22.2/npm 11.19.1, with Go installed:

- `npm ci` and `npm run check` passed on both Node versions. Node 22: 80 tests passed, 6 native tests skipped; separate native run passed all 8. Node 24: all 86 tests passed, plus all 8 native tests.
- Packed-package installation test: 35 files, approximately 39 KiB compressed, on both Node versions.
- Evaluation corpus: 16 benign cases, 17 covered hazards, and three explicit coverage gaps.
- `npm run demo -- --auto` and `npm pack --dry-run`; the package includes the changelog and security policy, excludes this publishing checklist, local reports, fixtures, native binaries, and the demo video.
- `npm audit`: zero reported vulnerabilities. `npm outdated` found no newer compatible versions; `npm update` made no dependency changes.
- `gitleaks git --redact .`: history scan and current-file scan found no leaks.

Rerun verification on the exact final `main` commit and repeat the signed-out
link check after the release PR is merged.

## 1. Set up the personal laptop

- [ ] Install Git, Node.js 22 or 24 with npm, and the GitHub CLI.
- [ ] Authenticate the GitHub CLI with an account that can access this private
- [x] Install Git, Node.js 22 or 24 with npm, and the GitHub CLI.
- [x] Authenticate the GitHub CLI with an account that can access this private
repository. Run `gh auth login` if needed, then clone:

```sh
Expand All @@ -42,11 +42,11 @@ git status --short --branch
npm ci
```

- [ ] Install Go if validating the optional native transport. The standard npm
- [x] Install Go if validating the optional native transport. The standard npm
package does not require Go; see [setup](SETUP.md#optional-fast-transport).
- [ ] Install and authenticate any agent clients used for live compatibility
- [x] Install and authenticate any agent clients used for live compatibility
checks. Do not copy credentials or agent settings into this repository.
- [ ] Confirm access to the npm account that will own the package:
- [x] Confirm access to the npm account that will own the package:

```sh
npm login
Expand All @@ -60,19 +60,18 @@ package name and update documentation and packaging tests before continuing.

## 2. Finish the public-content review

- [ ] Run a history-aware secret scan, for example `gitleaks git --redact .`
- [x] Run a history-aware secret scan, for example `gitleaks git --redact .`
after installing Gitleaks, and inspect any findings.
- [ ] Review tracked files and commit metadata for personal paths, internal
- [x] Review tracked files and commit metadata for personal paths, internal
URLs, account IDs, customer details, and secrets. Keep scan reports private.
- [ ] Watch `docs/assets/nomeatproxy-video.mov` and inspect the embedded README
video for private terminal content, notifications, paths, and identifiers.
- [ ] Review existing Actions logs and artifacts before changing visibility;
- [x] Watch `docs/assets/nomeatproxy-video.mov` and inspect the README video for
private terminal content, notifications, paths, and identifiers.
- [x] Review existing Actions logs and artifacts before changing visibility;
they can become publicly accessible with the repository.
- [ ] Check links as an outside reader. `NOTICE` references PlanSentry, whose
repository was private at the previous review. Preserve the copyright and
license attribution; clarify source availability or publish the upstream
separately if intended. This release does not require making another
repository public.
- [ ] Check links as an outside reader. The PlanSentry source repository remains
private; its source availability is clarified in `NOTICE`. Preserve the
copyright and license attribution. This release does not require making
another repository public.

Remove sensitive material from history as well as the current checkout if any
is found, and rotate exposed credentials before publishing.
Expand All @@ -92,11 +91,11 @@ git diff -- package.json package-lock.json
`npm outdated` can exit nonzero when it finds newer versions. Review the output
before continuing; do not treat every newer major as required release work.

- [ ] Confirm `package.json` and `package-lock.json` both report `0.1.0`, with
- [x] Confirm `package.json` and `package-lock.json` both report `0.1.0`, with
publishing enabled.
- [ ] Review every dependency change and commit the lockfile.
- [ ] Keep Node types aligned with the minimum supported runtime.
- [ ] If changing the supported Node versions, update `engines`, documentation,
- [x] Review dependency changes and commit the lockfile.
- [x] Keep Node types aligned with the minimum supported runtime.
- [x] If changing the supported Node versions, update `engines`, documentation,
and the CI matrix together.

The handoff baseline uses TypeScript `5.9.3` and locked Node types `22.20.5`.
Expand All @@ -110,16 +109,16 @@ matrix to pass. Action modernization can follow the first release.

## 4. Prepare the release documentation

- [ ] Update the quickstart in [README](../README.md) and [setup](SETUP.md) to
- [x] Update the quickstart in [README](../README.md) and [setup](SETUP.md) to
use the registry installation below when the package is published.
- [ ] Update retained tarball examples from `0.0.1` to `0.1.0`.
- [ ] Add a root `CHANGELOG.md` entry for `0.1.0`, including supported operations,
- [x] Update retained tarball examples from `0.0.1` to `0.1.0`.
- [x] Add a root `CHANGELOG.md` entry for `0.1.0`, including supported operations,
agent integrations, installation, and known limitations.
- [ ] Add a root `SECURITY.md` with a working private reporting route. Configure
- [x] Add a root `SECURITY.md` with a working private reporting route. Configure
that route before advertising it.
- [ ] Keep the prototype label, POSIX-shell coverage limits, and Antigravity's
- [x] Keep the prototype label, POSIX-shell coverage limits, and Antigravity's
experimental status unless fresh evidence supports changing them.
- [ ] Keep benchmark claims tied to their measured runtime and transport.
- [x] Keep benchmark claims tied to their measured runtime and transport.
The advertised native/resident timing is not the default Node CLI timing.
- [ ] Update the npm milestone in [roadmap](ROADMAP.md) after publication succeeds.

Expand All @@ -146,15 +145,15 @@ node scripts/compat.mjs codex
node scripts/compat.mjs opencode
```

- [ ] Verify each advertised integration observes the allowed control, blocks
- [x] Verify each advertised integration observes the allowed control, blocks
the disposable deletion canary, and preserves the sentinel.
- [ ] Record actual client versions, test date, mode, and results in
- [x] Record actual client versions, test date, mode, and results in
[compatibility](COMPATIBILITY.md).
- [ ] Sanitize any results copied to `docs/compatibility.local.json`; keep raw
- [x] Sanitize any results copied to `docs/compatibility.local.json`; keep raw
transcripts, temporary paths, and authentication details out of Git.
- [ ] If a client cannot be validated, state the older tested version or narrow
- [x] If a client cannot be validated, state the older tested version or narrow
the launch claim. Do not label an inconclusive run as a pass.
- [ ] Leave Antigravity experimental unless live enforcement is validated.
- [x] Leave Antigravity experimental unless live enforcement is validated.

The harness invokes real clients and can consume their configured model usage.
Its requests target a disposable test fixture. Follow the full scope and limits
Expand All @@ -178,30 +177,31 @@ Run `test:native` on macOS/Linux with Go installed. If the optional transport is
not tested on this machine, retain the earlier dated evidence and do not claim
it was freshly validated.

- [ ] All applicable checks pass.
- [ ] Inspect the package file list: compiled JavaScript, declarations,
documentation, and licensing are present; secrets, local reports, fixtures,
native binaries, and the demo video are absent.
- [ ] Review and commit release changes with a conventional commit message.
- [x] All applicable local checks pass.
- [x] Inspect the package file list: compiled JavaScript, declarations, product
documentation, changelog, security policy, and licensing are present; the
publishing checklist, local reports, fixtures, native binaries, and demo video
are absent.
- [x] Review and commit release changes with a conventional commit message.
Stage specific intended files rather than generated reports or credentials.
- [ ] Push the branch and merge through a reviewed pull request:

```sh
git push -u origin chore/public-launch
```

- [ ] Resolve the Actions billing/spending-limit block and obtain a successful
`Check` run for the final release commit. All six combinations of macOS,
Linux, Windows, and Node 22/24 should pass.
- [x] Obtain a successful `Check` run for the release candidate. All six jobs
passed on `be30fdc`; rerun after any additional release-content changes. The
matrix covers macOS, Linux, Windows, and Node 22/24.

If changing visibility before rerunning CI is necessary, complete the public
review first. Still require passing CI before publishing the package or post.

## 7. Make the source public and build the final tarball

- [ ] In GitHub repository settings, use **General → Danger Zone → Change
- [x] In GitHub repository settings, use **General → Danger Zone → Change
visibility → Public** when ready to expose the reviewed source and history.
- [ ] Check the repository, README, embedded video, and documentation links in a
- [ ] Check the repository, README, video download, and documentation links in a
signed-out browser.
- [ ] After the release branch is merged, use the exact verified commit on main:

Expand Down
Loading
Loading