[extoci]

Problem

Connection setup mixes host, backend, client, and publishing terminology. The instructions make users work out what they are connecting and who gets access.

Change

Use the approved host, pairing, permission, and T3 Connect wording in onboarding and Connections settings. Update the matching mobile pairing and permission text, plus the agent-activity setting and its accessibility label.

Copy before and after

Hosts and connection setup

Where it appears	Before	After
Home, disabled local host	This computer is off	This host is disabled in T3 Code
Home, how to enable the host	Turn it back on, or connect a different computer.	Enable it in Connections, or connect another host.
Home, no connection	No computer connected	No host connected
Home, where agents run	Your agents run on your computer.	Your agents run on your computer.
Home, when T3 Connect is unavailable	Your agents run on your computer. Start T3 Code there first.	Your agents run on your host. Start T3 Code there first.
Home, waiting for a connection	Waiting for your computer…	Waiting for your host…
Home, command caption	Run on your computer:	Run on your host:
T3 Connect setup, introduction	Mesh your devices together. Publish this environment and connect the rest, all in one place.	Use T3 Code on your other devices. Choose what to share and which hosts to connect.
T3 Connect setup, first step	Publish	Share {hostName}, or Share this host if the name is unavailable
T3 Connect setup, remote-access switch	Publish this environment	Allow access to this environment through T3 Connect
T3 Connect setup, remote-access help	Make this environment available to your other devices through T3 Connect.	Connect to {hostName} from other devices signed in to your account. If the name is unavailable, use "this host".
Mobile, alternative to direct pairing	Or use the managed relay	Or use T3 Connect

Pairing and permissions

Where it appears	Before	After
Create pairing link dialog	Generate a one-time link that another device can use to pair with this backend as an authorized client.	Generate a single-use link to connect another device to this T3 Code server.
Pairing link, when no shareable URL is available	Copy the token and pair from another client using this backend's reachable host.	Copy the pairing code. On your other device, enter it alongside this server's address.
Pairing QR area, when the address only works locally	No QR for this endpoint. Another device scanning a loopback link would dial itself; copy the URL for use on this machine instead.	Not showing a QR code because this address only works on this device. Use a network address instead, or copy the link to use it here.
Connection permissions, web	These permissions apply to your active route. Other routes may have different permissions.	These permissions only apply to the current connection. Other ways of connecting may have different permissions.
Connection permissions, mobile	Applies to the route marked In use. Other routes may have different permissions and have not been checked.	These permissions only apply to the current connection. Other ways of connecting may have different permissions.
Current connection permissions, web	These permissions apply to this client’s current connection.	These permissions only apply to the current connection.

Agent activity on mobile devices

Where it appears	Before	After
Agent-activity switch, setup and Connections settings	Publish agent activity	Send agent activity to mobile devices
Setup, agent-activity help	Send activity from this environment to your mobile clients for push notifications and Live Activities.	Use agent activity in push notifications or Live Activities on your phone.
Connections settings, agent-activity help	Send activity to mobile notifications and Live Activities without T3 Connect.	Use agent activity in push notifications or Live Activities on your phone.
Agent-activity switch, screen-reader label	Publish agent activity to mobile clients	Send agent activity to mobile devices
Confirmation after enabling activity	This environment publishes agent activity to your mobile clients.	This environment sends agent activity to your mobile devices.
Confirmation after disabling activity	This environment will stop publishing agent activity.	This environment will stop sending agent activity to your mobile devices.
Confirmation after disabling the tunnel while activity stays enabled	The managed tunnel was removed. Agent activity publishing stays on.	The managed tunnel was removed. Agent activity stays enabled.

The setup step and remote-access help use the current host's name, for example, "Share MacBook Pro" and "Connect to MacBook Pro from other devices signed in to your account." The empty home screen has no connected host to name, so the highlighted sentence keeps "computer". Its other instructions use "host".

The updated switch label also appears in settings search. Desktop uses the same web copy.

Scope and approval

Copy-only maintenance. The exact wording and four-PR split were requested and approved in the originating T3 Code conversation. Runtime behavior and defaults are unchanged.

Verification

• vp run check:changed passes on this independent branch.
• Opened Connections and the Create pairing link dialog in the real web client against isolated worktree state. Captured the existing and updated dialog without generating a pairing link.
• Matching mobile copy is covered by the changed-package typecheck. Native mobile screens were not exercised.

Screenshots

Before and after: Create pairing link dialog

Before

After

Model: GPT-6.1-Sol. Harness: Codex in T3 Code.

[macroscopeapp]

Approvability

Verdict: Approved at 9594df3

Macroscope's review found this PR approvable — Clarifies connection, pairing, host, and permission wording across mobile and web, including host-specific onboarding labels. Existing connection behavior, access controls, and product defaults are unchanged.

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

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: 9594df3

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 5ef5685
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: fa172980-4342-4cb4-baf9-a6f2b6fb2993

Commits

Reviewing files that changed from the base of the PR and between 4be7f76 and 9594df3.

Files selected for processing: 8

• apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx
• apps/mobile/src/features/settings/EnvironmentRoutesSection.tsx
• apps/web/src/components/HostedEmptyState.tsx
• apps/web/src/components/cloud/ConnectOnboardingDialog.tsx
• apps/web/src/components/settings/AuthorizedClientsSettings.tsx
• apps/web/src/components/settings/SavedEnvironmentRows.tsx
• apps/web/src/components/settings/SessionPermissions.tsx
• apps/web/src/components/settings/settingsSearch.ts

Files skipped from review as they are similar to previous changes: 8

• apps/mobile/src/features/settings/EnvironmentRoutesSection.tsx
• apps/web/src/components/HostedEmptyState.tsx
• apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx
• apps/web/src/components/settings/SavedEnvironmentRows.tsx
• apps/web/src/components/settings/AuthorizedClientsSettings.tsx
• apps/web/src/components/settings/SessionPermissions.tsx
• apps/web/src/components/settings/settingsSearch.ts
• apps/web/src/components/cloud/ConnectOnboardingDialog.tsx

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

Walkthrough

This pull request updates interface wording for T3 Connect, hosts, connection permissions, device pairing, and agent activity sent to mobile devices. The described sign-in and connected-environment behavior remains unchanged.

Changes: Connection and activity copy

Layer / File(s)	Summary
Connection and host labels apps/mobile/src/features/connection/ConnectionsNewRouteScreen.tsx, apps/web/src/components/HostedEmptyState.tsx	The T3 Connect heading and hosted environment messages use updated connection and host terminology.
Pairing and permission guidance apps/mobile/src/features/settings/EnvironmentRoutesSection.tsx, apps/web/src/components/settings/AuthorizedClientsSettings.tsx, apps/web/src/components/settings/SessionPermissions.tsx	Pairing instructions describe using a pairing code and server address. Permission notices describe the scope of the current connection.
Access and mobile activity wording apps/web/src/components/cloud/ConnectOnboardingDialog.tsx, apps/web/src/components/settings/SavedEnvironmentRows.tsx, apps/web/src/components/settings/settingsSearch.ts	The onboarding dialog, saved environment settings, and settings search use updated language for T3 Connect access and sending agent activity to mobile devices.

Priority: Low

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

Change: Other

Merge Risk: Minimal · up to 9594d

No actionable issue remains from this review; the change is mergeable after normal checks.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title is concise, uses the repository's conventional format, and accurately describes the copy changes for connection setup and pairing.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description check		The description includes the required Problem, Change, Scope and approval, Verification, and UI evidence sections. It clearly describes the copy changes, approval basis, verification results, limitati…

Full details: Description check

Explanation

The description includes the required Problem, Change, Scope and approval, Verification, and UI evidence sections. It clearly describes the copy changes, approval basis, verification results, limitations, and before/after screenshots. It does not include a direct approval link or maintainer approval comment, and the screenshots cover only the pairing dialog, but the description is otherwise mostly complete.

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Dismissing prior approval to re-evaluate 98aadca

Dismissing prior approval to re-evaluate 4e55003

Dismissing prior approval to re-evaluate 4be7f76

Dismissing prior approval to re-evaluate 9594df3

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

thanks @extoci. your copy makes disabled hosts, pairing, connection permissions, and mobile activity sharing clearer while preserving the existing actions.

merged current main into your branch without rewriting its three commits. resolved the onboarding and settings-search conflicts, kept main's account/tunnel-limit controls and /settings/access destination, and changed the disabled-host instruction to "Environments" to match the current section and button. compared the original diff with the final eight-file diff; no original pieces were dropped.

verification at 9594df369d702055dab977495f5e3ea2dafd4aa5:

• blacksmith vp run check:changed passed: formatting, lint, knip, affected web/mobile/scripts typechecks, 22 existing tests, and 12 focused compiler checks.
• real chrome client: opened pairing, inspected the updated copy, changed read-only permissions from 16 selected scopes to 4, restored standard permissions, cancelled, and opened the current-connection permissions panel.
• both independent read-only reviews approved this head with no findings.
• native mobile, electron shell, signed-in T3 Connect onboarding/activity delivery, and remote pairing were not exercised. their actions and permission logic are unchanged. all 33 ci checks are green; macroscope approved and coderabbit reported no actionable findings.

matching pairing-dialog captures using current main's copy and this head:

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

Verified in a real dev environment

verified unchanged head 9594df369d702055dab977495f5e3ea2dafd4aa5 on a linux boat vm using repository Playwright and /usr/bin/google-chrome. no mocks, fixtures, or demo provider. no code changes or pushes.

• reproduced the old pairing description on github/main (e5909e53c3) in a separate worktree after vp i. stopped that server before starting the pr. opened Settings > Sharing & access > Create link on both with matching empty-label, standard-permission state. the pr renders the single-use server wording.
• exercised Read only (4 scopes), Standard (16 scopes), and Cancel. created a real read-only code and paired an independent chrome session by entering the code and server address. the new fallback instructions render. its permission panel shows the new current-connection wording, four allowed scopes, twelve not granted, and no create-link control.
• reused the consumed code in another session: rejected as invalid. revoked the paired client through the app: that client returned to pairing on reload.
• added a project pointing at a real git repository through the app, created a thread, selected Codex gpt-6.1-sol, and submitted a real turn through the local proxy. native provider events show a completed turn with no error and connection verification passed.; the same reply appears in the web client after reopening the thread.
• Blacksmith vp run check:changed 5ef56853ef1854da50bc1909c6c0a32700f2cb13 passed: format, lint, knip, web/mobile/scripts typechecks, 22 existing adjacent tests, and 12 compiler checks. the explicit base is needed because the worker snapshot lacks origin/main; fetched the pr history on that worker. head CI: 33 successful, none failing or pending.

runtime transcript

Not verified

native iOS/Android and Electron shell behavior were not exercised on this linux web pass. signed-in T3 Connect onboarding, host-name interpolation, tunnel/activity toggles and notifications require an account and other devices; those flows were not exercised. hosted no-host/disabled-host states, remote-route permission help, and the loopback QR explanation were not reached in this local-server setup. other providers and cross-network pairing were not exercised.

the initial thread view did not display the completed provider response until reload/reopening; live reply rendering is therefore not verified as healthy. the response persisted and rendered afterward. this eight-file copy-only diff does not change that path, and no unrelated fix was made.

uploaded video playback and seeking were checked in chrome. task dev servers are stopped after verification.