Fix - Add react-native-live-markdown to the Custom Agent Instructions input

[FitseTLT]

Explanation of Change

Agent instructions are stored and rendered as Markdown everywhere they're displayed, but the inputs used to author them rendered as plain text with no live formatting. All five prompt inputs pass InputComponent={TextInput} without a type, so BaseTextInput falls back to its default implementation instead of RNMarkdownTextInput — the @expensify/react-native-live-markdown component the chat composer already uses.

This adds type="markdown" to the prompt input on all five surfaces (create agent, edit agent instructions, Profile → AI Prompt, add agent rule, edit agent rule), along with excludedMarkdownStyles={['mentionReport']} — on these surfaces @email renders as a mention but #room does not, since a room mention can't resolve outside a report context, so without the exclusion the input would live-style #room as a mention that never renders once saved. The two rule pages and the AI Prompt section submit on Cmd/Ctrl+Enter through onKeyPress, and the markdown input inserts a line break for any Enter keydown that isn't already default-prevented, so those handlers now call event.preventDefault() before submitting. The agent-name field and the rule suggestions search box are left as plain inputs.

Fixed Issues

$ #96902
PROPOSAL: #96902 (comment)

Tests

Pre-requisite: a workspace with Rules enabled (Workspace > More features).

Two checks are reused across the inputs below:

Markdown check — type *bold*, _italic_, # heading, `code` and ~ strike-through~, and verify the formatting renders live as you type, matching the chat composer. Then type #room and verify it stays plain text, and type @user@example.com and verify it is styled as a mention.

1. Account > Agents > Create agent → Instructions — run the Markdown check.
2. Account > Agents > (any existing agent) > Instructions — run the Markdown check.
3. Account > Profile > AI Prompt (signed in as the agent) — run the Markdown check.
4. Workspace > Rules > Agents > Add rule > Write your own — run the Markdown check
5. Workspace > Rules > Agents > select any existing rule— run the Markdown check

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • 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 followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

2026-08-05.15-59-02.mp4

Android: mWeb Chrome

2026-08-05.15-42-27.mp4

iOS: Native

2026-08-05.17-21-19.mp4

iOS: mWeb Safari

2026-08-05.15-39-43.mp4

MacOS: Chrome / Safari

2026-08-05.15-35-50.mp4

[melvin-bot]

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

[FitseTLT]

@shawnborton @roryabraham I see that we are missing the submit via Cmd+Enter in only AddAgentPage and I think it is an inconsistency as it exists in all other 4 ai input pages. I want you to confirm if I am right then I will raise another PR according to Contributors+ Process Doc (C+)

bang.mp4

[codecov]

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 Δ
...rc/pages/settings/Agents/Fields/EditPromptPage.tsx	71.42% <100.00%> (+0.69%)	⬆️
...rc/pages/settings/Profile/AgentAIPromptSection.tsx	82.52% <100.00%> (+0.17%)	⬆️
...orkspace/rules/AgentRules/AddAgentRuleWriteTab.tsx	0.00% <0.00%> (ø)
...s/workspace/rules/AgentRules/EditAgentRulePage.tsx	0.00% <0.00%> (ø)
src/pages/settings/Agents/AddAgentPage.tsx	90.12% <50.00%> (-3.21%)	⬇️
... and 44 files with indirect coverage changes

[shawnborton]

Makes sense to me 👍

[Pujan92]

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

Screen.Recording.2026-08-06.at.23.21.32.mov

Screen.Recording.2026-08-06.at.23.17.33.mov

[FitseTLT]

Makes sense to me 👍

Added it here

[joekaufmanexpensify]

Good for product.

[Pujan92]

LGTM!

[github-actions]

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

[OSBotify]

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

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6695479de5d-f1b9fa4-6b2829415337a92806892cf33efd24ac089d691a/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6695479-f1b9fa4-b77f4d9dc668a6636d030619bc06bc66f31d46c5/index.html

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

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.52-0 🚀

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

[MelvinBot]

Help site review: no changes required

I reviewed this PR against the AI agents help articles under docs/articles and no help site changes are required.

Why: This is a presentation-layer UX change. It adds type="markdown" to the five agent instruction/prompt/rule inputs so they render formatting live as you type (matching the chat composer), plus the Cmd/Ctrl+Enter submit handling that comes with it. It does not add or change any documented feature, workflow, setting, tab, or button.

Importantly, per the PR description, agent instructions were already "stored and rendered as Markdown everywhere they're displayed." Markdown support in instructions already existed at the render layer — this PR only makes the authoring input show the live preview. So a user's ability to accomplish anything is unchanged; only the input's visual feedback is.

Articles checked

• Create-and-Use-Custom-Agents.md — "How to write instructions for an agent" describes instructions as natural language; makes no claim about input formatting that this PR contradicts.
• Create-Agent-Rules.md — covers creating/editing rules; no input-formatting behavior documented.
• How-to-Write-Agent-Rules.md — prompt-writing best practices; unaffected.

None describe the live-preview behavior of the input field, and none make a statement this change invalidates.

No draft docs PR was created since there is nothing to document.

@FitseTLT, if you'd still like a help article to explicitly mention that instructions/rules support Markdown formatting (now that the input previews it live), let me know and I'll draft the docs PR.

[lanitochka17]

Deploy Blocker #98325 was identified to be related to this PR.

[OSBotify]

🚀 Deployed to production by https://github.com/roryabraham in version: 9.4.52-11 🚀

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

Bundle Size Analysis (Sentry):

• Android