[Due for payment 2026-06-23] [$250] Add confirmation modal after creating your first AI rule (when an agent is created)

[MelvinBot]

Problem

When a user creates their first AI rule, RuleBot silently creates an agent and adds it as an admin to their workspace. There's no clear explanation of what just happened, which is confusing.

Solution

Show a confirmation modal after a user creates their first AI rule (i.e., when an agent is created on their behalf) with the following content:

RuleBot has been added to your workspace

To enforce your agent rules, we've created an agent for you and added it as an admin to your workspace.

Edit your agent's details in Account > Agents

( Got it )

Context

This came out of feedback that the experience of creating a first AI rule doesn't explain that an agent is being created and added as a workspace admin. A modal makes this transparent.

Slack thread: https://expensify.slack.com/archives/C090U774ZH7/p1781267199740459

Issue Owner

Current Issue Owner: @aimane-chnaif

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022066565317596970159
• Upwork Job ID: 2066565317596970159
• Last Price Increase: 2026-06-15
• Automatic offers:
• aimane-chnaif | Reviewer | 111731471

[puneetlath]

Mockup from @shawnborton

[puneetlath]

@MelvinBot investigate this.

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a user adds their first AI rule, the backend silently creates a "RuleBot" agent and adds it as an admin to the workspace. Nothing in the UI explains this, so the side effect is confusing. We want a one-time confirmation modal explaining what happened.

What is the root cause of that problem?

This is a missing-UX gap, not a bug. The agent is created server-side as a side effect of the ADD_POLICY_AI_RULE command — the frontend saveRule handler just fires the action and immediately navigates back, with no acknowledgement that an agent was created:

Code references

• Rule submit handler navigates back with no confirmation: AddAIRulePage.tsx:56-59
• The action only writes the rule; agent creation is server-side: Policy/Rules.ts:329-397
• The created agent is tracked on the policy via ruleBotAccountID: Policy.ts:2283-2284
• Existing AI rules live at policy.rules.aiRules: Policy.ts:2279-2280

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

This is frontend-only in Expensify/App — no backend change needed, since the agent is already created server-side and we only need to surface a message.

1. In AddAIRulePage.tsx, detect whether this is the first rule before submitting, using the same isEmptyObject check the section already uses (AIRulesSection.tsx:34-35):

   const policy = usePolicy(policyID);
   const [showAgentCreatedModal, setShowAgentCreatedModal] = useState(false);
   
   const saveRule = (values) => {
       const isFirstRule = isEmptyObject(policy?.rules?.aiRules);
       addPolicyAIRule(policyID, rand64(), values[INPUT_IDS.PROMPT]);
       if (isFirstRule) {
           setShowAgentCreatedModal(true); // navigate back on confirm
       } else {
           Navigation.goBack();
       }
   };

2. Render a ConfirmModal with a single "Got it" action (shouldShowCancelButton={false}) that calls Navigation.goBack() on confirm/close. Title: "RuleBot has been added to your workspace"; prompt: the body copy from the mockup; confirm text: "Got it".
3. Add the new strings to the workspace.rules.aiRules block in en.ts:7505-7517 and translate across the other src/languages/*.ts files.

Design considerations

• "First rule" detection: checking isEmptyObject(policy?.rules?.aiRules) at submit time is reliable because the optimistic update for the new rule hasn't been applied yet when saveRule runs. Alternatively !policy?.ruleBotAccountID could be used, but ruleBotAccountID is only set after the server responds, so it's not safe for the optimistic flow.
• Offline: the modal is purely informational and triggers optimistically, so it works offline. The agent is still created server-side once the queued request flushes.
• Edge case: if a user deletes all rules and adds another, aiRules would be empty again and the modal would re-show. Confirm with design whether that's acceptable, or gate on ruleBotAccountID already existing to make it strictly once-per-workspace.

What alternative solutions did you explore?

Showing the modal on PolicyRulesPage/AIRulesSection after navigating back (e.g., watching ruleBotAccountID transition from unset → set). This is more "correct" (fires only when the agent truly exists) but adds cross-page state and a watcher; the in-page approach is simpler and matches the mockup's flow.

---

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

[NicolasBonet]

@MelvinBot let's implement this

[MelvinBot]

🤖 Draft PR created: #93466
Please mark it as "Ready for review" when it is ready for review.