Skip to content

Check upstream changes from just-every/code and openai/codex #124

@cbusillo

Description

@cbusillo

Objective

Review recent upstream changes from just-every/code and openai/codex and decide what Every Code should import, adapt, ignore, or track separately.

Current Status

State: Immediate OpenAI Codex upstream intake is complete; #214, #215, #216, and #225 are done.
Next action: Decide whether to pick up desktop remote-control compatibility (#217/#37) or continue with the in-progress manual skill discovery branch.
Blocked by: None.
Waiting for: Product choice on remote/desktop direction before starting #226/#227.
Last verified: 2026-05-30.

Completed intake:

Remaining parked follow-ups:

Decision:
Do not port Codex CLI features just for parity. Codex desktop remote-control compatibility remains design work under #217/#37.

Scope

  • In: Recent commits, workflow changes, prompt/system instruction changes, agent/model routing changes, model metadata/default changes, release/build fixes, bug fixes, and compatibility-relevant behavior from just-every/code and openai/codex.
  • Out: Blind bulk merges, large tree rewrites, or adopting upstream behavior that erases intentional Every Code product differences without an explicit decision.

Acceptance Criteria

  • Current refs/remotes for just-every/code and openai/codex are fetched or otherwise verified.
  • A concise delta summary is produced for each upstream.
  • Candidate imports are classified as import now, adapt first, defer, or reject.
  • Prompt/system instruction changes are explicitly checked.
  • Model metadata/default changes, including any GPT-5.6-related changes, are explicitly checked.
  • Release/build workflow changes are explicitly checked.
  • App-server, app-server-protocol, remote-control, session lifecycle, file-watch, and auth/server changes from Codex CLI since the fork are explicitly checked.
  • The selected implementation batch is split into focused follow-up PRs or issues.
  • Each selected import explains the Every Code product value or hardening value; parity alone is not sufficient.

Validation

Use git comparisons against the relevant upstream refs, inspect changed prompt/workflow/build/model files directly, and run ./build-fast.sh on any implementation PR that imports changes.

Relationships

Related to #51 for ongoing upstream alignment.
Related to #85 for Every Code product independence and import policy.
Related to #195 for GPT-5.6 model metadata readiness.
Sub-issues:

Notes

Preserve Every Code-specific behavior unless there is a clear compatibility, safety, or maintenance reason to change it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions