fix(web): name the step that registers a mobile client

[Sethmr]

Problem

The Mobile clients empty state reads:

Sign in to T3 Code on your iPhone to register it for push notifications and Live Activities.

That is satisfiable in a way that does nothing. Signing in to the mobile app and pairing it to an environment — over a LAN address or a Tailscale link — is a reasonable reading of "sign in to T3 Code on your iPhone", and it leaves this page empty.

Registration needs a T3 Connect token. Without one, remoteRegistration.ts:369 skips it and logs relay device registration skipped; user is not signed in. So a user who has done everything the sentence asks lands on an empty page with nothing to act on and no way to tell which part is missing.

I hit this myself: phone paired over Tailscale, fully working — I could start a session on my desktop from it — and this page still said "No mobile clients" and told me to do the thing I had already done.

Fix

Copy only. Name the sign-in that registers a device, and rule out the one that doesn't:

Install T3 Code on your phone and sign in to T3 Connect with this account to register it for push notifications and Live Activities. Pairing a phone directly to an environment over your LAN or Tailscale does not register it here.

The second sentence mirrors the guarantee already documented in docs/user/mobile-notifications.md:

Background delivery requires T3 Connect; a direct or Tailscale connection alone does not enable push notifications.

No logic, props, or layout change — EmptyMobileClients has no conditional branches, so the rendered result differs only in this string.

On the before/after images

CONTRIBUTING.md asks for before/after images. I have the before (attached below) but could not capture the after in a dev build, and would rather say so than pad the PR with a misleading substitute.

The panel is a Clerk UserButton.UserProfilePage, so it only renders for a signed-in Clerk session. The web dev server cannot get one: the production Clerk instance rejects a localhost origin outright.

Origin: http://localhost:5733  -> HTTP 400  {"code":"origin_invalid"}
Origin: https://app.t3.codes   -> HTTP 200

isLoaded therefore stays false and the sign-in never mounts. pnpm dev:desktop should route around this through @clerk/electron, and the shell does load — @clerk/electron/react resolves and Vite pre-bundles it — but sign-in still did not come up in a dev desktop build, which looked unrelated to this change and not worth chasing further.

Happy to add the after image if a maintainer can produce it, or to drop this if the copy is not wanted.

Verification

• vp lint clean on the changed file.
• tsc --noEmit clean in apps/web.

Written by Claude Opus 5 in Claude Code.

Summary by CodeRabbit

• Documentation
  • Updated the empty mobile clients message to explain that users can install T3 Code on their phone and sign in to T3 Connect with the account they want associated with the phone.
  • Clarified that signing in registers the phone for push notifications and Live Activities, regardless of which connection the phone uses to access environments.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: fd408b69-cbcf-4db0-9d4b-9fb6a8f066b3

📥 Commits

Reviewing files that changed from the base of the PR and between 19fb8311b2b6af3c737c6173a4e5c734a5ebd064 and 7ff4c22.

📒 Files selected for processing (1)

• apps/web/src/components/clerk/MobileClientsUserProfilePage.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/web/src/components/clerk/MobileClientsUserProfilePage.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

The mobile clients empty state now instructs users to install T3 Code and sign in to T3 Connect. Registration follows that sign-in regardless of the connection used to reach environments.

Changes

Mobile client guidance

Layer / File(s)	Summary
Registration message update apps/web/src/components/clerk/MobileClientsUserProfilePage.tsx	The empty-state message now describes registration through T3 Code and T3 Connect for all environment connection types.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 7ff4c

No merge-blocking issue is identified in the mobile client guidance update.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the copy change that names the sign-in step used to register a mobile client.
Description check	✅ Passed	The description clearly explains the problem, the copy-only fix, the registration requirements, verification results, and the limitation with after screenshots. It does not use the template headings e…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved at a466585

Macroscope's review found this PR approvable — This is a contained, copy-only clarification in the existing mobile-clients empty state. It changes no registration logic, data flow, layout behavior, product defaults, or static-analysis configuration.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.