feat: show in-app web apps only to already-connected users - #5438
YellowSnnowmann wants to merge 2 commits into
Conversation
The in-app web apps (Accounts webview rail) are being removed from the app after 31 August 2026. Hide the feature from users who never connected one and show a persistent removal notice to those who have. - Remove the "Add apps" button + AddAccountModal from the sidebar rail and the deep-link accounts step; already-connected apps still show and can be reconnected or disconnected. Zero connected -> only the agent tile. - Add a non-dismissable WebAppsSunsetNotice, shown only when at least one app is connected, mounted beside the other shell banners. - Add webAppsSunset.* copy to every supported locale. Closes tinyhumansai#5423
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (21)
Comment |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 58c5b6474f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
The accounts/setup deep link stays reachable (old chat/onboarding pills can dispatch it), so a user who never connected a web app could still see the removal notice — a trace of the retired feature tinyhumansai#5423 requires hiding. Gate the step on order.length (consistent with the shell banner and rail): for a never-connected user it now closes without rendering anything.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Closing this as superseded by upstream. This PR gated the in-app web apps (the Accounts webview rail) and added a non-dismissable 31-Aug-2026 sunset notice, i.e. it hid the feature ahead of its planned removal. Since it was opened, upstream That deletes the exact surface this PR touched — the merge conflicts here are modify/delete against files upstream removed. Resolving them would mean re-introducing the deleted The sunset goal (#5423) is fully satisfied by the upstream removal, so there's nothing left to gate. Closing. |
Summary
WebAppsSunsetNotice, shown only when ≥1 app is connected, mounted beside the other shell banners.webAppsSunset.*copy added to every supported locale.Problem
New users shouldn't pick up a feature that's about to disappear, and existing users need a clear heads-up. The app had no way to gate the web-apps entry points by "has this user connected one?".
Solution
The durable "already connected" signal is the persisted Redux
accountsslice (survives session drops), so a channel that dropped its session still shows for reconnect while a never-connected one shows nothing. All add-new entry points are removed; a non-dismissable banner names the 31 August 2026 date.Submission Checklist
Closes #NNNImpact
Related
AI Authored PR Metadata (required for Codex/Linear PRs)
N/A — not a Codex/Linear-authored PR.
Validation Run
pnpm --filter openhuman-app format:checkpnpm typecheck