[s77rt]

This is based on #103788 so let's merge that one first

Explanation of Change

Added option to create company agents in Workspace > Agents page

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/681638
PROPOSAL:

Tests

• Have a workspace

1. Go to Workspace > Agents
2. Click on New agent and create an agent
3. Verify the agent is created
4. Verify the agent is added to the workspace with the chosen role
5. Go to Settings > Agents
6. Verify the agent is listed there too
7. Verify the agent owner is either the policy account or domain account (and not your account)

Screen.Recording.2026-10-19.at.2.14.00.PM.mov

• Verify that no errors appear in the JS console

Offline tests

Same as Tests except steps 4 and 7

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 verified any copy / text that was added to the app 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 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 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.
• If the PR adds or modifies the UI:
  • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
  • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
  • I verified all new/changed elements have meaningful accessible names and roles.
  • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
• 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[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 Δ
...s/Search/SearchRouter/useNavigationSuggestions.tsx	93.39% <ø> (ø)
src/hooks/useWorkspaceMembers.ts	89.28% <ø> (ø)
src/libs/API/types.ts	100.00% <ø> (ø)
src/libs/actions/Agent.ts	74.00% <100.00%> (+1.95%)	⬆️
src/pages/settings/Agents/DynamicNewAgentPage.tsx	98.70% <100.00%> (+0.09%)	⬆️
src/pages/workspace/WorkspaceInitialPage.tsx	86.36% <100.00%> (+0.12%)	⬆️
src/pages/workspace/getWorkspaceMenuItems.ts	98.50% <100.00%> (+0.01%)	⬆️
src/types/form/AddAgentForm.ts	100.00% <ø> (ø)
...ppNavigator/Navigators/WorkspaceSplitNavigator.tsx	7.69% <0.00%> (ø)
src/pages/settings/Agents/DynamicAddAgentPage.tsx	91.96% <95.55%> (-0.67%)	⬇️
... and 3 more
... and 61 files with indirect coverage changes

[melvin-bot]

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-13T04:57:32.739598Z	1c1378f	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[melvin-bot]

🎯 @linhvovan29546, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/681638.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

[puneetlath]

LGTM. Should we have the design team review as well?

[s77rt]

cc @Expensify/design

[s77rt]

@puneetlath Let's actually merge this. I will handle any reviews here in the next PR

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

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

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-778b5af-f8df561-c33da868d6f492e8b21d9adeda665a1a939e4c0d/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-778b5af-f8df561-2da73a2ed1b3fba7d1c2f595449b33acdcc0806d/index.html

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

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.5.16-0 🚀

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

[MelvinBot]

No help site update needed. The only new user-facing feature is creating company agents from Workspace > Agents, and only users with the companyAgents beta can see it. The Agents menu item is gated in getWorkspaceMenuItems.ts:260, and the page is blocked without the beta in WorkspaceAgentsPage.tsx:133. Personal agents in Settings > Agents work the same as before, so no existing article is now wrong. You can revisit the docs when the companyAgents beta is removed.

---

view run

[mitarachim]

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

[OSBotify]

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.5.18-0 🚀

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

[MelvinBot]

No help site update needed: the new Workspace > Agents page where you create company agents only appears behind the COMPANY_AGENTS beta (isBetaEnabled(CONST.BETAS.COMPANY_AGENTS) in getWorkspaceMenuItems.ts and WorkspaceAgentsPage.tsx), and the personal agent flow in Settings > Agents works the same for users as before.

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.5.18-1 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[melvin-bot]

🤖 Payment issue created: #104871