Improve signup-to-first-session conversion - #157
Open
ohong wants to merge 4 commits into
Open
Conversation
Keep validated local return paths through OAuth, magic links, auth retries, and login/signup navigation. New accounts can return to explicit CLI approval before optional profile setup. Co-authored-by: Codex <noreply@openai.com>
Move optional profile editing to Settings. Add manual-copy fallback and bounded, non-overlapping usage checks with retry and sign-in recovery. Complete setup only after confirmed usage and a successful save, and show accurate usage totals. Co-authored-by: Codex <noreply@openai.com>
Document observable first-sync success conditions, retain ccusage, and carry forward source-attribution and model-presentation questions from the superseded provider review. Co-authored-by: Codex <noreply@openai.com>
Cover immediate access and skipping, real usage confirmation and completion, and retry after a failed save. Use isolated loopback-only test accounts and capture desktop/mobile evidence without storing sessions in the repository. Co-authored-by: Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reachedNext included review available in 37 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (14)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 5, 2026
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
1 participant
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.
New users must pass two onboarding screens before seeing the sync command. CLI users who need to sign in also lose their authorization return URL when login starts OAuth or sends a magic link. Both obstacles interrupt signup-to-first-sync conversion (#19).
Success means the command is visible immediately, interrupted checks offer recovery, and sign-in returns CLI users to explicit authorization. Copying the command or exploring the feed must not complete onboarding.
The change puts the command and live status on the first onboarding screen, moves optional profile editing to Settings, and adds manual copying plus status/completion retries. It preserves validated local return paths through login, signup, and callbacks. The success view uses actual spend, tokens, model, and date, without treating daily usage counts as individual coding sessions. We chose this smaller web change over a separate CLI-first signup funnel; existing three-day backfill and the collector remain in place.
Validation:
bun run test: 776 web tests and 205 CLI tests passed, including 48 new onboarding/auth regression tests.bun run typecheck,bun run lint, andbun run build: passed.PLAYWRIGHT_USE_DEV_SERVER=1, line reporter, temporary local config selecting installed Chromium 1234). Real local auth, usage reads, completion writes, skip behavior, and retry after a controlled failure were verified; desktop/mobile screenshots were inspected.autoreview --mode local --engine codex: clean, no actionable findings. Rebased onto current main (7ee21a7); only a documentation conflict required resolution, and full checks were rerun.git diff --check: passed.Issue triage also records the decision to retain ccusage and preserves the remaining model-presentation/source-attribution ideas from #28 in the roadmap. #99's collector replacement is not planned, and #144's nightly report tracker is obsolete. Thank you to @alexesprit, @rube-de, @darthShadow, @jqueguiner, and everyone who contributed ideas and feedback.
This PR has not been merged or released to production, and it does not establish a conversion lift. Production OAuth/magic-link delivery has not been exercised; it still depends on the project's configured callback URL allowlist. Compare the existing signup, first-sync-confirmed, and activation-completed events after release. Local browser verification uses a local test account and controlled failure responses.
Authored with Codex, with implementation delegated to coding agents and verification/review coordinated by the main agent.