Skip to content

[No QA] Add new Agent explanatory articles and restructure AI Agents hub - #103119

Merged
VictoriaExpensify merged 29 commits into
mainfrom
helpsite-revise-agent-docs
Oct 8, 2026
Merged

VictoriaExpensify merged 29 commits into
mainfrom
helpsite-revise-agent-docs

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

Explanation of Change

Created 2 new articles:

  • Learn-About-Al-in-Expensify.md - a single help page explaining all types of Al in Expensify
  • Understand-How-Agents-Work.md - explains the difference between personal agents and agent rules/Rulebot

Also updates the remaining articles to tighten scope and reinforce cross-linking,

Fixed Issues

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

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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.
  • 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

stephanieelliott and others added 16 commits October 5, 2026 14:23
Ports the AI Agents docs refactor from claude-docs-agentRuleSuggestions onto this branch, keeping this branch's content wherever the two conflict:

- Rename Create-Agent-Rules -> Automate-Workflows-with-Agent-Rules, Create-and-Use-Custom-Agents -> Create-and-Use-Agents, How-to-Write-Agent-Rules -> How-to-Write-Agent-Instructions
- Use Learn-About-Agents as the overview article
- Add the RuleBot-as-approver section and FAQ, and generalize the writing guide to cover both Agents and Agent rules
- Update cross-links across the AI Agents set and inbound links from other articles
- Add redirects for the three renamed articles
- Leave AI-Agent-Capabilities.md and AI-Agent-Triggers.md unchanged

Co-authored-by: Stephanie Elliott <[email protected]>
Add scope and setup columns, Concierge workspace setup and bulk updates, agent messaging points, and fix links, casing, and frontmatter.

Co-authored-by: Stephanie Elliott <[email protected]>
Updated the order of the article to reflect new structure.
Updated the link to the article on how agents work.
Added order metadata for article organization.
Updated the link text for learning about agents to improve clarity.
Updated the link to the section on how agents use instructions for better clarity.
Added order field to the Agent Capability Reference.
Added order field to the Agent Trigger Reference documentation.
@stephanieelliott stephanieelliott self-assigned this Oct 6, 2026
@stephanieelliott
stephanieelliott requested a review from a team as a code owner October 6, 2026 02:46
@stephanieelliott stephanieelliott added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Oct 6, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-06T02:57:08.217406Z 262aa1f PR opened
ℹ️ 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

melvin-bot Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @VictoriaExpensify

@melvin-bot
melvin-bot Bot requested review from VictoriaExpensify and mkhutornyi and removed request for a team October 6, 2026 02:46
@melvin-bot

melvin-bot Bot commented Oct 6, 2026

Copy link
Copy Markdown

@mkhutornyi @VictoriaExpensify One of you needs to 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]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

@stephanieelliott
stephanieelliott removed the request for review from mkhutornyi October 6, 2026 02:46
Added contentType and order metadata to the Agent Trigger reference.
@stephanieelliott

Copy link
Copy Markdown
Contributor Author

@MelvinBot can you apply the rules defined in HELP_AUTHORING_GUIDELINES.md and HELPSITE_NAMING_CONVENTIONS.md on the branch claude-helpdotNamingNavigationConventions (PR #103116) to the articles edited in this PR?

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@MelvinBot

Copy link
Copy Markdown
Contributor

I reviewed all 12 edited articles against HELP_AUTHORING_GUIDELINES.md and HELPSITE_NAMING_CONVENTIONS.md from [HOLD on 102832] Update HelpDot naming, navigation, and capitalization conventions. I couldn't push the fixes, so the changes needed are listed below.

⚠️ I can't push changes to this PR because I didn't open it and I'm not listed as an assignee. To have me make this fix, add me to the PR assignees and then retry your request.

Fixes that apply to most articles:

  1. Lowercase "agents" and "agent rules" in running text and ## headings. The UI uses lowercase in running text (for example, "agent rules being enforced by RuleBot"). Keep bold Agents or Agent rules only when naming the UI tab or page. The same goes for "Agent templates" and "Suggested Agent rules".
  2. Lowercase roles. "Workspace Admin(s)" → "workspace admin(s)". The role picker label is Admin, not Workspace Admin.
  3. Use "select", not "click" or "tap".
  4. Use bolded navigation paths with lowercase placeholders. For example, write Account > Agents or Workspaces > [workspace name] > Members. Don't split these into separate "Click X. Click Y." steps.
  5. Use the exact position parenthetical: "(on the left on web, on the bottom on mobile)". Don't write "and at the bottom on mobile".
Changes needed in each article

Learn-About-AI-in-Expensify.md

  • Change "Workspace Admins" → "workspace admins" (L5, L26, L33, L45, L91, L93, L170, L198).
  • Optional: the Concierge section (L51–57) and the agents section (L81–87) each end with 4 links in a row. The cross-linking rules discourage link lists that work like a navigation hub, so consider keeping 1–2 links per section.

Understand-How-Agents-Work.md

  • Change the ## headings to sentence case and add a question mark: "What are agents?", "What are agent rules?", "What is RuleBot?", "What are agent templates?", "How do agents and agent rules use instructions?", "When should I use an agent or an agent rule?"
  • Lowercase Agent, Agents, Agent rules, and Agent templates throughout, including the metadata.
  • L86: change the anchor text "Write Effective Agent Instructions" so it matches the target, for example "Learn how to write agent instructions". L17 in How-to-Write-Agent-Instructions links to the #how-do-agents-and-agent-rules-use-instructions anchor, so check that link still works after the heading change.
  • L102: change Workspace > Rules → Workspaces > [workspace name] > Rules.
  • Change "Workspace Admins" → "workspace admins" (L5, L36, L101).

How-to-Write-Agent-Instructions.md

  • Lowercase "Agent" and "Agent rules" in the headings (L21, L49–83, L95, L117) and in body text.
  • L109–113: replace the steps with "select Workspaces > [workspace name] > Members", then "Select RuleBot", "Select Profile", and "Select Message". Use "select" instead of "click".
  • Change "Workspace Admin" → "workspace admin" (L5, L25).

Create-and-Use-Agents.md

  • Replace every "click" and "tap" with "select" in the steps.
  • Combine each "click Account. Click Agents." pair into one step: "select Account > Agents" (L37–38, L50–51, L94–95, L106–107, L118–119, L131–132, L139–140). Change "Account > Agents" → "Account > Agents" (L158, L166).
  • L189: change "and at the bottom on mobile" and "[Workspace name]" to "(on the left on web, on the bottom on mobile)" and Workspaces > [workspace name] > Workflows.
  • L96: change "click the chat icon on the agent's row" → "select Chat", which matches the button named on L58.
  • L208: fix the broken link [...]([url](/articles/...)).
  • Change Copilot: Delegated Access → Copilot: Delegated access to match the UI (L17, L76, L246).
  • Lowercase the headings: "Who can use agents" and "How to create an agent".
  • L187: change "Workspace member" → "workspace member".

Automate-Workflows-with-Agent-Rules.md

  • Lowercase "Agent rule(s)" in the headings and body text, and change "Workspace Admin(s)" → "workspace admin(s)".
  • L116: add the missing period.
  • L119 and L130: change "AI rule" → "agent rule".
  • L145: change Workspace Admin → Admin to match the role label.

Use-Suggested-Agent-Rules.md

  • Change "Suggested Agent rule(s)" → "suggested agent rule(s)" in the headings (L21, L125, FAQ) and body text.
  • Change "Workspace Admins" → "workspace admins" (L5).

Use-Agent-Templates.md

  • L61: change "What Description Dan Does" → "What Description Dan does".
  • L13: change "personal Agents" → "personal agents". L5: change "Agent rules" → "agent rules".

AI-Agent-Capabilities.md and AI-Agent-Triggers.md

  • Lowercase "Agent" in the metadata and body text.
  • Change "Workspace Admin role" → "workspace admin role" and "Workspace configuration" → "workspace configuration" (Capabilities L95, L107, L143, L273).

What-Concierge-Can-Do.md

  • Change the title and # heading to title case: "What Concierge Can Help You Do in Expensify".
  • L120: change "click or tap the Help icon" → "select the Help icon".
  • L124: change "What Workspace tasks…" → "What workspace tasks…".
  • L164: change "Agents" → "agents".

Manage-Copilot-Access.md

  • Change the title and # heading to title case: "Manage Copilot Access".
  • L43 and L48: change "click" → "select".
  • L89 and L91: change "Workspace Admin(s)" and "Workspace" to lowercase.

Workspace-Rules.md

  • Change "Agent Rule(s)" → "agent rule(s)" (L14, L128, L135).
  • L20: change "Only Workspace Admins" → "Only workspace admins".
  • L157–161: use "(on the left on web, on the bottom on mobile), select Workspaces > [workspace name] > Categories", then "Select a category." Replace every "click" with "select" (L157–161, L207).

All articles already meet the guidelines on these points:

  • They have one # title plus # FAQ.
  • They use no ### headings.
  • Their headings are task-based.
  • They use relative links, with no links inside numbered steps.

view run

@stephanieelliott

Copy link
Copy Markdown
Contributor Author

@MelvinBot please push the changes suggested here: #103119 (comment)

@stephanieelliott stephanieelliott left a comment

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.

Clarity pass on the difference between Agents, Agent rules, and RuleBot, and between Agent templates, Agent instructions, and suggested Agent rules. AI-Agent-Capabilities.md and AI-Agent-Triggers.md are intentionally left alone.

Main themes in the inline suggestions:

  1. Instructions are the common thread. All AI Agents work from instructions, and Agent rules are RuleBot's instructions. Templates and suggested rules are pre-written instructions for each kind of Agent.
  2. Observer vs. approver. As an observer, RuleBot flags issues and asks questions. As an approver, it approves, rejects, edits and forwards. "Reject" was missing from RuleBot's action list.
  3. Personal Agents work on your own account until they're invited to a workspace as an approver.
  4. New FAQ: "Should I use a personal Agent or RuleBot as an approver?"

Outside the diff, so I couldn't add suggestions:

  • Create-and-Use-Agents.md: The first FAQ has a broken link: [...]([url](/articles/...)).
  • Use-Agent-Templates.md:
    • The keywords list "Splitter Sam", but the article covers "HotelSplitBot".
    • The heading "What Description Dan Does" is capitalized differently from the other headings.
    • The intro says "prebuilt personal Agents". Consider "starting points for creating a personal Agent".
  • Automate-Workflows-with-Agent-Rules.md:
    • The FAQ "Do I need to create or manage RuleBot? … managed by Expensify" conflicts with the remove/demote/delete section.
    • Step 5 says "select Edit to write your own rule". Please check the button label.
  • UI path mismatch: This PR says Rules > Add rule > Describe agent rule, but Workspace-Rules.md says Agents tab > Add AI rule.
  • Terminology: The articles mix "Agent rules", "agent rules", "Agent Rules" and "AI rule", plus "suggested Agent rule" and "Suggested Agent rule", plus "Agents" and "agents". Pick one form of each.

Lowercase agents, agent rules, and roles in running text; use select instead of click/tap; use bolded navigation paths with lowercase placeholders; fix heading casing and a broken FAQ link.

Co-authored-by: Stephanie Elliott <[email protected]>
@MelvinBot

Copy link
Copy Markdown
Contributor

I pushed the changes from my earlier comment in 9f2aacc. It updates all 12 articles.

These changes apply across the articles:

  • "Agents", "Agent rules", "Agent templates", and "Suggested Agent rules" are now lowercase in running text, metadata, and ## headings. Bold UI labels such as Agents and Agent rules are enforced by are unchanged.
  • "Workspace Admin(s)" is now "workspace admin(s)". In Automate-Workflows-with-Agent-Rules, the role label is now Admin.
  • Steps use "select" instead of "click" and "tap".
  • Steps use bolded navigation paths with lowercase placeholders, such as Account > Agents and Workspaces > [workspace name] > Workflows. Steps that were merged into one path are renumbered.
  • Every article uses the exact parenthetical "(on the left on web, on the bottom on mobile)".
Changes in specific articles
  • Understand-How-Agents-Work: The question headings now end with "?". The "Write Effective Agent Instructions" link now reads "Learn how to write agent instructions". Workspace > Rules is now Workspaces > [workspace name] > Rules. The anchor that How-to-Write-Agent-Instructions links to still works.
  • Create-and-Use-Agents: I fixed the broken [...]([url](...)) FAQ link. "Click the chat icon" is now "select Chat". Copilot: Delegated Access is now Copilot: Delegated access, which matches the UI.
  • Automate-Workflows-with-Agent-Rules: I added the missing period, and "AI rule" is now "agent rule".
  • Use-Agent-Templates: The heading now reads "What Description Dan does".
  • What-Concierge-Can-Do and Manage-Copilot-Access: The titles are now in title case. Neither file was renamed, so the URLs don't change.
  • Workspace-Rules: The category steps now use Workspaces > [workspace name] > Categories. "Agent Rules" is now "agent rules".

I left these unchanged:

  • Links whose text is an article's title, such as [Create and Use Agents], still use title case.
  • The keywords metadata.
  • The optional link trimming in Learn-About-AI-in-Expensify.

No automated checks apply to Markdown-only changes, so please spot-check the HelpDot preview that OSBotify posts for this commit.


view run

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.


---

## What are suggested Agent rules

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Inconsistent use of captalisation for Agent/agent

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 should be fixed now!


Both give you pre-written instructions, but for different kinds of Agents:

- An **Agent template** gives you instructions for a personal Agent that works on your own expenses.

@VictoriaExpensify VictoriaExpensify Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

https://8ca159ac.helpdot.pages.dev/articles/new-expensify/ai-agents/Learn-About-AI-in-Expensify feels like a pre-curser to this article, but it doesn't make any reference to agent templates. It was a bit jarring to go from that article to this one and see this reference for the first time. I think it might be good to reference Tamplates in the About AI article, even if it's just to say "here are some existing templates that can be applied..."

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.

Good call! I added this to Learn About AI in Expensify, under ## How do agents automate expense tasks?:

You don't have to create an agent from scratch. You can use agent templates, which come with pre-written instructions for common tasks. You can choose a template and customize its instructions to fit your workflow.

Learn more about agents, agent rules, and templates.

@VictoriaExpensify VictoriaExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I've left a couple of minor comments but this is looking good!

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@VictoriaExpensify
VictoriaExpensify merged commit 960127c into main Oct 8, 2026
16 of 18 checks passed
@VictoriaExpensify
VictoriaExpensify deleted the helpsite-revise-agent-docs branch October 8, 2026 02:45
@OSBotify OSBotify mentioned this pull request Oct 8, 2026
90 tasks done
@OSBotify

OSBotify commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/VictoriaExpensify in version: 9.5.6-0 🚀

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

@OSBotify

OSBotify commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.5.6-6 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants