Skip to content

Publish provider-owned standalone Codex support #13

Description

@rudijetson

Summary

Publish the already-completed CLI ownership migration that treats Codex as an OpenAI/provider-owned standalone installation while retaining RUDI integration, instructions, skills, and Agent Host launch support.

Invariants

  • Never accept a RUDI-owned executable as the external Codex provider binary.
  • Never remove a legacy installation before a standalone absolute-path version probe succeeds.
  • Preserve Codex auth, configuration, sessions, plugins, and skills.
  • RUDI may detect, integrate, and launch Codex but must not own its executable or updates.
  • Keep the primary follower checkout untouched; verify from the clean dedicated worktree.

Coordinated source

The matching Registry change is the remote codex/codex-standalone-ownership branch in learnrudi/registry.

Acceptance criteria

  • Full CLI tests pass on current origin/main plus the one ownership commit.
  • Build reproducibility, package dry run, and changed-file debt scan pass.
  • Generated manifests encode the provider-owned system contract.
  • Open a focused PR linked to the Registry issue/PR.
  • Do not perform any host installation or migration as part of this follower submission.

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