Add pagination to NewChatPage by sharabai · Pull Request #88452 · Expensify/App

sharabai · 2026-04-21T16:07:34Z

Explanation of Change

Note

#87881 must be merged first

Add pagination to `NewChatPage` (`usePaginatedData`)

Problem: Pagination used to live inside SelectionListWithSections. The screen prepared all personal details up front and the list just revealed more already-computed rows on scroll — purely visual, no real work saved. The screen had no control or visibility over it; you'd normally expect pagination at the data-preparation level, and the data flow in NewChatPage is complicated enough that it was easy to miss that pagination wasn't happening there at all. The new list doesn't carry this forward, so New Chat lost even the visual pagination while still processing the full list.

Approach: Move pagination up to the screen (NewChatPage) using a small, generic hook (usePaginatedData), applied at two points:

Before data preparation — cap how many raw personal details are processed (real pagination).
After the whole flow, before passing rows to the list, while searching — cap filtered rows (visual pagination, at the source).

Important

the two usages serve different purposes and are mutually exclusive:

Load flow (not searching) — slice before the heavy processing so less work is done on initial open; this is the real performance win.
Searching — the first pagination is skipped so search runs against the full dataset; instead, a purely visual pagination caps the filtered rows passed to the list. It works against already-processed data, so it doesn't affect performance — it's only there to keep the FlashList scroll from collapsing to something too small when the search result set is large.

Why: Pagination at the list level hid both work and intent. Owning it at the screen with a dedicated hook makes the data-prep flow traceable and controllable — on initial load (and whenever the user is not searching) "seeing pagination" now actually matches "pagination is happening."

Note

A purely visual pagination is still kept while the user is searching — search itself runs against the full dataset, but filtered rows are still fed into the list in chunks so the list doesn't mount everything at once.

Sort and dedupe before slicing (alphabetical pagination)

Problem: With pagination at the screen, page 1 was the first PAGINATION_SIZE of Object.values(personalDetails) — accountID order, not alphabetical. filterAndOrderOptions then alphabetized only that arbitrary slice, so loadMore could reveal a name that sorted earlier than already-visible rows. Imported phone contacts had the same issue; an Onyx-PD/contact login overlap also wasted page slots before the late dedupe in OptionsListUtils stripped one.

Approach: Dedupe + alphabetically sort the union of Onyx personal details and imported phone contacts upstream of pagination, in a small pure helper (mergeAndSortPersonalDetailsWithContacts). Dedupe key: addSMSDomainIfPhoneNumber(login).toLowerCase(). Onyx PDs are spread first, so on collision the real-accountID copy wins over the optimistic contact copy. The late personalDetails.concat(contacts) is removed (contacts are already merged upstream). While here, orderPersonalDetailsOptions is generic-ised and its sort key aligned with personalDetailsComparator, so the upstream sort agrees with the heap re-sort inside getValidOptions.

Why: A paginated slice should match the user's mental model of "first page." Sorting + deduping upstream makes page 1 the alphabetical prefix and loadMore strictly append-only under a stable data snapshot.

Performance gains on opening New Chat

With this change, opening NewChatPage on accounts with a large contact list is noticeably faster — +75.88 ms
(+22.2%) without the pagination.

Measured by forcing skipPagination: true on the first usePaginatedData usage (the one before data preparation) to simulate the previous behavior, and comparing against the current code with pagination enabled.

Fixed Issues

$ #86089
PROPOSAL:

Tests

Load-flow pagination (initial open)

Open the New Chat page
Verify the contacts list shows only a small slice (the scrollbar is short relative to the total number of contacts you know the account has)
Scroll to the bottom of the contacts list
Verify more contacts load in and the scrollbar grows, repeating as you keep scrolling

Visual pagination while searching

Open the New Chat page
Type a query in the search field that matches many contacts
Verify results are shown and the list is capped to a small initial slice (short scrollbar again), not the full filtered set
Scroll to the bottom of the search results
Verify more matching contacts are revealed as you scroll
Change the query (or clear it)
Verify the list resets back to its first page and pagination works again from the top

Sort + dedupe correctness

Open the New Chat page on an account where someone with a high accountID has an early alphabetical name (e.g. "Aaron")
Verify they appear on page 1, not after scrolling
Scroll to load more pages — already-visible rows must keep their order; new rows only append below
If applicable: verify a person who exists in both your phone contacts and Expensify appears exactly once (with the Onyx avatar/display name)

Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

pagination.mp4

codecov · 2026-04-21T16:16:42Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
.../components/SelectionList/components/TextInput.tsx	`97.36% <100.00%> (ø)`
src/hooks/useFilteredOptions.ts	`82.35% <100.00%> (ø)`
src/hooks/usePaginatedData.ts	`100.00% <100.00%> (ø)`
src/libs/OptionsListUtils/index.ts	`84.98% <100.00%> (ø)`
src/libs/ReportUtils.ts	`84.83% <ø> (-0.05%)`	⬇️
...hatPage/mergeAndSortPersonalDetailsWithContacts.ts	`100.00% <100.00%> (ø)`
...es/NewChatPage/useGroupChatDraftParticipantSync.ts	`100.00% <100.00%> (ø)`
src/pages/NewChatPage/index.tsx	`78.01% <76.92%> (-0.78%)`	⬇️
... and 42 files with indirect coverage changes

staszekscp · 2026-04-23T07:54:35Z

+    if (skipPagination) {
+        return {paginatedData: data, loadMore: () => {}, hasMore: false};
+    }
+
+    if (pageSize < 1) {
+        return {paginatedData: [], loadMore: () => {}, hasMore: false};
+    }


Could these early returns can go above the if (resetKey !== prevResetKey) condition? 🤔

at first, after reading this question, I though it would be better to move it down. But actually it needs to stay in place.

Example:

usePaginatedData(data, pageSize, { resetKey: "false", skipPagination:false}) // some time later usePaginatedData(data, pageSize, { resetKey: "true", skipPagination:true}) // some time later usePaginatedData(data, pageSize, { resetKey: "false", skipPagination:false})

If we move the condition down, the change in resetKey would go unnoticed; the pagination would not reset to the first page.

staszekscp · 2026-04-23T08:11:12Z

+        paginatedData: personalDetails,
+        loadMore: loadMorePersonalDetails,
+        hasMore: hasMorePersonalDetails,
+    } = usePaginatedData(allPersonalDetailOptions, PAGINATION_SIZE, {skipPagination: isSearching, resetKey: String(isSearching)});


If isSearching return a boolean so doesn't String(isSearching) return "true" or "false"? I think it might be a mistake

That's an area I was also unsure about. It looks a little bit off, and I'm open to suggestions how to do it better.

Returning to your question, I intentionally type casted boolean to get "true"/"false" as the resetKey.

What case am I trying to handle here?

Initial load -> use this pagination

User starts typing in search field -> skip pagination in this place

User clears search query -> pagination is back, but page is reset

isSearching is a perfect flag for when we should reset pagination, but since key is typed as a string, I casted the boolean value here.

I tried to do something similar to React Component key, which is defined as:

interface Attributes { key?: Key | null | undefined; } type Key = | string | number | bigint

It does not accept a boolean value, and it makes sense, especially here with the name resetKey, which is a key that on change would cause a reset to internal state. If it also accepted a boolean value, it becomes a bit hard to understand the intent of the prop. What does resetKey: true mean? So I'd stick with a string type.

Ideally I'd change the key only once when we go back from isSearching: true -> false. And it needs to a string value for reasons explained above.
The simple String(isSearching) does it well, wouldn't cause unnecessary re-renders when the searchTerm is changing like a -> ab -> abc -> abcd.

The casting may look strange, but it does what it set out to do, causes only one additional re-render vs potentially many more by passing searchTerm

It could always be handled more explicitly (we can write out explicit logic to track changes between renders to isSearching and change the key only on the flip from true to false), but imo String(isSearching) is enough.

@staszekscp I agree with your point that it might be confusing, so I used a more explicite string key here, so that next devs would not have to wonder if this was done intentionally.
Now is smth like: isSearching ? 'OneKey' : 'AnotherKey'

staszekscp · 2026-04-23T08:16:13Z

+import isLoadingOnyxValue from '@src/types/utils/isLoadingOnyxValue';
+import type SelectedOption from './types';
+
+function useGroupDraftRestore(


I wonder if this hook should be renamed of have at least some comment to explain what it does, because it doesn't seem intuitive to me 😄

Yeah, totally makes sense! This was also flagged by a reviewer on a previous PR that the current one is based from.
Now that I rebased to only include the relevant commits to this PR, js doc is in place.

staszekscp · 2026-04-23T10:11:15Z

+    const shouldRestoreSelectedOptionsRef = useRef(true);
+    const isScreenInBackgroundRef = useRef(false);


Why are these values treated as refs?

To avoid causing re-renders.
They control the returned value from the selector. And the selector itself causes re-renders. But we normally don't need those values (only in the few exceptions). Normally, selector's supposed to return undefined (nothing) and not react to changes in the draft from Onyx.

staszekscp · 2026-04-23T10:13:10Z

+        if (!isSubscriptionActive) {
+            return undefined;
+        }
+        return draft?.participants;


Wouldn't eg. empty array be more natural here so we can avoid nullish coalescing in its usage?

Tried applying this change, but the field returned first in ternary is itself possibly undefined, so unfortunately it didn't help.

Even if the selector always returns an array (guarded with additional nullish coalescing operator),

the value returned from onyx is still possibly undefined.

staszekscp · 2026-04-23T10:18:34Z

+            isScreenInBackgroundRef.current = false;
+
+            return () => {
+                isScreenInBackgroundRef.current = true;


Isn't there any utility function from Navigation to check if the screen is backgrounded? 🤔

Great catch!
The useIsFocused, but it causes re-renders. I need a ref here, but even then, there's a hook useIsFocusedRef, which I myself refactored out from some component some time ago because I needed it.
Thanks, I'll be able to shorten boilerplate code here.

sharabai · 2026-04-23T16:39:46Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d1abdd0b1f

ℹ️ 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".

chatgpt-codex-connector · 2026-04-23T16:54:16Z

+
+    if (resetKey !== prevResetKey) {
+        setPrevResetKey(resetKey);
+        setCurrentPage(1);


Reset pagination state before slicing data

When resetKey changes after the user has already loaded multiple pages, this hook queues setCurrentPage(1) but still computes limit from the previous currentPage in the same render. That means one render returns too many rows for the new context (for example, after changing the search term), which can briefly show stale pagination and trigger extra onEndReached work before the next render corrects it.

Useful? React with 👍 / 👎.

When you call the set function during render, React will re-render that component immediately after your component exits with a return statement, and before rendering the children.

sharabai · 2026-04-23T17:27:40Z

@codex review

chatgpt-codex-connector · 2026-04-23T17:41:13Z

Codex Review: Didn't find any major issues. Keep it up!

ℹ️ 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".

sharabai · 2026-04-27T12:12:48Z

@codex review

chatgpt-codex-connector

💡 Codex Review

App/src/pages/NewChatPage/index.tsx

Lines 109 to 111 in c00fd1e

    
               reports, 
        
               personalDetails: personalDetails.concat(contacts), 
        
           },

Move contact pagination after ordering

Paginating allPersonalDetailOptions before calling getValidOptions means we sort and filter only an arbitrary raw slice (Object.values order) instead of the full contact set, so the first page can exclude contacts that should be at the top (e.g., alphabetically) and then reorder/jump when more pages are loaded. getValidOptions/filterAndOrderOptions are where personal details are actually ordered, so slicing needs to happen after those steps to preserve stable, correct list ordering.

ℹ️ 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".

sharabai · 2026-04-28T14:27:47Z

@codex review

chatgpt-codex-connector · 2026-04-28T14:43:44Z

Codex Review: Didn't find any major issues. Another round soon, please!

ℹ️ 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".

sort alphabetically before paginating add tests

sharabai · 2026-04-29T13:16:13Z

@codex review

chatgpt-codex-connector · 2026-04-29T13:39:22Z

Codex Review: Didn't find any major issues. Another round soon, please!

ℹ️ 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".

sharabai · 2026-04-30T17:41:02Z

@NikkiWines
I didn't change much the utils from the the PR you mentioned. I’m happy to defer to your judgment here since you have more context 👍

NikkiWines · 2026-04-30T17:51:08Z

Yeah, i think there's some potential for conflicts if we reimplement the changes in the linked PR - just want to make sure nothing overlaps before we move forward with this one 🙇

NikkiWines · 2026-05-07T17:25:29Z

Confirmed we're keeping this on hold for now

NikkiWines · 2026-05-18T14:14:45Z

Still on hold pending this

NikkiWines · 2026-05-29T15:59:49Z

helloooo 👋 sorry for the delay, but it looks like we can now move forward with this PR 🙇

…reparation/pagination

sharabai · 2026-06-01T16:05:17Z

@staszekscp, @NikkiWines, @dukenv0307 PR is ready. Conflicts've been resolved.

dukenv0307 · 2026-06-02T03:14:33Z

Looks good to me

Screen.Recording.2026-06-02.at.10.13.19.mov

staszekscp

Looking good! Good job!

staszekscp · 2026-06-02T07:16:20Z


    const handleEndReached = () => {
-        if (!hasMore || !areOptionsInitialized || !isScreenFocusedRef.current) {
+        if ((!hasMoreFilteredPersonalDetails && !hasMorePersonalDetails && !hasMore) || !areOptionsInitialized || !isScreenFocusedRef.current) {


NAB: I had to think for a moment to understand this condition 😄 Maaaaybe this could become a separate hasMoreData variable instead of (!hasMoreFilteredPersonalDetails && !hasMorePersonalDetails && !hasMore)

@staszekscp yep, it took me a moment to remember what this condition checked too 😅. Which is a good indicator that changing it would help.

NikkiWines

looks good, couple very small things

NikkiWines · 2026-06-08T14:25:57Z

@sharabai friendly bump here 🙇

staszekscp · 2026-06-09T08:46:06Z

Hey @NikkiWines! On behalf of @sharabai I wanted to let you know that Sergei is on sick leave and will handle the review after he's back in shape! Also, sorry for not responding since Wednesday, but Thursday and Friday there was a bank holiday in Poland and we all were OOO 😄

NikkiWines · 2026-06-09T09:20:10Z

No worries, thanks for the update @staszekscp 🙇 Hope you get well soon @sharabai, and I hope you all had a good holiday weekend

sharabai · 2026-06-10T10:17:32Z

@NikkiWines thanks for the suggestions! Looks cleaner with them.

…reparation/pagination

NikkiWines

github-actions · 2026-06-10T14:13:54Z

🚧 @NikkiWines has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-06-10T14:19:59Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #88452.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7f08aa69c94-5dd32c1-def0d445f13b7769001e0b2c8f2c7eb67a4f8d1a/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7f08aa6-5dd32c1-1891acd2c546c832bee7cea6312f8209360d2e5a/index.html

Web 🕸️
https://88452.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-06-10T23:50:14Z

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.4.5-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-06-10T23:53:00Z

Help site review — no docs changes required

I reviewed the changes in this PR against the help articles under App/docs/articles, and no help site updates are needed. I did not create a draft docs PR.

Why: This PR is an internal performance/architecture refactor of how NewChatPage prepares its contact data — it moves pagination up to the screen (usePaginatedData), and sorts/dedupes personal details + imported contacts before slicing. None of this changes the user-facing workflow documented in the help site:

The relevant article, Create a New Chat, describes the steps to start a private/group/room chat (click + → Start Chat → enter name/email/phone → select). Those steps are unchanged.
The changes (load-flow pagination, visual pagination while searching, alphabetical sort/dedupe) are about how fast and in what order contacts are processed/revealed — implementation details, not documented behavior. The help site does not describe contact-list pagination or sort order, so there is nothing to update or correct.
No new features, settings, tabs, buttons, or labels were introduced.

Files reviewed

All 12 changed files are TypeScript source/tests (usePaginatedData.ts, NewChatPage/index.tsx, mergeAndSortPersonalDetailsWithContacts.ts, OptionsListUtils, ReportUtils, hooks, and unit tests). None are under docs/articles, and none alter a customer-facing flow.

If you believe a customer-facing behavior did change in a way that should be documented, let me know what the user would observe and I'll draft the docs update.

OSBotify · 2026-06-11T23:41:46Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.5-6 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

melvin-bot Bot assigned sharabai Apr 21, 2026

sharabai changed the title ~~Fix/new chat page/data preparation/pagination~~ Add pagination to NewChatPage Apr 21, 2026

sharabai mentioned this pull request Apr 21, 2026

[Due for payment 2026-06-18] [HOLD] Start chat - All contacts load instead of 50 contacts per page #86089

Open

7 tasks

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch 2 times, most recently from 32a8f31 to f020be6 Compare April 22, 2026 13:40

staszekscp reviewed Apr 23, 2026

View reviewed changes

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch 2 times, most recently from 68fe534 to 9e86bb0 Compare April 23, 2026 11:34

sharabai requested a review from staszekscp April 23, 2026 16:27

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch from c15ac76 to d1abdd0 Compare April 23, 2026 16:33

chatgpt-codex-connector Bot reviewed Apr 23, 2026

View reviewed changes

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch 2 times, most recently from bebd537 to c00fd1e Compare April 27, 2026 11:58

chatgpt-codex-connector Bot reviewed Apr 27, 2026

View reviewed changes

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch from c00fd1e to 0a2cfc1 Compare April 28, 2026 14:27

add pagination hook

6d23e93

sort alphabetically before paginating add tests

sharabai force-pushed the fix/newChatPage/dataPreparation/pagination branch from 0a2cfc1 to 6d23e93 Compare April 29, 2026 13:15

sharabai marked this pull request as ready for review April 29, 2026 13:54

sharabai requested review from a team as code owners April 29, 2026 13:54

melvin-bot Bot requested a review from dukenv0307 April 29, 2026 13:54

NikkiWines changed the title ~~[HOLD] Add pagination to NewChatPage~~ Add pagination to NewChatPage May 29, 2026

sharabai added 2 commits June 1, 2026 17:36

Merge remote-tracking branch 'origin/main' into fix/newChatPage/dataP…

003e26f

…reparation/pagination

Remove arbitrary stings, add clarifying comments

7fc615a

dukenv0307 approved these changes Jun 2, 2026

View reviewed changes

staszekscp approved these changes Jun 2, 2026

View reviewed changes

Refactor: change var names

8d30a5e

NikkiWines requested changes Jun 3, 2026

View reviewed changes

Comment thread src/hooks/useFilteredOptions.ts Outdated

Comment thread src/hooks/usePaginatedData.ts

Comment thread src/pages/NewChatPage/index.tsx Outdated

Apply reviewer suggestions

1801324

sharabai added 3 commits June 10, 2026 13:45

Merge remote-tracking branch 'origin/main' into fix/newChatPage/dataP…

6286eeb

…reparation/pagination

Fix lint

c21b360

Fix prettier

a48299e

NikkiWines approved these changes Jun 10, 2026

View reviewed changes

NikkiWines merged commit 7f08aa6 into Expensify:main Jun 10, 2026
32 checks passed

OSBotify mentioned this pull request Jun 10, 2026

Deploy Checklist: New Expensify 2026-06-10 #93219

Closed

72 tasks

		const shouldRestoreSelectedOptionsRef = useRef(true);
		const isScreenInBackgroundRef = useRef(false);

	reports,
	personalDetails: personalDetails.concat(contacts),
	},

Conversation

sharabai commented Apr 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Add pagination to NewChatPage (usePaginatedData)

Sort and dedupe before slicing (alphabetical pagination)

Performance gains on opening New Chat

Fixed Issues

Tests

Load-flow pagination (initial open)

Visual pagination while searching

Sort + dedupe correctness

Offline tests

QA Steps

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Apr 21, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sharabai commented Apr 23, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Apr 23, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sharabai commented Apr 23, 2026

Uh oh!

chatgpt-codex-connector Bot commented Apr 23, 2026

Uh oh!

sharabai commented Apr 27, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

sharabai commented Apr 28, 2026

Uh oh!

chatgpt-codex-connector Bot commented Apr 28, 2026

Uh oh!

sharabai commented Apr 29, 2026

Uh oh!

chatgpt-codex-connector Bot commented Apr 29, 2026

Uh oh!

sharabai commented Apr 30, 2026

Uh oh!

sharabai commented Apr 21, 2026 •

edited

Loading

Add pagination to `NewChatPage` (`usePaginatedData`)

codecov Bot commented Apr 21, 2026 •

edited by github-actions Bot

Loading

sharabai Jun 3, 2026 •

edited

Loading