Concierge - Explain button missing from action menu

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.4.9-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91863
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11/ Chrome
App Component: Other

Action Performed:

1. Sign in to staging.new.expensify.com
2. Go to Concierge chat
3. Enter a message so that it trigger "reasoning" (eg. How do I know the current status of my expense report?)
4. Right click (hold on mobile) on AI response message

Expected Result:

Explain button is displayed among other in the action menu

Actual Result:

No explain button is displayed in the action menu

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7182819_1781643817616.bandicam_2026-06-16_23-55-17-268.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7182819

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/915bbc7073e5b8fd0356ea81fcae406fefb1cb6ddf028328f3a832f8e0cbfda1

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91863

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Issue Analysis

Root Cause: The "Explain" context menu item only renders when the AI response's originalMessage.reasoning field is truthy. On staging that field is empty, so the gate returns false and the item is hidden. No App code populates reasoning on a report action — it must arrive from the backend on the persisted Concierge comment. This points to a backend issue (the AI response is not being persisted with a reasoning field), not an App bug.

The Explain item's shouldShow is gated solely on hasReasoning(reportAction), which checks originalMessage.reasoning. The live "thinking" reasoning that streams in over Pusher is stored only in the transient AgentZeroReasoningStore (used for the in-progress indicator) and is cleared when the response completes — it is never written into the finalized report action. So the Explain button depends entirely on the backend including reasoning in the comment's originalMessage.

This requires a change outside the App repo. Please escalate to an internal engineer to verify why the staging backend isn't persisting reasoning on the Concierge AI response's originalMessage (e.g. the AI/AgentZero pipeline, or a backend beta/flag gating the field on staging).

Re: the deploy-blocker assignment to PR #91863 — that PR is very likely not the cause. It touched the Explain code, but only the onPress handlers (swapping in getParticipantsPersonalDetails) and unrelated group-chat creation logic. It did not change the shouldShow/hasReasoning gate that controls visibility. Since other context-menu items still render, this is the visibility gate returning false, which #91863 doesn't affect.

Investigation details & alternatives considered

• Visibility gate: ContextMenuActions.tsx:502-507 → returns hasReasoning(reportAction).
• Gate implementation: ReportActionsUtils.ts:4651-4654 → 'reasoning' in originalMessage && !!originalMessage.reasoning.
• No client-side writer: A repo-wide search for reasoning writes found only AgentZeroReasoningStore.addReasoning(...) (transient, keyed by reportID+agent, cleared on completion) and the Pusher event type. Nothing merges reasoning into a report action's originalMessage.
• Alternative considered — (Part 3) Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts #91863 regression: Ruled out. Its diff to ContextMenuActions.tsx and ReportActionItemMessageWithExplain.tsx only changes click handlers/personal-details; its Report/index.ts changes are group-chat creation, not the reasoning subscription.
• Alternative considered — beta gating: The App shouldShow does not check any beta, so if reasoning were present the item would show. If reasoning is gated behind a backend beta/flag on staging, that is still a backend-side concern.
• Confidence: Medium-High on the App-side analysis (clear code evidence). The backend-not-persisting-reasoning conclusion is the only remaining explanation given the App code, but final confirmation needs backend/log access I don't have.

---

Next Steps: This needs a backend engineer to confirm why reasoning is missing on the staging AI response. Reply with @MelvinBot <feedback> to refine this analysis.