Skip to content

feat(setup): expose T3 Connect activity and webhook settings - #56

Open
0libote wants to merge 12 commits into
dizys:mainfrom
0libote:feat/connect-activity-settings
Open

0libote wants to merge 12 commits into
dizys:mainfrom
0libote:feat/connect-activity-settings

Conversation

@0libote

@0libote 0libote commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

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:

  • All 913 Node tests passed.
  • The Access audit passed all 10 light/dark phone, tablet, desktop and embedded configurations, including both setup modes through sign-in and restart, revoked-link recovery, independent switches, duplicate submissions, failed saves, retries and stale polling.
  • HTTP regressions cover authenticated and same-site access, confirmed saves surviving failed and older refreshes, native revocation overriding stale CLI state, mode validation and actual CLI arguments. A TTY check verifies notification-only arguments reach the login helper.
  • A disposable native T3 server verified activity preference persistence, linked-account gating and preservation of webhook holding. The preference was restored and test sessions revoked afterward.
  • All four shell behavior suites, the 29-check harness audit, generated mise checks, JavaScript/shell syntax, ShellCheck and git diff --check passed.

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.

Setup choice Light Dark
Phone Phone light Phone dark
Desktop Desktop light Desktop dark

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant