feat: Implement "Explain" button for report actions with Concierge reasoning #78487

samranahm · 2025-12-26T23:39:10Z

Explanation of Change

Fixed Issues

$ #78464
PROPOSAL: #78464 (comment)

Tests

Create an expense in the workspace chat.
Open the expense report and trigger Concierge with "Change Category to Travel."
Once Concierge replies, right-click or long-press on the Concierge message and click Explain.
Verify that a new thread is created with the Concierge message, and a new message from the user is sent:

Please explain this to me.

Change the language in preferences, repeat the steps, and verify that the user message appears in the selected language.

Verify that no errors appear in the JS console

Offline tests

Same as test

QA Steps

Same as test
// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

PR Author Checklist

Uploaded videos of Android Native and MacOs Chrome, will upload remaining platform videos once BE changes deployed.

Screenshots/Videos

Android: Native

Android.Native.mp4

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS.Chrome.mp4

…expenses

melvin-bot · 2025-12-26T23:39:15Z

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

Look at the code and make sure there are no malicious changes.
Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

Copilot

Pull request overview

This PR implements an "Explain" button in the context menu for report actions with Concierge reasoning. When users right-click or long-press on specific Concierge messages (MODIFIED_EXPENSE or AUTO_SUBMITTED actions), they can select "Explain" to create a thread with an automated user message asking for clarification.

Key Changes:

Added reasoning field to OriginalMessageModifiedExpense type to store Concierge's explanation
Created new context menu action with "Explain" button that triggers thread creation
Implemented explain function to create/navigate to thread and post localized message

Reviewed changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/types/onyx/OriginalMessage.ts	Adds optional `reasoning` field to store Concierge's explanation for expense modifications
src/pages/home/report/ContextMenu/ContextMenuActions.tsx	Implements new "Explain" context menu action with validation logic and unused imports
src/pages/home/report/ContextMenu/BaseReportActionContextMenu.tsx	Adds QuestionMark icon support for the explain action
src/libs/actions/Report.ts	Implements `explain` function and modifies `navigateToAndOpenChildReport` to return report ID
src/languages/*.ts	Adds localized translations for "explain" and "explainMessage" across 9 languages
src/CONST/index.ts	Adds AUTO_SUBMITTED action type constant and EXPLAIN sentry label

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/pages/home/report/ContextMenu/ContextMenuActions.tsx

codecov · 2025-12-26T23:47:35Z

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	`83.47% <ø> (ø)`
...report/ContextMenu/BaseReportActionContextMenu.tsx	`0.00% <0.00%> (ø)`
...ges/home/report/ContextMenu/ContextMenuActions.tsx	`0.75% <0.00%> (-0.03%)`	⬇️
src/libs/actions/Report.ts	`54.40% <0.00%> (-0.31%)`	⬇️
... and 7 files with indirect coverage changes

eh2077 · 2025-12-27T12:01:01Z

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 there are no new alerts related to the canBeMissing param for useOnyx
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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
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)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
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.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
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

eh2077 · 2025-12-27T12:04:11Z

@samranahm is the ts check failure related to this PR?

eh2077 · 2025-12-27T13:43:19Z

@samranahm I'm not able to test the feature following the test steps, am I missing something?

Screen.Recording.2025-12-27.at.9.41.09.PM.mov

eh2077 · 2025-12-27T12:18:09Z

src/pages/home/report/ContextMenu/ContextMenuActions.tsx

+            const isExplainableAction = [CONST.REPORT.ACTIONS.TYPE.MODIFIED_EXPENSE, CONST.REPORT.ACTIONS.TYPE.AUTO_SUBMITTED].some((actionType) => reportAction.actionName === actionType);
+            if (!isExplainableAction) {
+                return false;
+            }


I don't think this is correct according to #78464 (comment)

For this feature we need to implement an "Explain" button in the frontend for any report action that has a reasoning field.

This button will exist in the right-click menu for now

This one actually need more clarification but currently I implement this

To start it will be visible on the following report actions:

Concierge auto-categorized something using AI

Concierge auto-submitted a report

src/libs/actions/Report.ts

eh2077 · 2025-12-27T12:52:29Z

src/libs/actions/Report.ts

+    // eslint-disable-next-line @typescript-eslint/no-deprecated
+    InteractionManager.runAfterInteractions(() => {


Can we avoid wrapping with runAfterInteractions as it's deprecated?

This causes the issue because the comment is posted immediately, before the thread is created and we navigates to it and it return an error.

src/libs/actions/Report.ts

samranahm · 2025-12-27T14:02:58Z

I'm not able to test the feature following the test steps

@eh2077 We are waiting for BE PR to deployed. #78464 (comment)

…n keys

samranahm · 2025-12-27T19:38:42Z

@eh2077 Please take a look.

samranahm added 4 commits December 27, 2025 04:00

Add "Explain" button to context menu for modified and auto-submitted …

00ba7a6

…expenses

Add explain function to create explanation threads for report actions

94994df

Add auto-submitted action and extend OriginalMessage type

bb9af45

Add translation for button and message in all locals

6baa484

Copilot AI review requested due to automatic review settings December 26, 2025 23:39

samranahm requested review from a team as code owners December 26, 2025 23:39

melvin-bot bot assigned samranahm Dec 26, 2025

melvin-bot bot requested review from JmillsExpensify, eh2077, flaviadefaria, heyjennahay, joekaufmanexpensify, marcaaron and trjExpensify December 26, 2025 23:39

Copilot started reviewing on behalf of samranahm December 26, 2025 23:39 View session

Copilot AI reviewed Dec 26, 2025

View reviewed changes

src/pages/home/report/ContextMenu/ContextMenuActions.tsx Outdated Show resolved Hide resolved

src/pages/home/report/ContextMenu/ContextMenuActions.tsx Outdated Show resolved Hide resolved

src/pages/home/report/ContextMenu/ContextMenuActions.tsx Outdated Show resolved Hide resolved

fix: lint

b15c207

samranahm mentioned this pull request Dec 27, 2025

[$250] [Explain feature] Add support for the "Explain" button in the front end #78464

Open

Merge branch 'Expensify:main' into 78464/add-explain-button

f500a4b

eh2077 reviewed Dec 27, 2025

View reviewed changes

samranahm added 3 commits December 27, 2025 21:37

extract thread creation into helper

0541ce0

add current user personal details to context menu actions

be58bf7

refactor: update type definition for OriginalMessage to handle unknow…

1f889e5

…n keys

		// eslint-disable-next-line @typescript-eslint/no-deprecated
		InteractionManager.runAfterInteractions(() => {

feat: Implement "Explain" button for report actions with Concierge reasoning #78487

Are you sure you want to change the base?

feat: Implement "Explain" button for report actions with Concierge reasoning #78487

Conversation

samranahm commented Dec 26, 2025 • 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!

melvin-bot bot commented Dec 26, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

codecov bot commented Dec 26, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

eh2077 commented Dec 27, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

eh2077 commented Dec 27, 2025

Uh oh!

eh2077 commented Dec 27, 2025

Uh oh!

eh2077 Dec 27, 2025

Choose a reason for hiding this comment

Uh oh!

samranahm Dec 27, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

eh2077 Dec 27, 2025

Choose a reason for hiding this comment

Uh oh!

samranahm Dec 27, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

samranahm commented Dec 27, 2025

Uh oh!

samranahm commented Dec 27, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

samranahm commented Dec 26, 2025 •

edited

Loading

codecov bot commented Dec 26, 2025 •

edited by github-actions bot

Loading