hq: prefer API-key codex auth and run the assistant on gpt-5.6-terra #25

Merged

founder merged 1 commit from hq-codex-apikey-and-models into main

2026-08-01 09:57:33 +00:00

founder commented

2026-08-01 09:57:26 +00:00

Owner

HQ carries its own copy of the codex-login unit rather than importing the forge module — so it carried its own copy of the bug too. Caught live during today's HQ deploy:

[codex-login] replaced auth.json from newer agenix seed (2026-05-22... > missing)

install_auth_seed_if_newer succeeds whenever the seed merely exists (so the API-key branch was unreachable), and an api-key auth.json has no last_refresh — so the expired ChatGPT seed always compared "newer" and reinstated itself. That is what left the assistant identity dead from 2026-05-28.

The live host is currently held together by a last_refresh timestamp I stamped by hand to defeat that comparison; this replaces the workaround with the same codexPreferApiKey switch the forge uses.

Also: the assistant runs on HQ, not the forge, so this file decides its model — it was still pinned to gpt-5.4-mini at low effort while the forge had moved to gpt-5.6-terra at medium. Now aligned.

🤖 Generated with Claude Code

HQ carries its **own copy** of the codex-login unit rather than importing the forge module — so it carried its own copy of the bug too. Caught live during today's HQ deploy: ``` [codex-login] replaced auth.json from newer agenix seed (2026-05-22... > missing) ``` `install_auth_seed_if_newer` succeeds whenever the seed merely exists (so the API-key branch was unreachable), and an api-key `auth.json` has no `last_refresh` — so the expired ChatGPT seed always compared "newer" and reinstated itself. **That is what left the assistant identity dead from 2026-05-28.** The live host is currently held together by a `last_refresh` timestamp I stamped by hand to defeat that comparison; this replaces the workaround with the same `codexPreferApiKey` switch the forge uses. Also: **the assistant runs on HQ, not the forge**, so this file decides its model — it was still pinned to `gpt-5.4-mini` at low effort while the forge had moved to `gpt-5.6-terra` at medium. Now aligned. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

founder added 1 commit

2026-08-01 09:57:26 +00:00

hq: prefer API-key codex auth and run the assistant on gpt-5.6-terra

Release: If Needed / Check (Release Needed) (push) Successful in 5s

Details

Deploy: Web / Deploy (Web) (push) Failing after 8s

Details

Deploy: API / Deploy (API) (push) Successful in 2m58s

Details

ddeb36d255

HQ carries its own copy of the codex-login unit rather than importing the
forge module, so it also carried its own copy of the bug the forge fix
addressed. Observed on HQ during today's deploy:

  [codex-login] replaced auth.json from newer agenix seed (2026-05-22... > missing)

install_auth_seed_if_newer returns success whenever the seed merely exists, so
the API-key branch was unreachable, and an api-key auth.json has no
`last_refresh`, so the expired ChatGPT seed always compared "newer" and
reinstated itself over a working login. That is what left the assistant identity
dead from 2026-05-28: the supervisor spun on token refresh while its queue grew.

The live host is currently held together by a `last_refresh` timestamp stamped
into auth.json by hand, which defeats the comparison. This replaces that
workaround with the same codexPreferApiKey switch the forge uses.

Also point HQ at the models actually requested. The assistant identity runs on
HQ, not the forge, so this file -- not the forge config -- decides what the
assistant uses; it was still pinned to gpt-5.4-mini at low effort while the
forge had moved to gpt-5.6-terra at medium.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>