Skip to content

ai-memory consolidation: dated note on GPT-6 models and upstream #852 - #313

Merged
seathatflowsinourveins merged 1 commit into
mainfrom
claude/gpt6-consolidation-note-20260926
Sep 26, 2026
Merged

seathatflowsinourveins merged 1 commit into
mainfrom
claude/gpt6-consolidation-note-20260926

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator

Scope

  • What this changes: adds a dated paragraph to docs/native-memory-consolidation.md for hosts running ai-memory with Codex-provider consolidation. It explains why GPT-6 models fail on 2.3.2 and 2.4.0, and which upstream fix and release carry the fix.
  • Base commit: origin/main at the time of rebase.
  • Lane: lane:foundation.
  • Owned paths touched: docs/native-memory-consolidation.md and manifests/evidence.json (hash re-registration only).

SOTA sources

  • akitaonrails/ai-memory #852, "fix(llm): omit temperature for gpt-6 models": merge f7ec2eda6e6579cbcb5dfa9b8343d6b81932716c, issue #851. The changes are in crates/ai-memory-llm/src/{openai_oauth.rs,openai.rs,copilot.rs}.
  • Releases carrying the fix: v2.4.1 (tag commit 433a19f3) and release/2.5 (dde5806b). v2.3.2 (353841d9) and v2.4.0 (b1b25219) lack it; their request predicates skip temperature only for gpt-5/o*.
  • akitaonrails/ai-memory #859: the prefix backport that keeps the laptop on 2.3.2.

Evidence-class table

Claim Class
gpt-6-luna, gpt-6-sol and gpt-6-astra return 400 Unsupported parameter: temperature through a 2.3.2 build (6 of 6 runs) native_proven on the WSL authoring laptop
2.4.0 behaves the same source_review: the three request files are the same blobs as 2.3.2
The laptop build's three changed files are byte-identical to f7ec2eda; the live service runs it with gpt-6-sol source_review and native_proven. Two independent reviews: a Claude evidence-reviewer and a Codex gpt-6-astra/ultra cross-review (SAFE_TO_DEPLOY). After restart, a live structured gpt-6-sol call succeeded.
gpt-6-sol is the better consolidation model Not claimed: keep-but-compare (n=2)
A 2.4.1 host can set a GPT-6 model directly source_review only

Checks:

  • scripts/validate.py: passed.
  • evidence_manifest.py --check: passed.
  • Full python3 -m unittest (before the wording-only revision): 5784 tests, OK.
  • Guarded gitleaks on origin/main..HEAD: no leaks.
  • The reviewer's wording fixes are applied verbatim.

🤖 Generated with Claude Code

With llm_provider = "codex", ai-memory 2.3.2/2.4.0 send temperature and gpt-6-luna,
gpt-6-sol and gpt-6-astra reject it (400). Upstream #852 (f7ec2eda) omits it; it ships in
v2.4.1 and release/2.5. Records the laptop's 2.3.2 build carrying the #859 and #852
backports, running gpt-6-sol (keep-but-compare) since 2026-09-26.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Sep 26, 2026
@seathatflowsinourveins
seathatflowsinourveins enabled auto-merge (squash) September 26, 2026 02:31
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant