Skip to content

[no QA] Docs updates for E/A#100686 Document all agent Copilot entry points - #101264

Closed
MelvinBot wants to merge 1 commit into
mainfrom
melvin-docs-agent-copilot-entry-points
Closed

MelvinBot wants to merge 1 commit into
mainfrom
melvin-docs-agent-copilot-entry-points

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

Help site follow-up for Fix back button loop on Profile after copiloting into an agent (Expensify/App#100686).

That PR fixes a navigation loop that happens after using Copilot into account from the agent chat header. Reviewing it surfaced a gap in Create and Use Agents: the article documents only one of the three places you can start a Copilot session with an agent, so the exact flow that PR fixes is not described anywhere on the help site.

This PR updates docs/articles/new-expensify/ai-agents/Create-and-Use-Custom-Agents.md to:

  • Note that Chat with agent on the agent's Edit agent page is a second way to open the agent chat.
  • Add a ## Where else you can Copilot into an agent's account section covering the Edit agent page and the agent chat header → Profile page entry points.
  • State where back navigation lands after Copiloting, which is the behavior Expensify/App#100686 corrects.

No product behavior is documented as changing — the code fix restores the expected back behavior, and the article now matches it.

UI label verification. Every label used was checked against the running app on web rather than taken from the existing article. Confirmed exact strings: Agents, Copilot, Edit, Edit agent, Chat with agent, Copilot into account, Profile, Account.

Screenshots of the verified UI

Agents list row — Copilot and Edit controls plus the chat icon:

Agents list row showing Copilot and Edit controls

Edit agent page — Chat with agent, Copilot into account, Delete agent:

Edit agent page with Copilot into account button

Agent chat header → Profile page — Copilot into account:

Agent chat header Profile page with Copilot into account button

Written against docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md: bolded UI labels with no quotation marks, a task-based ## heading, no new # heading, and the unified web/mobile navigation phrasing already used in the article.

Fixed Issues

$
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

Suggested check for this docs-only change:

  1. Go to Account > Agents and open an agent's row to reach the Edit agent page.
  2. Verify the page shows Chat with agent and Copilot into account, matching the article.
  3. From the agent's chat, click the chat header and verify the Profile page shows Copilot into account.
  4. Use Copilot into account, press back, and verify the Account page opens, matching the article.
  • Verify that no errors appear in the JS console

Offline tests

This change only edits a Markdown file under docs/articles. There is no offline-specific behavior.

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.
// 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.
  • 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

@yusufdeveloper2903, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

Co-authored-by: Yusuf: Software Engineer <yusufdeveloper2903@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team September 16, 2026 00:15
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Sep 16, 2026
@stephanieelliott stephanieelliott changed the title Docs updates for E/A#100686 Document all agent Copilot entry points [no QA] Docs updates for E/A#100686 Document all agent Copilot entry points Sep 22, 2026

Copy link
Copy Markdown
Contributor

No update needed on this, per tightened Melvinbot criteria (see https://github.com/Expensify/Expensify/issues/685679). Feel free to reopen if you disagree!

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.

2 participants