Repository navigation
Conversation
Codex 0.164.0 changed login status for API keys from Logged in to API key configured. The old probe returned unknown, breaking the saved-key and sign-in-completion smoke checks in PR dizys#56. Accept the configured-key status only on successful probes, retain legacy output support, and cover both formats plus signed-out and error states. Document that configured keys are validated when Codex sends a request.
Resolve the Codex auth probe conflict by keeping main's equivalent compatibility fix and its broader failed-probe regression coverage. Drop the redundant PR-local test while preserving connection preferences and the documented Codex 0.164.0 compatibility note. Validation: all 822 Node tests pass, including the sign-in and connection preferences tests; JavaScript and shell syntax checks and git diff --check pass. Docker image smoke checks remain for CI.
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
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.
Access now exposes Publish agent activity and Hold webhooks while offline, using T3 Code's native API. Preference changes take effect without restarting agents and preserve the other setting.
T3 Connect setup offers T3 Connect tunnel or Notifications only before sign-in. Notifications only links the server for mobile notifications and Live Activities while devices keep using their own server address. The same mode is available through
t3-login connect link --publish-only; the helper forwards Connect commands and options while retaining its privilege handling.Offline webhook holding requires a managed tunnel and a supported server version. The UI explains that T3 Connect stores requests outside this server for up to 24 hours and still delivers already-held requests after the setting is disabled.
Removed account links show Set up again and cannot change preferences until relinked. Older servers that omit the optional tunnel flag retain their managed-link behavior. Successful saves update the status cache and use the native save response, so a failed refresh or older in-flight read cannot undo the confirmed result. Overlapping saves are blocked; unavailable settings and errors remain visible.
Validation:
git diff --checkpassed.Docker is unavailable locally; the updated head's four image build/smoke jobs must pass before merge. Phone push delivery and relay-side offline storage/replay were not tested.
Screenshots use synthetic fixture data.