Skip to content

feat: [89310] add agents flow#89547

Open
NicolasBonet wants to merge 14 commits intomainfrom
feat/89310-add-agents-flow
Open

feat: [89310] add agents flow#89547
NicolasBonet wants to merge 14 commits intomainfrom
feat/89310-add-agents-flow

Conversation

@NicolasBonet
Copy link
Copy Markdown
Contributor

@NicolasBonet NicolasBonet commented May 4, 2026

Explanation of Change

Implements the add agent form based on the design doc specification.

Fixed Issues

$ #89310
PROPOSAL: https://expensify.enterprise.slack.com/docs/T03SC9DTT/F0AKV1FPD41

Tests

  1. Click the New agent button
  2. Verify you see the modal with the default avatar and the ability to set name and prompt
  3. Verify name is defaulted to "bob's agent" assuming the creating user is named "bob"
  4. Verify name is editable
  5. Verify default prompt is present
  6. Verify prompt is editable
  7. Hit save
  8. Verify CreateAgent API is called in Network tab
  9. Verify that the new agent is optimistically shown on the Agents page with the provided details
  10. Click the New Agent button
  11. Refresh the page
  12. Check that the modal is shown and that the Agents list if shown beneath
  • Verify that no errors appear in the JS console

Offline tests

No special steps needed.

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 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 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 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.
  • 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
Screen.Recording.2026-05-04.at.4.31.14.PM.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-05-04.at.5.12.52.PM.mov

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@OSBotify

This comment has been minimized.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 4, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 92.30% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/ROUTES.ts 17.29% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/AvatarButtonWithIcon.tsx 100.00% <100.00%> (ø)
src/components/Icon/DefaultBotAvatars.ts 100.00% <100.00%> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
src/libs/actions/Agent.ts 75.00% <100.00%> (+75.00%) ⬆️
... and 6 more
... and 8 files with indirect coverage changes

@NicolasBonet NicolasBonet changed the title Feat/89310 add agents flow feat: [89310] add agents flow May 4, 2026
@OSBotify

This comment has been minimized.

@NicolasBonet NicolasBonet force-pushed the feat/89310-add-agents-flow branch from 5247084 to 90149a3 Compare May 4, 2026 20:25
const defaultPrompt = translate('addAgentPage.defaultPrompt');
const illustrations = useMemoizedLazyIllustrations(['AiBot']);
const expensifyIcons = useMemoizedLazyExpensifyIcons(['Sync']);
const avatarStyle = [styles.avatarXLarge, styles.alignSelfCenter];
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This follows the format of ProfilePage.tsx

@NicolasBonet NicolasBonet marked this pull request as ready for review May 4, 2026 21:26
@NicolasBonet NicolasBonet requested review from a team as code owners May 4, 2026 21:26
@melvin-bot melvin-bot Bot requested review from bernhardoj and flaviadefaria and removed request for a team and flaviadefaria May 4, 2026 21:26
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 4, 2026

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

Comment on lines +1 to +10
import BotAvatarBlue from '@assets/images/avatars/bots/bot-avatar--blue.svg';
import BotAvatarGreen from '@assets/images/avatars/bots/bot-avatar--green.svg';
import BotAvatarIce from '@assets/images/avatars/bots/bot-avatar--ice.svg';
import BotAvatarPink from '@assets/images/avatars/bots/bot-avatar--pink.svg';
import BotAvatarTangerine from '@assets/images/avatars/bots/bot-avatar--tangerine.svg';
import BotAvatarYellow from '@assets/images/avatars/bots/bot-avatar--yellow.svg';

const botAvatars = [BotAvatarBlue, BotAvatarGreen, BotAvatarIce, BotAvatarPink, BotAvatarTangerine, BotAvatarYellow] as const;

export {BotAvatarBlue, BotAvatarGreen, BotAvatarIce, BotAvatarPink, BotAvatarTangerine, BotAvatarYellow, botAvatars};
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file follows the same format of DefaultAvatars.ts

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented May 4, 2026

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 7e519a52..f976d31f 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2736,13 +2736,13 @@ ${amount} für ${merchant} – ${date}`,
     },
     addAgentPage: {
         title: 'Neue Kontaktperson',
-        agentName: 'Name des Agenten',
+        agentName: 'Name der Ansprechperson',
         instructions: 'Eigene Anweisungen schreiben',
         createAgent: 'Agent erstellen',
-        switchAvatar: 'Avatar wechseln',
-        defaultAgentName: (displayName: string) => `Agent von ${displayName}`,
+        switchAvatar: 'Profilbild wechseln',
+        defaultAgentName: (displayName: string) => `Agent*in von ${displayName}`,
         defaultPrompt:
-            'Ausgaben für Glücksspiele, Kinobesuche oder andere offensichtlich nicht geschäftliche Zwecke ablehnen.\n\nDen Benutzer immer daran erinnern, ein Belegbild beizufügen, das das Trinkgeld deutlich zeigt.\n\nDen Bericht genehmigen, wenn er früheren Berichten desselben Benutzers sehr ähnelt.\n\nBerichte mit mehr als 500 $ an Reiseausgaben ablehnen.',
+            'Lehne Ausgaben ab, die für Glücksspiele, Kinobesuche oder andere offensichtlich nicht geschäftliche Zwecke sind.\n\nErinnere den:die Nutzer:in daran, immer ein Belegfoto beizufügen, auf dem das Trinkgeld klar erkennbar ist.\n\nGenehmige den Bericht, wenn er früheren Berichten derselben Person sehr ähnlich ist.\n\nLehne Berichte mit mehr als 500 $ an Reisekosten ab.',
     },
     expenseRulesPage: {
         title: 'Ausgabenregeln',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 54eebfe6..8e4b0aca 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2743,12 +2743,12 @@ ${amount} pour ${merchant} - ${date}`,
     addAgentPage: {
         title: 'Nouvel agent',
         agentName: 'Nom de l’agent',
-        instructions: 'Écrire des instructions personnalisées',
+        instructions: 'Rédiger des instructions personnalisées',
         createAgent: 'Créer un agent',
         switchAvatar: 'Changer d’avatar',
         defaultAgentName: (displayName: string) => `Agent de ${displayName}`,
         defaultPrompt:
-            'Rejeter les dépenses liées aux jeux d’argent, aux films ou à d’autres raisons manifestement non professionnelles.\n\nRappeler à l’utilisateur d’inclure toujours une image de reçu montrant clairement le pourboire.\n\nApprouver le rapport s’il est très similaire aux rapports précédents du même utilisateur.\n\nRejeter les rapports contenant plus de 500 $ en frais de déplacement.',
+            'Rejeter les dépenses liées aux jeux d’argent, aux films ou à d’autres motifs manifestement non professionnels.\n\nRappeler à l’utilisateur d’inclure systématiquement une image du reçu où le pourboire est clairement visible.\n\nApprouver le rapport s’il est très similaire aux rapports précédents du même utilisateur.\n\nRejeter les rapports contenant plus de 500 $ de frais de déplacement.',
     },
     expenseRulesPage: {
         title: 'Règles de dépenses',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index cd477def..3e6cd4fe 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2737,7 +2737,7 @@ ${amount} per ${merchant} - ${date}`,
         switchAvatar: 'Cambia avatar',
         defaultAgentName: (displayName: string) => `Agente di ${displayName}`,
         defaultPrompt:
-            "Rifiutare le spese per giochi d'azzardo, cinema o altri motivi evidentemente non aziendali.\n\nRicordare all'utente di includere sempre un'immagine della ricevuta che mostri chiaramente la mancia.\n\nApprovare il rapporto se è molto simile ai rapporti precedenti dello stesso utente.\n\nRifiutare i rapporti con più di 500 $ di spese di viaggio.",
+            'Rifiuta le spese relative a gioco d’azzardo, cinema o altri motivi chiaramente non legati all’attività.\n\nRicorda all’utente di includere sempre un’immagine della ricevuta in cui la mancia sia ben visibile.\n\nApprova il report se è molto simile ai report precedenti dello stesso utente.\n\nRifiuta i report con più di 500 $ di spese di viaggio.',
     },
     expenseRulesPage: {
         title: 'Regole spese',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 52b0e8b4..9eef33fb 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -2703,14 +2703,14 @@ ${date} の ${merchant} への ${amount}`,
         emptyAgents: {title: 'エージェントは作成されていません', subtitle: '手作業はやめて、代わりにエージェントに指示を出して、時間を大幅に節約しましょう。'},
     },
     addAgentPage: {
-        title: '新しい担当者',
-        agentName: '担当者名',
-        instructions: 'カスタム手順を作成',
+        title: '新しいエージェント',
+        agentName: 'エージェント名',
+        instructions: 'カスタム指示を作成',
         createAgent: 'エージェントを作成',
         switchAvatar: 'アバターを切り替え',
-        defaultAgentName: (displayName: string) => `${displayName}のエージェント`,
+        defaultAgentName: (displayName: string) => `${displayName} さんの代理人`,
         defaultPrompt:
-            'ギャンブル、映画、その他の明らかに業務外の理由による経費を却下してください。\n\nチップがわかる領収書の画像を必ず添付するようユーザーに通知してください。\n\n同じユーザーの以前のレポートと非常に類似している場合はレポートを承認してください。\n\n交通費が500ドルを超えるレポートを却下してください。',
+            'ギャンブル、映画、またはその他明らかにビジネス目的ではない理由による経費は却下します。\n\nチップの金額が明確にわかるレシート画像を必ず添付するよう、ユーザーにリマインドします。\n\n同じユーザーの過去のレポートと非常によく似ている場合は、そのレポートを承認します。\n\n出張費が500ドルを超えるレポートは却下します。',
     },
     expenseRulesPage: {
         title: '経費ルール',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 06e30c85..28ff4e2f 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2728,14 +2728,14 @@ ${amount} voor ${merchant} - ${date}`,
         emptyAgents: {title: 'Geen agents aangemaakt', subtitle: 'Stop met dingen handmatig doen. Geef in plaats daarvan een opdracht aan een agent en bespaar jezelf veel tijd.'},
     },
     addAgentPage: {
-        title: 'Nieuwe medewerker',
-        agentName: 'Naam agent',
-        instructions: 'Aangepaste instructies schrijven',
-        createAgent: 'Agent maken',
-        switchAvatar: 'Wissel avatar',
+        title: 'Nieuwe agent',
+        agentName: 'Naam medewerker',
+        instructions: 'Schrijf aangepaste instructies',
+        createAgent: 'Agent aanmaken',
+        switchAvatar: 'Profielavatar wisselen',
         defaultAgentName: (displayName: string) => `Agent van ${displayName}`,
         defaultPrompt:
-            'Uitgaven voor gokken, films of andere duidelijk niet-zakelijke redenen afwijzen.\n\nDe gebruiker altijd herinneren een bonafoto toe te voegen waarop de fooi duidelijk te zien is.\n\nHet rapport goedkeuren als het sterk lijkt op eerdere rapporten van dezelfde gebruiker.\n\nRapporten met meer dan $500 aan reiskosten afwijzen.',
+            'Wijs declaraties af die zijn voor gokken, films of andere duidelijk niet-zakelijke redenen.\n\nHerinner de gebruiker eraan altijd een bonafbeelding toe te voegen waarop de fooi duidelijk is.\n\nKeur het verslag goed als het sterk lijkt op eerdere verslagen van dezelfde gebruiker.\n\nWijs verslagen af met meer dan $500 aan reiskosten.',
     },
     expenseRulesPage: {
         title: 'Declaratieregels',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index b5881191..1a633f9f 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2726,9 +2726,9 @@ ${amount} dla ${merchant} - ${date}`,
         instructions: 'Napisz własne instrukcje',
         createAgent: 'Utwórz agenta',
         switchAvatar: 'Zmień awatar',
-        defaultAgentName: (displayName: string) => `Agent użytkownika ${displayName}`,
+        defaultAgentName: (displayName: string) => `Agent ${displayName}`,
         defaultPrompt:
-            'Odrzucaj wydatki na hazard, filmy lub inne oczywiste powody niezwiązane z działalnością.\n\nPrzypominaj użytkownikowi o dołączeniu zdjęcia paragonu, na którym wyraźnie widać napiwek.\n\nZatwierdź raport, jeśli jest bardzo podobny do poprzednich raportów tego samego użytkownika.\n\nOdrzucaj raporty z wydatkami na podróże przekraczającymi 500 $.',
+            'Odrzucaj wydatki związane z hazardem, filmami lub innymi oczywistymi celami niezwiązanymi z działalnością biznesową.\n\nPrzypominaj użytkownikowi, aby zawsze dołączał zdjęcie paragonu, na którym wysokość napiwku jest wyraźnie widoczna.\n\nZatwierdź raport, jeśli jest bardzo podobny do wcześniejszych raportów tego samego użytkownika.\n\nOdrzucaj raporty zawierające więcej niż 500 USD wydatków na podróże.',
     },
     expenseRulesPage: {
         title: 'Reguły wydatków',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 8eaf2423..68efa428 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -2728,7 +2728,7 @@ ${amount} para ${merchant} - ${date}`,
         switchAvatar: 'Trocar avatar',
         defaultAgentName: (displayName: string) => `Agente de ${displayName}`,
         defaultPrompt:
-            'Rejeitar despesas com jogos de azar, filmes ou outros motivos claramente não comerciais.\n\nLembrar o usuário de sempre incluir uma imagem do recibo que mostre claramente a gorjeta.\n\nAprovar o relatório se for muito semelhante a relatórios anteriores do mesmo usuário.\n\nRejeitar relatórios com mais de US$ 500 em despesas de viagem.',
+            'Rejeite despesas relacionadas a jogos de azar, cinema ou outros motivos claramente não relacionados ao negócio.\n\nLembre o usuário de sempre incluir uma imagem do recibo em que a gorjeta fique clara.\n\nAprove o relatório se ele for muito semelhante a relatórios anteriores do mesmo usuário.\n\nRejeite relatórios com mais de US$ 500 em despesas de viagem.',
     },
     expenseRulesPage: {
         title: 'Regras de despesas',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 141e416d..29afd758 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2653,14 +2653,14 @@ ${amount},商户:${merchant} - 日期:${date}`,
         emptyAgents: {title: '尚未创建代理', subtitle: '别再手动处理这些事情了。交给智能代理去执行,为自己节省大量时间。'},
     },
     addAgentPage: {
-        title: '新代理人',
-        agentName: '代理姓名',
+        title: '新代理',
+        agentName: '代理名称',
         instructions: '编写自定义说明',
         createAgent: '创建代理',
         switchAvatar: '切换头像',
-        defaultAgentName: (displayName: string) => `${displayName}的代理`,
+        defaultAgentName: (displayName: string) => `${displayName} 的代理人`,
         defaultPrompt:
-            '拒绝用于赌博、电影或其他明显非商业原因的费用。\n\n提醒用户始终附上清楚显示小费的收据图片。\n\n如果报告与同一用户之前的报告非常相似,则批准该报告。\n\n拒绝出行费用超过500美元的报告。',
+            '拒绝与赌博、电影或其他明显非商务原因相关的报销。\n\n提醒用户务必附上一张能清楚显示小费金额的收据图片。\n\n如果报销报告与同一用户之前的报告非常相似,则批准该报告。\n\n拒绝包含超过 500 美元差旅费用的报销报告。',
     },
     expenseRulesPage: {
         title: '报销规则',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a63929f285

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/pages/settings/Agents/AddAgentPage.tsx
Comment thread src/pages/settings/Agents/AddAgentPage.tsx Outdated
@NicolasBonet NicolasBonet marked this pull request as draft May 4, 2026 21:51
@Expensify Expensify deleted a comment from github-actions Bot May 4, 2026
NicolasBonet and others added 6 commits May 4, 2026 17:06
- Added new SVG files for bot avatars: Ice, Pink, Tangerine, and Yellow.
- Updated DefaultBotAvatars.ts to include the new avatars.
- Modified AddAgentPage.tsx to randomly select an avatar from the updated list for display.
@NicolasBonet NicolasBonet force-pushed the feat/89310-add-agents-flow branch from 44ffcac to 1bb79fa Compare May 4, 2026 22:06
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

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

@NicolasBonet NicolasBonet marked this pull request as ready for review May 4, 2026 22:08
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

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

@Expensify Expensify deleted a comment from github-actions Bot May 4, 2026
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1bb79fa9fd

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/libs/actions/Agent.ts
@shawnborton
Copy link
Copy Markdown
Contributor

Is it possible to only show one form error message in the form if there is just one message?
CleanShot 2026-05-05 at 08 03 57@2x

I feel like we've done this elsewhere - basically the message directly above the button is kinda pointless given that it's easy to see the existing form error. That pattern was originally introduced for super long forms, to let you know you need to scroll up the screen.

@shawnborton
Copy link
Copy Markdown
Contributor

For this component:
CleanShot 2026-05-05 at 08 04 53@2x

It should match this component:
CleanShot 2026-05-05 at 08 05 08@2x

Where we have outline around the secondary remix button. Can we standardize please? Ideally we don't need to recreate a new component and we can use existing ones:
CleanShot 2026-05-05 at 08 05 36@2x

CleanShot 2026-05-05 at 08 05 52@2x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants