fix: Codex auth new endpoint + wave7 chain pages - #1810
Merged
Conversation
www.defined.fi/api (createApiTokens GraphQL mutation) is dead as of 2026-08. New endpoint is /api/codex/token which returns JWE directly. Still blocked by Vercel TLS checkpoint for Go HTTP — use CODEX_JWT env var or DEFINED_TOKEN_SERVICE_URL sidecar (Paris box) for automatic refresh. scrape-cookie: add awaitPromise fix, diagnostic headers, in-browser fetch test.
# Conflicts: # harnesses/aggregator-head-lag/cmd/scrape-cookie/main.go # harnesses/aggregator-head-lag/cmd/script/defined_auth.go
… api 24h window correct
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
createApiTokensatwww.defined.fi/apiis dead. New endpoint is/api/codex/tokenreturning JWE directly (blocked by Vercel TLS for Go, handled via Paris box sidecar + CODEX_JWT env)defined_auth.goto point at new endpoint with correct response parsingscrape-cookieutility withawaitPromisefix and diagnostic browser fetchTest plan
http://57.130.19.92:8080/tokenreturns valid JWE (curl test:curl -s http://57.130.19.92:8080/token | wc -cshould be ~693)