Skip to content

feat(auth): verify founder sessions through WorkOS AuthKit - #175

Draft
nullStack65 wants to merge 2 commits into
release/native-0.1.10from
feat/clo-1108-workos-authkit-phase2
Draft

nullStack65 wants to merge 2 commits into
release/native-0.1.10from
feat/clo-1108-workos-authkit-phase2

Conversation

@nullStack65

@nullStack65 nullStack65 commented Nov 22, 2026 •

Copy link
Copy Markdown
Owner

Adds opt-in WorkOS AuthKit Google sign-in for T3 Code Web and Desktop. The server verifies the signed code-exchange response and binds the matching enrolled founder to the existing T3 session at issuance. Desktop completes the handoff from the system browser with a single-use proof. Stock mobile pairing and device-key flows retain their wire contracts.

The operator guide lists the exact Dashboard redirects and Infisical bundle, and explains how an external app can use its own WorkOS client. Phase 1 attribution (#173) merges into this branch cleanly in a Git merge simulation.

Verification

  • 74 focused tests passed across server auth, Desktop and Web, including signed JWT rejection, state replay, sender attribution, revocation, and pairing regression.
  • Server, Desktop and Web typechecks, changed-file lint, formatting and staged Gitleaks scan passed. The commit hook's unused-file Knip failures reproduce on the release base. Both commits used a per-command local hook override after the Knip failure was reproduced on the release base. The four affected React Compiler cases passed after the Web fix. Knip reports the same 24 unused exports on the release base. The wider changed-file check also reported a workspace typecheck failure and an agent context budget mismatch.
  • Live WorkOS Google login in Web and Electron, production ingress, and individual external app canaries await the WorkOS Dashboard and environment setup. T3 sessions expire by design at the WorkOS token expiry or 15 minutes, whichever comes first.

Prior art

  • WorkOS hosted AuthKit and jose: adopt the existing authorization-code protocol and JWT verification.
  • T3 SessionStore and Desktop bearer bridge: extend existing infrastructure to keep identity, socket invalidation and pairing in the same session authority.
  • WorkOS Connect: use a distinct OAuth application where an external app needs an OIDC relying party.

Model: gpt-6.2-sol
Task: CLO-1108 Phase 2 implementation
Harness: Codex in T3 Code

Deploy: none

Model: gpt-6.2-sol
Task: implementation
Agent: Codex
Lane: codex
Model: GPT-6 (Codex)
Task: implementation
Agent: Codex
Lane: codex
@nullStack65

Copy link
Copy Markdown
Owner Author

FINDING

Single independent auth review on fd434346ef6727fb40f57fb70f7b6ef33f564805 against release base 18cf8f27f1df245acf78bbbbbea34c1475f4585a. Keep draft for F1 and F2. The reviewer recorded 68 focused passes and reproduced the reported Knip, evals typecheck, and context-budget issues on the base. Prior Phase 1 integration proof is tied to its earlier pin. The full Pairing DOM and live canary remain unverified.

{"reviewed_head":"fd434346ef6727fb40f57fb70f7b6ef33f564805","reviewer":"GPT-6.2 Sol via Codex · Magpie (independent T3 delegate)","findings":[{"id":"F1","severity":"critical","summary":"Require verified application binding before accepting an AuthKit session for founder attribution.","outcome":"open"},{"id":"F2","severity":"important","summary":"Apply the existing managed remote-client policy to AuthKit browser issuance.","outcome":"open"}]}

This branch has not been deployed

No deployments
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