[Payment due @huult] Render server-driven AZ status on expense reports by inimaga · Pull Request #95959 · Expensify/App

inimaga · 2026-07-13T14:37:59Z

Explanation of Change

Held on:

This PR updates the AgentZero status provider so non-chat reports can mount the status gate when the server has written an AgentZero processing indicator NVP, allowing parent expense reports to show server-driven thinking/status bubbles. Expense reports without server status still skip optimistic kickoff, and unit coverage now verifies both the server-driven render path and the quiet default path.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/651801
PROPOSAL: N/A

Tests

Verify that no errors appear in the JS console

Manual tests

Pre-requisite (Skip to Test Steps if testing in/with Staging/Prod):

Ensure you have AZ/Concierge is setup in dev
Checkout, compile, and run https://github.com/Expensify/Auth/pull/22870 in Auth
Checkout and run https://github.com/Expensify/Web-Expensify/pull/54486 in Web-E
Checkout and run [Payment due @huult] Render server-driven AZ status on expense reports #95959 (current branch) in App and login with a test account

Test Steps:

Create or open an expense report that contains at least two expenses with different merchants, for example McDonalds and Starbucks.
Go on the parent multi-expense report, not the individual transaction thread.
Type and and send a concierge request like: 'Update the description for the McDonalds expense to "Lunch with James"'?
Wait a while, then verify the McDonalds expense description is updated to 'Lunch with James'.
Verify Concierge posts a visible acknowledgement in the parent report, for example: I’ve added the description
“Lunch with James” to the McDonalds expense on this report.

Expected result:

Concierge should emit/show a thinking indicator while the request is in progress. At the end of which, the description update succeeds and the parent multi-expense report receives a visible Concierge acknowledgement.

Issue.651801.-.Manual.Test.mp4

Offline tests

QA Steps

Same as manual test steps above

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

…se-reports

…iven-AZ-status-on-expense-reports # Conflicts: # src/pages/inbox/report/ReportActionsListTailIndicator.tsx # tests/unit/ReportActionsListTailIndicatorTest.tsx

melvin-bot · 2026-07-17T11:13:49Z

@huult Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 056f875ba5

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

huult · 2026-07-17T11:54:20Z

Reviewer Checklist

Screenshots/Videos

Android: HybridApp

Screen.Recording.2026-07-21.at.15.34.37.mov

Android: mWeb Chrome

Screen.Recording.2026-07-21.at.15.39.27.mov

iOS: HybridApp

Screen.Recording.2026-07-21.at.15.43.42.mov

iOS: mWeb Safari

Screen.Recording.2026-07-21.at.15.52.08.mov

MacOS: Chrome / Safari

Screen.Recording.2026-07-21.at.15.19.32.mov

joekaufmanexpensify

Good for product 👍

huult · 2026-07-20T06:14:55Z

@inimaga Could you help set up your local env so I can access it to test this PR?

…se-reports

inimaga · 2026-07-20T11:58:15Z

@huult You don't need the additional setup. The backend PR is already deployed so you can test directly against staging. In the instructions for manual test above, you can go straight to test steps.

codecov · 2026-07-20T12:36:40Z

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 Δ
.../MoneyRequestReportView/MoneyRequestReportView.tsx	`55.91% <100.00%> (+0.96%)`	⬆️
src/pages/inbox/AgentZeroStatusContext.tsx	`95.08% <100.00%> (+0.16%)`	⬆️
src/pages/inbox/report/ReportActionsList.tsx	`83.94% <100.00%> (ø)`
...es/inbox/report/ReportActionsListTailIndicator.tsx	`100.00% <100.00%> (ø)`
...equestReportView/MoneyRequestReportActionsList.tsx	`62.67% <43.75%> (-1.36%)`	⬇️
... and 32 files with indirect coverage changes

github-actions · 2026-07-20T12:48:18Z

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

huult · 2026-07-21T05:48:14Z

Screen.Recording.2026-07-21.at.12.46.46.mov

Yeah, I can see it. I'll do some more testing and update the checklist.

huult · 2026-07-21T06:06:16Z

Screen.Recording.2026-07-21.at.12.58.44.mov

Reproduction Steps

Create a report.
Create 4 expenses:
- 3 expenses with the description "McDonalds"
- 1 expense with the description "Starbucks"
Send the message:

Update the description for the McDonalds expense to "Lunch with James"
Select the "All 3 expenses" option from Concierge.
Verify that the descriptions are updated from "McDonalds" to "Lunch with James".
Send another message:

Update the description for the McDonalds expense to "Lunch"

Current behavior:
The descriptions are updated from "Lunch with James" to "Lunch", even though there are no longer any expenses with the description "McDonalds".

Expected behavior:
The update should not be applied because no expense with the description "McDonalds" exists anymore.

@inimaga Could you take a look at this issue?

huult · 2026-07-21T06:31:40Z

Untitled.2.mov

@inimaga I occasionally encounter this issue. After sending a request, Concierge remains in the "Thinking..." state and never returns a response.

Retrying the same request usually succeeds:

Screen.Recording.2026-07-21.at.13.24.43.mov

huult · 2026-07-21T06:38:07Z

Screen.Recording.2026-07-21.at.13.33.13.mov

Create a report with 2 expenses:
- One expense with the description "McDonalds"
- One expense with the description "Starbucks"
Send the following message:

Update the description for the McDonalds expense to "Lunch"
While Concierge is showing "Thinking...", send another message:

Update the description for the Starbucks expense to "Lunch with James"

Current behavior

After Concierge finishes processing, only the McDonalds expense is updated to "Lunch". The second request is not processed, and Concierge does not post the expected acknowledgement message for it.

Expected behavior

After the first request completes, Concierge should also process the second request (or clearly indicate that it cannot). An acknowledgement message should be posted for each successfully completed request.

@inimaga could you check this issue?

huult · 2026-07-23T02:25:26Z

@inimaga Could you take a look at my comment when you have a chance?

inimaga · 2026-07-23T14:27:42Z

@huult Sorry for the delay here.

Regarding the flagged issues;

For issue 1: Send an initial message to change the description, and a subsequent message referencing the old changed description.

Current behavior:
The descriptions are updated from "Lunch with James" to "Lunch", even though there are no longer any expenses with the description "McDonalds".

Expected behavior:
The update should not be applied because no expense with the description "McDonalds" exists anymore.

The fix for this belongs in the backend. Thanks for flagging. I will create a separate issue to track this. The App PR only renders the status indicator so I want the potential blockers here to only be focused on this.

For issue 2: Occasional stuck thinking state. Looking at the videos you submitted, its not actually stuck in a thinking state (as there is no thinking indicator). But rather, it stopped thinking, but there wasn't an acknowledgment to say what it decided to do. In this particular instance, a simple acknowledgement would have sufficed. To be also fixed in the backend. Will track with a separate issue.

For issue 3: Follow-up request while Concierge is thinking is not processed. This isn't actually limited to this flow and is an issue with Concierge handling multiple requests even in the main flow. When you start a concierge 1-on-1 dm and ask it a question, then while its thinking, ask another question, it'll only answer / action your first question. But overall, I agree this makes for a bad product experience so will make another separate issue to fix across the product (not just this flow).

Overall we shouldn't block on the above 3 issue as they are beyond the scope of this PR. Nevertheless, I will be addressing them separately in follow-ups.

huult

LGTM.

melvin-bot · 2026-07-23T14:35:01Z

@cristipaval Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

melvin-bot · 2026-07-23T14:35:03Z

🎯 @huult, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/651801.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

inimaga · 2026-07-23T15:25:51Z

Trackings for backend follow-up issues created here:

huult · 2026-07-23T16:00:57Z

Thank you

OSBotify · 2026-07-23T21:25:42Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-07-23T21:27:58Z

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

github-actions · 2026-07-23T21:33:36Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7c23e695abb-32d40ea-23b466ebbefac22583100d90eb012445580f87dd/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7c23e69-32d40ea-71c569c65b722a44b7bd64835998c961dad890ea/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-07-23T23:05:04Z

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.4.44-0 🚀

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

MelvinBot · 2026-07-23T23:08:40Z

Help site review — no docs changes required

I reviewed the changes in this PR against App/docs/articles and applied the naming/authoring/template guidelines. No help site updates are needed, so I did not open a draft docs PR.

Why: This PR is internal UI plumbing — it lets non-chat (expense) reports mount the AgentZero status gate when the server writes a processing-indicator NVP, so parent multi-expense reports can render the server-driven Concierge "thinking"/status bubble. That indicator is transient, in-product visual feedback; it introduces no new user-facing feature, setting, tab, label, button, or workflow that the help site documents.

The actual user-facing capability this supports — editing/updating an expense by chatting with Concierge on a report — is already documented and accurate in Expense-Assistant.md, including the "Modify expenses → Edit the description" flow and the "In a report chat" context-resolution note. Nothing in that article needs to change for this PR.

If a future PR adds a documented behavior change (e.g., a new Concierge capability, a user-visible setting, or copy the help site references), flag it and I'll draft the docs update then.

@inimaga, please confirm you agree no help site changes are needed here. If you'd still like a docs PR created (or believe an article should call out this behavior), reply with the details and I'll open one.

melvin-bot · 2026-07-27T18:45:36Z

🤖 Payment issue created: #97137

OSBotify · 2026-07-27T18:47:12Z

🚀 Deployed to production by https://github.com/marcaaron in version: 9.4.44-6 🚀

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

Bundle Size Analysis (Sentry):

Android

inimaga added 2 commits July 13, 2026 14:54

Render server driven thinking indicator status

019aff5

Add test coverage

9090c51

melvin-bot Bot assigned inimaga Jul 13, 2026

inimaga added 5 commits July 13, 2026 15:50

Merge branch 'main' into issa/Render-server-driven-AZ-status-on-expen…

d29e300

…se-reports

Extract tail indicator

e3a321e

Show indicator in tables

459d623

Wrap search report view

a0d18ff

Pad table tail

42614c0

inimaga changed the title ~~[Hold Auth#22870][Hold Web-E#54486] Render server-driven AZ status on expense reports~~ Render server-driven AZ status on expense reports Jul 17, 2026

Merge remote-tracking branch 'origin/main' into issa/Render-server-dr…

056f875

…iven-AZ-status-on-expense-reports # Conflicts: # src/pages/inbox/report/ReportActionsListTailIndicator.tsx # tests/unit/ReportActionsListTailIndicatorTest.tsx

inimaga marked this pull request as ready for review July 17, 2026 11:13

inimaga requested review from a team as code owners July 17, 2026 11:13

melvin-bot Bot requested a review from huult July 17, 2026 11:13

melvin-bot Bot requested review from joekaufmanexpensify and removed request for a team July 17, 2026 11:13

chatgpt-codex-connector Bot reviewed Jul 17, 2026

View reviewed changes

Comment thread src/components/MoneyRequestReportView/MoneyRequestReportActionsList.tsx

joekaufmanexpensify previously approved these changes Jul 17, 2026

View reviewed changes

Merge branch 'main' into issa/Render-server-driven-AZ-status-on-expen…

d8c1cab

…se-reports

Fix money request tail indicator autoscroll

f0aef5c

inimaga dismissed joekaufmanexpensify’s stale review via f0aef5c July 20, 2026 12:32

This comment has been minimized.

Sign in to view

huult approved these changes Jul 23, 2026

View reviewed changes

melvin-bot Bot requested a review from cristipaval July 23, 2026 14:34

melvin-bot Bot changed the title ~~Render server-driven AZ status on expense reports~~ [Payment due @huult] Render server-driven AZ status on expense reports Jul 23, 2026

cristipaval approved these changes Jul 23, 2026

View reviewed changes

cristipaval merged commit 7c23e69 into main Jul 23, 2026
44 of 47 checks passed

cristipaval deleted the issa/Render-server-driven-AZ-status-on-expense-reports branch July 23, 2026 21:17

OSBotify mentioned this pull request Jul 23, 2026

Deploy Checklist: New Expensify 2026-07-23 #96914

Closed

51 tasks

MelvinBot mentioned this pull request Jul 24, 2026

[Due for payment 2026-08-03] Chat-While inviting user in expense report, concierge thinking is briefly shown and disappear #96979

Closed

7 tasks

yuwenmemon mentioned this pull request Jul 24, 2026

[CP Staging] Revert server-driven AZ status on expense reports #97003

Merged

37 tasks

MelvinBot mentioned this pull request Jul 27, 2026

[Payment due @mkhutornyi] Sage Intacct: Default vendor as navigable arrow row with updated copy #97016

Merged

40 tasks

melvin-bot Bot mentioned this pull request Jul 27, 2026

[Due for payment 2026-08-03] Payment issue for E/App PR#95959 #97137

Closed

quinthar added the #ai label Aug 11, 2026

Conversation

inimaga commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Manual tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Jul 17, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

huult commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

joekaufmanexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

huult commented Jul 20, 2026

Uh oh!

inimaga commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Jul 20, 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!

github-actions Bot commented Jul 20, 2026

Uh oh!

This comment has been minimized.

huult commented Jul 21, 2026

Uh oh!

huult commented Jul 21, 2026

Reproduction Steps

Uh oh!

huult commented Jul 21, 2026

Uh oh!

huult commented Jul 21, 2026

Current behavior

Expected behavior

Uh oh!

huult commented Jul 23, 2026

Uh oh!

inimaga commented Jul 23, 2026

Uh oh!

huult left a comment

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Jul 23, 2026

Uh oh!

melvin-bot Bot commented Jul 23, 2026

Uh oh!

inimaga commented Jul 23, 2026

Uh oh!

huult commented Jul 23, 2026

Uh oh!

Uh oh!

OSBotify commented Jul 23, 2026

Uh oh!

github-actions Bot commented Jul 23, 2026

Uh oh!

github-actions Bot commented Jul 23, 2026

Uh oh!

OSBotify commented Jul 23, 2026

Uh oh!

MelvinBot commented Jul 23, 2026

Help site review — no docs changes required

Uh oh!

melvin-bot Bot commented Jul 27, 2026

Uh oh!

OSBotify commented Jul 27, 2026

inimaga commented Jul 13, 2026 •

edited

Loading

huult commented Jul 17, 2026 •

edited

Loading

inimaga commented Jul 20, 2026 •

edited

Loading

codecov Bot commented Jul 20, 2026 •

edited by github-actions Bot

Loading