Skip to content

Bind actual native Codex and Node runtime behind the M5 helper wrapper #215

Open

Description

@realmarcin

Independent read-only review of PR #214 found that the new helper launcher pins the codex entrypoint symlink/JavaScript but not the executable it actually launches. On M5, bin/codex resolves to the npm codex.js wrapper, which resolves the codex-darwin-arm64 package and executes its native binary. A changed native binary or Node runtime can therefore pass check_runtime and inherited-canary checks while retaining the same JavaScript bytes.

Before the first live helper canary, bind and replay the actual resolved native executable, Node interpreter and resolution metadata, or invoke the pinned native executable through the work-account wrapper with a narrowly controlled PATH. Add a regression that keeps the entrypoint fixed while the native executable changes. Retain work-account selection and no model override. This is an execution identity guard, not scientific validation. No native helper was launched before the finding.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions