Keep efficiency work aligned with just-every/code and Codex CLI

[cbusillo]

Objective

Keep Every Code maintainable as a fork while aligning with upstream just-every/code and Codex CLI behavior where that improves compatibility, safety, and mergeability.

Finish Line

Efficiency and local-agent work lands in small, upstream-aware changes that preserve Every Code-specific strengths: auto-review, multi-provider agents, memory mode, browser/control ergonomics, and autonomous workflows.

Current Status

State: Active
Next action: For each implementation issue under #43, identify whether upstream just-every/code, upstream OpenAI Codex CLI, or Every Code-specific behavior should lead.
Blocked by: None
Last verified: 2026-05-11, parent #43 discussion

Scope

• In: Fork-drift analysis, upstream behavior comparison, small mergeable branches, compatibility-preserving design, and explicit Every Code feature preservation.
• Out: Blindly reverting Every Code features to match upstream or adding broad fork-only abstractions without clear need.

Acceptance Criteria

• Each subtrack records upstream compatibility considerations before implementation.
• Changes preserve auto-review, multi-provider agents, and memory behavior unless an explicit decision says otherwise.
• Fork-specific changes are small and easy to carry across upstream pulls.
• Design notes distinguish just-every/code alignment from OpenAI Codex CLI alignment.

Relationships

Parent: #43
Blocks: final design choices across all implementation subissues.

Validation

Before merging implementation PRs, confirm they do not unnecessarily increase fork drift and still pass repo validation.

Decisions

Every Code should get closer to upstream where it helps, while preserving the features that make it valuable.

Open Questions

Which upstream behaviors are worth adopting directly, and which Every Code behaviors should remain intentionally different?