[CP staging] Surface AgentZero request ID in report action context menu by jasperhuangg · Pull Request #94221 · Expensify/App

jasperhuangg · 2026-06-22T21:53:17Z

Explanation of Change

Adds a staging/dev-only report-action context menu item, "Copy AgentZero request ID", that copies the agentZeroRequestID stamped on AgentZero comments (from the companion Auth PR) so internal employees can trace an AI reply. It mirrors the existing non-prod "Copy Onyx data" item and reads the ID from the comment's originalMessage.

Fixed Issues

$
For https://github.com/Expensify/Expensify/issues/651179
PROPOSAL:

Tests

Requires the companion Auth PR deployed so AgentZero comments carry agentZeroRequestID.

Run the app in a non-production environment (dev or staging).
Open a chat where AgentZero/Concierge has posted a reply.
Right-click (or long-press) the AgentZero message to open the context menu.
Verify a "Copy AgentZero request ID" item appears.
Click it, then paste into a text field and verify the pasted value is the request ID.
Right-click a normal user message and verify the item does NOT appear.
On a production build, verify the item never appears.

Verify that no errors appear in the JS console

Offline tests

Go offline.
Right-click an AgentZero message and click "Copy AgentZero request ID".
Verify the ID copies from already-synced Onyx data with no errors (no network required).

QA Steps

On staging, open a chat where Concierge/AgentZero has replied.
Right-click (or long-press) the AgentZero message.
Verify "Copy AgentZero request ID" appears and copies the ID to the clipboard.
Right-click a normal user message and verify the item does NOT appear.

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

OSBotify · 2026-06-22T21:54:51Z

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff

diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 1f2c159aad3..232d3e37294 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -840,7 +840,7 @@ const translations: TranslationDeepObject<typeof en> = {
         joinThread: 'Rejoindre la discussion',
         leaveThread: 'Quitter la discussion',
         copyOnyxData: 'Copier les données Onyx',
-        copyAgentZeroRequestID: "Copier l'ID de requête AgentZero",
+        copyAgentZeroRequestID: 'Copier l’ID de demande AgentZero',
         flagAsOffensive: 'Signaler comme offensant',
         menu: 'Menu',
     },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 6bffb040d3a..bb83bbbf6ed 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -837,7 +837,7 @@ const translations: TranslationDeepObject<typeof en> = {
         joinThread: 'Entrar na conversa',
         leaveThread: 'Sair da conversa',
         copyOnyxData: 'Copiar dados do Onyx',
-        copyAgentZeroRequestID: 'Copiar ID de solicitação do AgentZero',
+        copyAgentZeroRequestID: 'Copiar ID da solicitação do AgentZero',
         flagAsOffensive: 'Sinalizar como ofensivo',
         menu: 'Menu',
     },

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

codecov · 2026-06-22T21:57:39Z

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 Δ
src/CONST/index.ts	`94.11% <ø> (+0.27%)`	⬆️
...report/ContextMenu/BaseReportActionContextMenu.tsx	`85.80% <100.00%> (+0.26%)`	⬆️
...es/inbox/report/ContextMenu/ContextMenuActions.tsx	`44.23% <14.28%> (-0.35%)`	⬇️
... and 543 files with indirect coverage changes

melvin-bot · 2026-06-23T18:30:36Z

@Valforte 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]

jasperhuangg · 2026-06-23T18:39:31Z

No product review is needed, as this is strictly a staging and dev change that affects only employees.

Gate the copy AgentZero request ID context-menu action to dev and staging only instead of all non-production environments. Co-authored-by: Cursor <cursoragent@cursor.com>

yuwenmemon · 2026-06-25T04:40:12Z

+        successIcon: 'Checkmark',
+        shouldShow: ({type, reportAction, isDevelopment, isStaging}) =>
+            type === CONST.CONTEXT_MENU_TYPES.REPORT_ACTION &&
+            (isDevelopment || isStaging) &&


Why wouldn't we do !isProduction like above with copyOnyxData? This keeps it consistent with that other very similar button.

(Jasper's Agent) Good catch, updated to use !isProduction for consistency.

…check

yuwenmemon · 2026-06-26T05:04:07Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

OSBotify · 2026-06-29T17:37: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-06-29T17:40:06Z

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

github-actions · 2026-06-29T17:47:06Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-4aa01635a65-0f1cc02-33452aa9981e722cc91afcaefeadb33f5bc5dcaa/index.html	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed

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

👀 View the workflow run that generated this build 👀

…-menu Surface AgentZero request ID in report action context menu (cherry picked from commit 4aa0163) (cherry-picked to staging by blimpich)

OSBotify · 2026-06-29T18:50:08Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.4.22-4 🚀

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

OSBotify · 2026-06-29T19:37:09Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.4.24-0 🚀

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

OSBotify · 2026-06-30T11:50:02Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.4.24-0 🚀

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

Bundle Size Analysis (Sentry):

Android

OSBotify · 2026-06-30T12:06:22Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.4.25-0 🚀

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

OSBotify · 2026-06-30T12:33:00Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.4.24-0 🚀

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

OSBotify · 2026-07-01T19:45:09Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.4.25-2 🚀

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

Bundle Size Analysis (Sentry):

Android

feat(report): surface AgentZero request ID in context menu

b4a823e

melvin-bot Bot assigned jasperhuangg Jun 22, 2026

jasperhuangg changed the title ~~Surface AgentZero request ID in report action context menu~~ [HOLD Auth#22430] Surface AgentZero request ID in report action context menu Jun 22, 2026

jasperhuangg requested a review from yuwenmemon June 23, 2026 18:29

jasperhuangg marked this pull request as ready for review June 23, 2026 18:30

jasperhuangg requested review from a team as code owners June 23, 2026 18:30

melvin-bot Bot requested review from Valforte and joekaufmanexpensify and removed request for a team June 23, 2026 18:30

melvin-bot Bot removed the request for review from a team June 23, 2026 18:30

jasperhuangg removed request for Valforte and joekaufmanexpensify June 23, 2026 18:39

fix(report): restrict AgentZero request ID action to dev/staging

ca60b6a

Gate the copy AgentZero request ID context-menu action to dev and staging only instead of all non-production environments. Co-authored-by: Cursor <cursoragent@cursor.com>

jasperhuangg changed the title ~~[HOLD Auth#22430] Surface AgentZero request ID in report action context menu~~ Surface AgentZero request ID in report action context menu Jun 25, 2026

yuwenmemon requested changes Jun 25, 2026

View reviewed changes

fix(report): use !isProduction for copyAgentZeroRequestID visibility …

446fe05

…check

yuwenmemon approved these changes Jun 26, 2026

View reviewed changes

jasperhuangg merged commit 4aa0163 into main Jun 29, 2026
39 of 40 checks passed

jasperhuangg deleted the jasper/az-request-id-context-menu branch June 29, 2026 17:30

jasperhuangg changed the title ~~Surface AgentZero request ID in report action context menu~~ [CP staging] Surface AgentZero request ID in report action context menu Jun 29, 2026

jasperhuangg changed the title ~~[CP staging] Surface AgentZero request ID in report action context menu~~ Surface AgentZero request ID in report action context menu Jun 29, 2026

jasperhuangg changed the title ~~Surface AgentZero request ID in report action context menu~~ [CP staging] Surface AgentZero request ID in report action context menu Jun 29, 2026

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Jun 29, 2026

OSBotify mentioned this pull request Jun 29, 2026

Deploy Checklist: New Expensify 2026-06-29 #94832

Closed

36 tasks done

Conversation

jasperhuangg commented Jun 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

OSBotify commented Jun 22, 2026

🦜 Polyglot Parrot! 🦜

Uh oh!

codecov Bot commented Jun 22, 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!

melvin-bot Bot commented Jun 23, 2026

Uh oh!

jasperhuangg commented Jun 23, 2026

Uh oh!

yuwenmemon Jun 25, 2026

Choose a reason for hiding this comment

Uh oh!

jasperhuangg Jun 25, 2026

Choose a reason for hiding this comment

Uh oh!

jasperhuangg Jun 25, 2026

Choose a reason for hiding this comment

Uh oh!

yuwenmemon commented Jun 26, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

github-actions Bot commented Jun 29, 2026

Uh oh!

github-actions Bot commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 29, 2026

Uh oh!

OSBotify commented Jun 30, 2026

Uh oh!

OSBotify commented Jun 30, 2026

Uh oh!

OSBotify commented Jun 30, 2026

Uh oh!

OSBotify commented Jul 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

jasperhuangg commented Jun 22, 2026 •

edited

Loading

codecov Bot commented Jun 22, 2026 •

edited by github-actions Bot

Loading