Skip to content

feat(codex): require stable 0.171.0 for smart routing - #1799

Open
masonc08 wants to merge 5 commits into
mainfrom
masonc08/codex-stable-upgrade
Open

masonc08 wants to merge 5 commits into
mainfrom
masonc08/codex-stable-upgrade

Conversation

@masonc08

@masonc08 masonc08 commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

Smart-routed Codex terminal launches require stable 0.171.0 or newer. Known older clients are offered the existing native updater. When routing comes from the workspace's managed default, declining or failing the update, or remaining below the routing minimum, warns and continues the same launch without smart routing. No explicit disable flag is needed. Explicit routing requests retain the required-version gate; UG_AUTO_UPGRADE_AGENT=1 runs updates without confirmation. A known older app-server still warns and runs unrouted because its stdin carries the client protocol.

The stable floor provides native delegation and status-line provider support. Routing CI pins 0.171.0; ordinary Codex launches keep the 0.156.0 minimum. Regression coverage checks the stable boundary, prereleases, slow version probes, successful upgrades, managed fallback, explicit disable, and launch-scoped routing environment restoration. The managed integration journey now requires a warning and completed native child work in the same launch after declining an update.

This is the bottom PR in the stack. The Smart Router indicator PR targets this branch and adds the footer separately. Merge this PR first.

Validation: 944 CLI tests and 733 agent/version/launcher/contract tests passed in separate processes; Ruff lint/format and type checks passed. Seven selected installation checks passed against the built wheel. Six live Linux/npm Arclet scenarios against the requested Databricks workspace completed hidden-file tasks: declined updates on Codex 0.164.0 and 0.170.0, manual update failure, automatic update failure, EOF input followed by update failure, and accepted upgrade to 0.171.0. The first five continued without routing and preserved the installed version; successful upgrade started the routing layer. Five cases used the real TUI; EOF used native exec with closed stdin. Admin policy input used the checked-in managed-config fixture; binaries, npm updates, and inference were real. Backend route selection is outside these upgrade checks.

@masonc08

Copy link
Copy Markdown
Collaborator Author

/ug-review


This comment was generated with GitHub MCP.

Comment thread src/ucode/cli.py
Comment on lines +4463 to +4467
ensure_minimum_version(
"codex",
lambda: codex_agent.minimum_version_error(smart_routing_enabled=True),
)
routing_unavailable = None

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bug · high
can we fall back to the old warning here? A managed config with an old Codex now blocks launch when the user declines, the update fails, or piped/EOF input takes the default, and the user can't change the admin's setting. Suggest catching RuntimeError and running without smart routing.

Suggestion:

Suggested change
ensure_minimum_version(
"codex",
lambda: codex_agent.minimum_version_error(smart_routing_enabled=True),
)
routing_unavailable = None
try:
ensure_minimum_version(
"codex",
lambda: codex_agent.minimum_version_error(
smart_routing_enabled=True
),
)
routing_unavailable = None
except RuntimeError as exc:
routing_unavailable = str(exc)

version_match = re.search(r"\b(\d+)\.(\d+)\.(\d+)\b", version_output)
assert version_match is not None, version_output
routing_supported = tuple(int(part) for part in version_match.groups()) >= (0, 164, 0)
routing_supported = tuple(int(part) for part in version_match.groups()) >= (0, 171, 0)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test · low
what happens with inputs.codex_version=0.171.0-alpha.1? _smart_routing_version_supported rejects that prerelease, but this check treats it as supported, so the test takes the wrong branch. can we use the same rule (or call that helper)? same issue in test_ug_codex_app_server.py

Comment on lines +1038 to +1041
gate.send("n\r", "decline the required upgrade")
gate.wait_for(lambda _: gate.ended, "blocked launch to exit")
gate.child.close()
assert gate.child.exitstatus != 0

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other · high
will this break current ug users? managed-routing users on Codex 0.164–0.170 who decline the upgrade used to get a warning and launch unrouted. Now they're blocked until they pass --disable-smart-routing. can we keep the warn-and-continue fallback?

@github-actions

github-actions Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

UG review recommendation

RECOMMENDATION: REJECT (request changes)

Reasons:

  • Finding 1 (cli.py 4460-4463) describes a reproducible regression in an existing workflow. Old-Codex managed launches used to warn and run unrouted. Now they prompt on every launch. Piped or EOF runs default to "yes", so codex update (up to 300s) runs on every invocation, even when Codex stays belo
  • Finding 3 (cli.py 4465-4466) is minor: the version warning prints twice. It should be cleaned up but is not blocking on its own.
  • Finding 4 (cli.py 4464) is minor: continued_with_fallback=False misreports the metric when a failed update falls back to an unrouted launch. This is a telemetry accuracy follow-up.
  • Findings 2 and 5 (integration tests) point to test gaps. The tests' version checks ignore the prerelease handling ug now uses. On prerelease runners, one test skips the unrouted path and the other expects routing that ug refuses. The tests should share codex.MINIMUM_SMART_ROUTING_CODEX_VERSION or

Findings considered: 5 (severities: low: 4, medium: 1); see the inline review comments.

Advisory only: this recommendation never approves or merges the pull request. The ready-to-approve label tracks it.

@github-actions

Copy link
Copy Markdown
Contributor

Polly AI Review

Blocking issues

  • src/ucode/cli.py:4463 — can we gate upgrades by launch shape? managed old app-server consumes JSON-RPC stdin; exec can update or fail despite never routing.

    The new managed check runs before the launcher's app-server fallback. Its confirmation reads stdin and treats EOF as approval, breaking the promised unrouted protocol path.

    can we extend tests/test_cli.py::TestSubcommandRouting::test_codex_routing_version_requires_upgrade_or_explicit_disable with managed app-server and exec cases?

Security vulnerabilities

None found in the frozen diff. Workflow changes retain the existing triggers and credential boundaries.

Non-blocking notes

  • tests/integration/test_ug_smart_routing_hooks.py:1013, tests/integration/test_ug_codex_app_server.py:64 — can both cases preserve prerelease suffixes? 0.171.0-alpha.N wrongly selects supported behavior, causing failure or an early return.
  • src/ucode/agents/codex.py:197 — is accepting 0.172.0-alpha.1 intentional? the description requires stable clients, but the helper and version test explicitly accept this prerelease.
  • tests/README.md:1512 — can we include CUJ7 in the 0.171.0 pin description? .github/workflows/integration.yml:1005 upgrades it too.

Approach

Reuse the existing shape-aware gate in codex.launch for managed launches instead of duplicating enforcement in cli.py. The native updater and post-update validation already provide the required recovery flow.

Summary

Diff size (computed): 13 files; +134 / -74 lines (208 changed text lines); 0 binary files.

Category Files Added Deleted Share of changed text lines
Tests and test support 8 96 51 70.7%
Documentation 2 13 14 13.0%
Dependencies and lockfiles 0 0 0 0.0%
Implementation / other 3 25 9 16.3%

Shares use additions + deletions, including generated text and lockfiles. Binary files have no line count. Tests include fixtures/helpers under test paths and colocated test/spec files; categories are path-based, not coverage measurements.

Changes

Raises the routed Codex floor, adds prerelease-aware checking, requires upgrades for managed launches, and updates CI pins and documentation. Ordinary launches retain their separate minimum.

The size is proportional to the outcome. Removing the duplicate managed enforcement would simplify implementation and prevent the protocol regression. No dependency, lockfile, generated-asset, or unrelated footer changes appear.

Tests

Test-by-test assessment

Static assessment only: the snapshot checksum matched, and both required policy files were read. Tests were not executed. Reported test totals, lint/type results, and live native validation remain unverified. No actual gateway usage-data evidence was inspected.

Test / case Behavior protected Layer Needed? Action / rationale
tests/test_agent_codex.py::TestMinimumVersion::test_supported_version — below-floor cases Ordinary minimum remains valid while older clients cannot route Unit keep Retains ordinary-floor and routed-boundary regression coverage.
tests/test_agent_codex.py::TestMinimumVersion::test_supported_version — minimum alpha/RC cases Prereleases at 0.171.0 are rejected Unit keep Directly exercises suffix handling at the release boundary.
tests/test_agent_codex.py::TestMinimumVersion::test_supported_version — stable, build metadata, major-version cases Supported releases and build metadata compare correctly Unit keep Smallest reliable layer for version boundaries.
tests/test_agent_codex.py::TestMinimumVersion::test_supported_version — 0.172.0-alpha.1 A newer prerelease is accepted Unit uncertain Resolve the stable-only wording noted above, then align this expectation.
tests/test_agent_codex.py::TestMinimumVersion::test_smart_routing_rechecks_an_unknown_version_with_a_longer_bound — all parameters Slow probes recover; old and unknown results remain bounded and cached Component keep Exercises probe timing and repeated checks without a native process journey.
tests/test_cli.py::TestSubcommandRouting::test_managed_smart_routing_overrides_env_vars_but_not_the_flag_or_a_version Managed routing respects explicit controls CLI component keep Supported-version stub changes preserve existing precedence coverage.
tests/test_cli.py::TestSubcommandRouting::test_codex_routing_version_requires_upgrade_or_explicit_disable — explicit decline, upgrade, disable cases Decline blocks, upgrade enables routing, disable bypasses upgrading CLI component keep Covers externally observable orchestration and environment restoration.
tests/test_cli.py::TestSubcommandRouting::test_codex_routing_version_requires_upgrade_or_explicit_disable — managed cases Managed refusal blocks and successful upgrade routes CLI component keep Covers changed enforcement; add managed app-server/exec parameters for the blocker.
tests/test_cli.py::TestSubcommandRouting::test_codex_routing_version_requires_upgrade_or_explicit_disable — prerelease parameters CLI dispatch applies the prerelease restriction CLI component keep Checks integration with launch decisions, beyond isolated comparison logic.
tests/test_cli.py::TestSubcommandRouting::test_warns_once_and_launches_unrouted_when_version_leaves_codex_unrouted Unrouted selections warn once and launch normally CLI component keep Updated version stub isolates the existing selection contract.
tests/test_codex_smart_routing_v2.py::TestLaunchCodex::test_codex_smart_routing_launch_dispatches_to_v2 — supported, prompted/automatic upgrade, decline, failure, still-old cases; both argument shapes Native updater recovery and blocking failure paths Launcher component keep Distinct updater outcomes are not all covered by the CLI test.
tests/test_codex_smart_routing_v2.py::TestLaunchCodex::test_codex_smart_routing_launch_dispatches_to_v2 — unknown-version cases Inconclusive probes cannot silently permit routing Launcher component keep Preserves unknown-version and post-upgrade validation behavior.
tests/test_codex_smart_routing_v2.py::TestLaunchCodex::test_app_server_routes_only_from_codex_routing_floor — both versions Old app-server launches warn and run unrouted without upgrading Launcher component keep Protects the direct launcher boundary, but bypasses the faulty managed CLI gate.
tests/test_codex_smart_routing_v2.py::TestLaunchCodex::test_codex_launch_normalizes_cached_bootstrap_model Cached startup models normalize correctly Component keep Only the prerequisite supported version changes.
tests/test_codex_smart_routing_v2.py::TestLaunchCodex::test_startup_config_precedence — all parameters Startup configuration precedence remains intact Component/filesystem keep Existing distinct configuration cases remain relevant; version stub changes only.
tests/test_codex_smart_routing_v2.py::TestCustomCatalogModels::test_start_model_comes_from_custom_catalog Custom catalog determines the startup model Component keep Preserves separate catalog-selection coverage.
tests/test_integration_contract.py::test_live_ci_lanes_together_cover_every_blocking_live_case — both agents Required live cases remain assigned to CI lanes with the routing pin Workflow contract keep Checks lane selection as well as the updated version.
tests/test_integration_contract.py::test_dedicated_cuj_ci_runs_each_discovered_file_on_its_own_runner Dedicated CUJ runners retain their execution shape and pins Workflow contract keep Covers different jobs from the full/managed matrix check.
tests/integration/test_ug_codex_app_server.py::test_ug_codex_app_server_runs_unrouted_below_routing_floor Real JSON-RPC initialization succeeds without upgrade prompting Process/protocol integration keep A real handshake uniquely checks stdio integrity; fix prerelease classification.
tests/integration/test_ug_smart_routing_hooks.py::test_smart_router_managed_default_matches_codex_version_at_launch Refusal exits unsuccessfully; disabled retry completes native work Native PTY/live integration keep Replaces warning-only expectations with exit/outcome assertions; fix prerelease classification.
tests/integration/test_ug_smart_routing_hooks.py — added TerminalProcess use Drives the real confirmation and observes termination Integration setup keep Reuses the existing PTY primitive rather than adding another harness.
tests/README.md — changed coverage and pin descriptions Documents component/live boundaries and routing prerequisites Documentation keep Correct the CUJ7 statement identified above; prose is not execution evidence.
tests/integration/README.md — changed compatibility, journey, command, and lane descriptions Documents installed-client validation and CI selection Documentation keep Supports reproduction and correctly includes both upgraded CUJs.

No test functions were removed or renamed, and no fixture definitions changed. Existing launcher tests cover updater failures and direct app-server fallback; they do not cover the managed CLI regression. A CLI component test is the smallest suitable addition.

For manual verification, use Codex 0.170.0 with managed routing enabled and connect a stdio client through ug codex app-server --listen stdio://. Initialization must succeed unrouted, warn only on stderr, and never prompt or update.

Scope

All changes support the stated routing-version outcome; no unrelated work was found. The managed launch-shape regression is a correctness issue within that scope. Acceptance of newer prereleases remains an unresolved contract question, not evidence of unrelated scope.


Automated review by Polly · workflow run

@masonc08

Copy link
Copy Markdown
Collaborator Author

/ug-review

Comment thread src/ucode/cli.py
"codex",
lambda: codex_agent.minimum_version_error(smart_routing_enabled=True),
)
routing_unavailable = None

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other · low
ensure_minimum_version passes continued_with_fallback=False to _update_installed_tool_binary. On this path a failed update still launches unrouted, so the metric reports the wrong outcome. Can we let the caller pass this flag through?

Comment thread src/ucode/cli.py
Comment on lines 4465 to 4466
except RuntimeError as exc:
routing_unavailable = str(exc)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other · low
ensure_minimum_version already calls print_warning(version_error), and line 4468 prints the same text again with "Running without smart routing.", so the user sees it twice. Can we drop one of them?

)
assert version, "`codex --version` reported no semver"
if tuple(map(int, version.groups())) >= (0, 164, 0):
if tuple(map(int, version.groups())) >= (0, 171, 0):

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test · low
this check ignores prerelease tags, but ug now treats 0.171.0-alpha.N as below the floor. on a prerelease runner the test returns early and never checks the unrouted path. can we use the same prerelease-aware check, or codex.MINIMUM_SMART_ROUTING_CODEX_VERSION?

@github-actions

Copy link
Copy Markdown
Contributor

Polly AI Review

Blocking issues

  • src/ucode/cli.py:4460 — can we skip the managed upgrade prompt for app-server? On 0.170.0 it consumes JSON-RPC stdin before the fallback, hanging initialization.

Security vulnerabilities

None found in the reviewed changes.

Non-blocking notes

  • tests/integration/test_ug_smart_routing_hooks.py:1015 — can we classify 0.171.0 prereleases as unsupported so this journey answers the upgrade prompt instead of waiting for native boot?
  • tests/test_cli.py:1203 — can we run updater faults once in test_codex_routing_upgrade_preserves_managed_fallback, leaving the version matrix to TestMinimumVersion.test_supported_version?
  • tests/README.md:1516 — can we update “other CUJs retain 0.156.0” to acknowledge that CUJ7 now also pins 0.171.0?

Approach

Reusing the native updater avoids another installation path. Apply the existing launch-shape eligibility check before invoking it: app-server must preserve protocol stdin, and non-routing commands should not request routing-only upgrades.

Summary

Diff size (computed): 13 files; +178 / -88 lines (266 changed text lines); 0 binary files.

Category Files Added Deleted Share of changed text lines
Tests and test support 8 131 57 70.7%
Documentation 2 23 22 16.9%
Dependencies and lockfiles 0 0 0 0.0%
Implementation / other 3 24 9 12.4%

Shares use additions + deletions, including generated text and lockfiles. Binary files have no line count. Tests include fixtures/helpers under test paths and colocated test/spec files; categories are path-based, not coverage measurements.

Changes

The PR raises the Codex smart-routing floor to stable 0.171.0 while retaining 0.156.0 for ordinary launches. It adds minimum-version prerelease handling and managed-default upgrade recovery, then aligns CI pins and documentation.

The implementation is proportional and reuses existing update and fallback mechanisms. Tests supply most of the changes; the concrete reduction opportunity is the repeated recovery matrix identified above. No dependency, lockfile, or generated-asset changes are included.

Tests

Test-by-test assessment

The frozen snapshot’s checksum matches the supplied value, and both trusted policy files were read in full.

No target pytest suite ran: local pytest and typer were unavailable. An isolated offline probe using the prompt/updater functions confirmed that protocol input is consumed and EOF attempts an update. This establishes the prompt failure, not a complete native app-server run. The PR-reported suite results and live Linux validation remain unverified.

Test / case Behavior protected Layer Needed? Action / rationale
tests/README.md — changed routing-version, recovery, coverage, and CI documentation Documents compatibility floors and verification boundaries Documentation keep Retains useful coverage guidance without adding executable setup. Correct the CUJ7 pin description noted above. Documentation is not execution evidence.
tests/integration/README.md — changed version, terminal fallback, app-server, and reproduction guidance Explains installed-client journeys and protocol constraints Documentation keep Relevant to reproducing the changed launch behavior. The no-prompt app-server statement describes the required contract; the new managed path currently violates it.
tests/integration/test_ug_codex_app_server.py — test_ug_codex_app_server_runs_unrouted_below_routing_floor Real stdio initialization, stderr warning, no prompt, and unrouted operation below the floor Installed-process / protocol keep Extends an existing transport-boundary test rather than adding another journey. Its explicit routing environment misses managed-default activation. Extend the existing scenario with managed configuration; also avoid silently excluding minimum-version prereleases through numeric-only classification. Initialization establishes protocol operation, not inference.
tests/integration/test_ug_smart_routing_hooks.py — test_smart_router_managed_default_matches_codex_version_at_launch Declining an upgrade continues the same terminal launch unrouted, preserves the installed version, and completes parent/child work Installed CLI / native TUI keep Reuses _run_calculation and requires completed work, not just boot. Replacing the former terminal no-prompt assertion follows the new contract. Fix prerelease classification as noted above. The separate supported-version routing journey remains useful because this baseline journey may exercise only the older-client branch.
tests/test_agent_codex.py — TestMinimumVersion.test_supported_version; ordinary versions, below-floor versions, 0.171.0-alpha.12, 0.171.0-rc.1, stable/build metadata, later versions Separates ordinary compatibility from routing eligibility and checks the stable boundary Unit keep The lowest reliable layer for this input matrix. Changed expectations intentionally remove routing support from previously accepted older versions while preserving ordinary compatibility. Later-version prereleases exercise a version floor, not a blanket prerelease ban.
tests/test_agent_codex.py — TestMinimumVersion.test_smart_routing_rechecks_an_unknown_version_with_a_longer_bound; supported, old, unreadable, and repeated-timeout results Bounded retry and cached version-probe recovery Component keep Distinct from version comparison: preserves timeout/retry assertions while updating supported and unsupported representatives. Mocked subprocess results do not establish native installation behavior.
tests/test_cli.py — TestSubcommandRouting.test_managed_smart_routing_overrides_env_vars_but_not_the_flag_or_a_version; both agents and existing flag/version combinations Managed precedence, explicit overrides, agent eligibility, and scoped environment CLI component keep Only the supported Codex fixture changes. These policy combinations protect behavior distinct from parsing or updater recovery; mocked launch assertions establish options/environment, not inference.
tests/test_cli.py — TestSubcommandRouting.test_codex_routing_upgrade_preserves_managed_fallback; four unsupported versions × decline, upgrade, disable, managed default, managed upgrade, update failure, still-old, EOF, and automatic failure Explicit gating, managed recovery, confirmation behavior, unrouted launch, and environment restoration CLI component consolidate Replaces test_codex_routing_version_requires_upgrade_or_explicit_disable; no separate scenario is lost. Preserve every recovery outcome, but run updater faults on a representative unsupported version. Boundary classification already belongs to TestMinimumVersion.test_supported_version; explicit updater outcomes also appear in the agent-launch test below. Extend this existing CLI scenario to managed app-server and non-routing shapes to catch the blocker.
tests/test_cli.py — TestSubcommandRouting.test_warns_once_and_launches_unrouted_when_version_leaves_codex_unrouted; existing agent, preset, flag, disable, and native-subcommand cases Warning behavior, ineligible presets, explicit disable, and command-shape policy CLI component keep Only the supported-version fixture changes. The native-subcommand case does not combine managed routing with an older client, so it does not cover the new early updater call.
tests/test_codex_smart_routing_v2.py — TestLaunchCodex.test_codex_smart_routing_launch_dispatches_to_v2; supported, upgraded, auto-upgraded, declined, failed, still-old, and unknown-version states × empty/positional arguments Explicit routing’s required-version gate and supported dispatch Agent-launch component keep Updates version representatives without weakening failure assertions. Unsupported execution remains forbidden; unknown versions avoid prompting/updating. Both argument shapes remain relevant. This is mocked update/dispatch coverage, not a native update.
tests/test_codex_smart_routing_v2.py — TestLaunchCodex.test_app_server_routes_only_from_codex_routing_floor; 0.170.0/0.171.0 Adapter-level old app-server fallback versus supported routing, without prompting/updating Agent-launch component keep Protects the adapter’s existing safeguard, but directly invokes codex.launch and misses the earlier CLI prompt. Add coverage at the CLI boundary rather than expanding this lower-layer matrix.
tests/test_codex_smart_routing_v2.py — TestLaunchCodex.test_codex_launch_normalizes_cached_bootstrap_model Cached bootstrap model normalization Agent-launch component keep Supported-version fixture adjustment prevents the new gate from obscuring the existing regression assertion. No new setup or unrelated behavior is introduced.
tests/test_codex_smart_routing_v2.py — TestLaunchCodex.test_startup_config_precedence; both home modes and existing managed/profile/user/malformed/absent combinations Model precedence, optional-config recovery, and saved-file preservation Component / temporary files keep Only the supported-version fixture changes. Existing combinations remain appropriate at this layer; they do not prove native configuration consumption.
tests/test_codex_smart_routing_v2.py — TestCustomCatalogModels.test_start_model_comes_from_custom_catalog Custom catalog precedence over cached models Agent-launch component keep Supported-version fixture adjustment preserves the existing catalog-selection assertion. Distinct from cached-model normalization; no API response is asserted.
tests/test_integration_contract.py — test_live_ci_lanes_together_cover_every_blocking_live_case; Claude/Codex parameters Baseline/routing pin separation and combined lane coverage Workflow contract / collection keep Updates routing-pin expectations while retaining the ordinary baseline and lane-selection checks. Collection coverage does not establish successful live execution.
tests/test_integration_contract.py — test_dedicated_cuj_ci_runs_each_discovered_file_on_its_own_runner Dedicated CUJ runner structure and CUJ4/CUJ7 pins Workflow contract keep Updates the existing contract rather than adding a duplicate test. Checks a different job from the preceding row; string assertions do not prove package availability or native behavior.

The smallest missing regression is a CLI component case combining managed-default routing, an old Codex, and app-server arguments. Existing adapter-only coverage cannot detect the earlier prompt. The installed protocol journey can reuse its current setup to verify the complete boundary.

tests/_helpers/README.md was absent from the trusted checkout; existing fixtures and integration primitives supplied the available context. No paired HTTP request/response evidence or downstream usage attribution was verified.

To confirm the fix manually with Codex 0.170.0, managed routing enabled, and UG_AUTO_UPGRADE_AGENT unset:

  • Connect a stdio client to ug codex app-server --listen stdio:// and send initialize. Expect a valid response, an unrouted warning on stderr, no confirmation, and no update.
  • Run ug codex exec ... and ug codex app-server generate-ts --out ...; neither should request a routing-only upgrade.
  • Launch the ordinary terminal, decline the upgrade, and confirm the same launch completes work unrouted without changing the installed version.

Scope

All changed files support the stated version-floor and managed-recovery outcome; no clearly unrelated changes were found. The app-server failure is an implementation regression within that scope, not a separate feature request.


Automated review by Polly · workflow run

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants