Agents - AI prompt Save button is not disabled in offline mode

[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: 9.3.89-1
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: #90823
Email or phone of affected tester (no customers): applausetester+sjdjois2jd@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other

Action Performed:

Precondition:

• Log in with Expensifail account.
• Create an agent on Account > Agents.

1. Go to staging.new.expensify.com
2. Go to Account > Profile.
3. Open account switcher.
4. Select the agent.
5. Go offline.
6. Edit AI prompt on Profile and click Save.

Expected Result:

AI prompt Save button should be disabled in offline mode.

Actual Result:

AI prompt Save button is not disabled in offline mode and it loads infinitely when clicked.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7165826_1780006710486.7.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @NicolasBonet

[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/e8c2e529a6aa507caa89ea93cdef3688fc10cc32fdba3631ef67494f9c074d1c

[melvin-bot]

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

[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]

Proposal

What is the root cause of that problem?

The Save button in the AI prompt section on the agent's Profile page does not factor in offline state. In src/pages/settings/Profile/AgentAIPromptSection.tsx:202, the button's isDisabled is only hasHtmlTag || isSaving, with no isOffline check.

When the user is offline and clicks Save, updateAgentPrompt runs and its optimistic data sets pendingAction: CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE on the SHARED_NVP_AGENT_PROMPT_${accountID} Onyx record. Because isSaving = agentPrompt?.pendingAction === UPDATE and the Button receives isLoading={isSaving}, the spinner stays on indefinitely while offline — the API call cannot resolve, so pendingAction is never cleared until reconnection.

Note that the standalone EditPromptPage.tsx is not affected because it uses FormProvider (whose default offline behavior disables submission unless enabledWhenOffline is set).

What changes do you think we should make in order to solve the problem?

In src/pages/settings/Profile/AgentAIPromptSection.tsx:

1. Import and call useNetwork() to get isOffline.
2. Add isOffline to the Save button's isDisabled so the button is disabled when offline, matching the expected behavior in the report.
3. Also guard isLoading (e.g. isLoading={isSaving && !isOffline}) so a stale pendingAction from a prior offline tap does not keep the button spinning if the user navigates back while still offline.

Optionally, early-return from handleSave when isOffline to defend against any path that re-enables the button.

What alternative solutions did you explore? (Optional)

• Convert to FormProvider with enabledWhenOffline (the pattern used by EditPromptPage) so the write is queued silently. Rejected because the issue's expected result explicitly asks for the Save button to be disabled offline, and this section lives inline on the Profile page rather than as a dedicated submit form.
• Clear pendingAction immediately when offline. Rejected — pendingAction is the signal OfflineWithFeedback uses to render the queued-state styling; clearing it would break the offline indicator and pending-state visuals shown around the TextInput.

Related PR

Introduced in PR #90823 (feat: add AI prompt section to profile settings for agent accounts, merged 2026-05-27).

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/92032) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.