Skip to content

[3/6] Add protection to the Pi harness plugin - #1877

Draft
shellz-n-stuff wants to merge 1 commit into
codex/security-provider-apifrom
codex/security-pi-integration
Draft

shellz-n-stuff wants to merge 1 commit into
codex/security-provider-apifrom
codex/security-pi-integration

Conversation

@shellz-n-stuff

@shellz-n-stuff shellz-n-stuff commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Pi agents need to stop at the shared protection boundary before consuming context or executing tools. This wires the Pi host and adapter into the captured policy, checks native conversation evidence, and isolates protected runtime state by policy revision. Policy changes retire the previous native sessions before work can resume.

Pi also registers its configured models for temporary, tool-free review inference. Pi unit and live protection tests, along with their macOS CI steps, accompany the adapter changes.

Code flow

[3/6] Add protection to the Pi harness plugin — illustrative code flow

Pi checks native sources, exact tool arguments with history, and held results or errors before their next consumer.

Illustrative flow; checks shown enabled. Source: host.mjs, runtime.ts.

Review and merge bottom to top:

  1. [1/6] Add verified plugin processes and native containment
  2. [2/6] Add agent-bound protection policy and plugin API
  3. [3/6] Add protection to the Pi harness plugin
  4. [4/6] Add protection to the Claude harness plugin
  5. [5/6] Add protection to the Codex harness plugin
  6. [6/6] Add protection to the Goose harness plugin

Validation

TypeScript and the Pi suite pass (111 tests), including the live protection fixture using locked Pi dependencies. The macOS CI lane adds the same Pi fixture at this layer.

Draft. Human app acceptance remains pending. The stack preserves the original implementation without functional changes from splitting it.

Co-authored-by: Codex <codex@openai.com>
Signed-off-by: Alex Rosenzweig <arosenzweig@squareup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant