Skip to content

Rebuild the Mac's OmniRoute gateway with GPT-6.1 Sol and follow the installed Codex version - #599

Merged
seathatflowsinourveins merged 2 commits into
mainfrom
claude/omniroute-mac-rebuild-20261002
Oct 2, 2026
Merged

seathatflowsinourveins merged 2 commits into
mainfrom
claude/omniroute-mac-rebuild-20261002

Conversation

@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator

Scope

  • What this PR changes, in one or two sentences: records the rebuild of the Mac coordinator's OmniRoute gateway on upstream release/v3.8.52 with upstream PRs 13788 and 15167 (GPT-6.1 Sol at max now answers through the gateway), the launch agent's wrapper that announces the installed Codex version at every start, and the daily update check; documentation and evidence only, no repository code changes.
  • Base commit: f0cb8041e2
  • Lane: lane:foundation (docs/ and evidence/artifacts/; manifests/evidence.json only by registration, in the last commit).
  • Owned paths touched: docs/decisions/2026-10-02-omniroute-mac-rebuild.md (new), evidence/artifacts/omniroute-mac-rebuild-20261002/ (new), manifests/evidence.json (registration only).
  • grants: none

SOTA sources

Evidence-class table

Claim Evidence class Command / receipt
The package was built from the named base plus the two PRs and passed upstream's artifact policy as a recorded canary build upstream_unchanged scripts plus local_integration build-manifest.json (tarball sha256 d602dc42…, BUILD_SHA 6f246e84a); scripts/build*.sh.txt
After the switch, GPT-6.1 Sol and GPT-6 Astra at max answer 200 and codex exec through the gateway works local_integration (probe gate) checks/probe-after.json, checks/switch-2.log
The first switch rolled back on its own after 401s from the migrated key table local_integration checks/switch-1.log, receipt.json
The gateway announces the installed Codex version (0.160.0 at start) local_integration receipt.json codex_follow
Upstream effort on the wire for GPT-6.1 Sol not read back here limit in receipt.json

Local commands run

$ the build: npm ci; npm run build:release; OMNIROUTE_ALLOW_CANARY_BUILD=1 npm run check:pack-artifact; npm pack
check:pack-artifact passed (canary recorded); tarball sha256 d602dc42c7357e032b1e2323ba6660e0e1400bb5e997cb1c3857882654f9dbe4
$ python3 switch_gateway.py <tarball> <manifest> <work>   # attempt 2
smoke healthy; switch bootstrap 0; health 200; probe attempt 1 passed; update-check agent bootstrapped
$ /usr/bin/python3 omniroute-update-check.py   # first run
codex_follow unchanged (0.160.0); latest release v3.8.51; PRs 13788 and 15167 unmerged
$ the locally runnable validate.yml steps (validate.py, evidence_manifest --check, zizmor offline, the generators' checks, the verdict gate)
all exit 0 (the final-catalog step needs #595)

Decision record

docs/decisions/2026-10-02-omniroute-mac-rebuild.md (alternatives: a version bump on the old build, waiting for an official v3.8.52, nightly automatic rebuilds; overturn: an official release carrying both PRs).

Host evidence

Not applicable: no file under evidence/hosts/.

Checklist

  • New/changed GitHub Actions are pinned to a full commit SHA with a version comment (no floating tags). None changed.
  • New/changed workflows declare top-level permissions: contents: read (or a narrower, explicitly justified addition). None changed.
  • No secrets are printed, logged or committed; no new required secret was added without a documented owner. The launch agent's key is the documented non-secret loopback placeholder.
  • No new paid hosting, subscription or billing surface was introduced.
  • Peer-owned untracked files and worktrees were preserved (not deleted, moved or overwritten).

🤖 Generated with Claude Code

seathatflowsinourveins and others added 2 commits October 1, 2026 23:54
…nstalled Codex version

The Mac gateway announced a fixed Codex 0.158.0-alpha client version on its live catalog query, so the backend never
offered GPT-6.1 Sol. It now runs upstream release/v3.8.52 (528235175) with upstream PRs 13788 (Codex web.run search)
and 15167 (GPT-6.1 Sol, max on the wire), built with upstream's build:release and artifact-policy check (a recorded
canary build). The launch agent starts it through a wrapper that announces the installed Codex version at every start,
passes the documented loopback placeholder as the configured key, and a daily launchd check restarts the gateway after
a Codex update and notifies when an official release carries both PRs. The probe gate passed: GPT-6.1 Sol and GPT-6
Astra at max answer 200 and codex exec through the gateway works. The first switch rolled back on its own (401 on the
migrated key table); the record keeps both attempts. Web search through the gateway falls back to DuckDuckGo, which is
unreachable from this host; recorded as a limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hot-file protocol (docs/lanes.md): the registration of this branch's new files, last commit only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Oct 2, 2026
@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.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

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