[No QA] Create a AgentZero reference page for upcoming features

[stephanieelliott]

Explanation of Change

Create page for "upcoming features" for AgentZero to reference when users ask about features that are in development.

Slack discussion: https://expensify.slack.com/archives/C07HPDRELLD/p1772598521535409?thread_ts=1772440234.162629&cid=C07HPDRELLD

Fixed Issues

$ #83970
PROPOSAL: N/A

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

N/A, no 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.

Screenshots/Videos

Android: Native

android.mp4

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

web.mp4

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://144cf85b.helpdot.pages.dev ⚡️

Updated articles:

• articles/Unlisted/AgentZero-Upcoming-Features

[melvin-bot]

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 @twisterdotcom

[melvin-bot]

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR introduces a new internal-only reference page listing upcoming features for AgentZero, along with a noindex/nofollow mechanism in the default layout template. The concept is sound and fills a real need -- giving AgentZero a structured reference for forward-looking answers. The template change is clean and well-scoped. The content itself is generally well-organized, but there are several terminology, style, and metadata issues in the new Markdown file that should be addressed before merge.

Scores Summary

• Readability: 7/10 - Clear and scannable bullet-point format. Descriptions are concise and jargon-free. However, the page mixes audience perspectives (sometimes addressing AgentZero as an operator, sometimes describing features in user-facing language) without fully committing to either voice. The use of the em dash separator pattern is consistent and effective.
• AI Readiness: 6/10 - The internalScope field is present but does not follow the recommended format (Audience is [target role]. Covers [main topic]. Does not cover [excluded areas].). Headings are descriptive but use title case with ampersands rather than sentence case. The keywords field uses a comma-separated string rather than the array format ([keyword1, keyword2]) used in other HelpDot articles (e.g., Workspace-Rules.md, Two-Factor-Authentication.md).
• Style Compliance: 5/10 - Multiple terminology issues conflict with Expensify documentation standards. See key findings below.

Key Findings

Terminology issues (must fix):

• The heading "Workspace & Policy" and the item "Policy presets" use the term "policy" in a user/reader-facing context. HelpDot standard terminology is "workspace" -- "policy" is an internal/code term. This should read "Workspace presets" or similar.
• "Report templates" references "default policy" in its description. This should say "default workspace."
• "Approval flow" should be "approval workflow" to match existing documentation (see Workspace-Rules.md).
• Several items reference "admins" generically. Existing docs use "Workspace Admins" as the specific term.

Front matter issues:

• keywords is formatted as a bare comma-separated string (upcoming features, roadmap, coming soon, AgentZero reference). Other Unlisted and New Expensify articles use YAML array syntax ([keyword1, keyword2, keyword3]). This should be made consistent.
• internalScope does not follow the established three-part pattern. Compare with Workspace-Rules.md which uses: Audience is Workspace Admins on the Control plan. Covers enabling and managing workspace-level rules... Does not cover personal expense rules.... A suggested revision: Audience is AgentZero and internal tooling. Covers planned and upcoming features for New Expensify that are not yet generally available. Does not cover released features, feature timelines, or implementation details.

Heading hierarchy:

• The page uses only # and ##, which is correct for AI readiness. However, headings use title case with ampersands ("Expense & Report Management", "Search, Insights & Export"). HelpDot articles typically use sentence case for section headings (e.g., "Expense and report management"). Ampersands should be spelled out as "and."

Positive aspects:

• The noindex/nofollow template change in default.html is clean, minimal, and correctly scoped behind a conditional. This is a valuable addition to the layout system for any future unlisted or internal pages.
• Placing the file in docs/articles/Unlisted/ is the correct location per the existing unlisted-docs-info.md guidance.
• The "How to Use This Page (AgentZero)" section at the bottom is a thoughtful addition that gives clear operational guidance.
• The disclaimer about items being subject to change is important and well-placed.
• Content is organized into logical, well-labeled sections that mirror the product feature areas.

Content accuracy caution:

• Since these are described as upcoming/planned features, accuracy cannot be fully verified against shipped product. The descriptions are plausible and well-written, but the page should have a clear internal owner responsible for keeping it current. Stale "coming soon" content that never ships could lead AgentZero to give misleading answers.

Minor note on the jekyll-seo-tag plugin:

• The jekyll-seo-tag plugin (used in this site) already supports a front matter field to suppress indexing. However, the manual <meta name="robots"> approach used here is explicit and works as a reliable fallback. No conflict is expected since the SEO plugin does not emit a robots meta tag by default. This is acceptable.

Recommendations

1. Fix terminology: Replace "policy" with "workspace" in user-facing descriptions. Replace "approval flow" with "approval workflow." Use "Workspace Admins" instead of generic "admins."
2. Align front matter format: Change keywords to array syntax. Revise internalScope to follow the three-part pattern used in other articles.
3. Use sentence case for headings: Change "Expense & Report Management" to "Expense and report management," and similarly for all other section headings.
4. Establish a maintenance plan: Add a comment or internal note about who owns keeping this page current and how often it should be reviewed. Stale roadmap content is worse than no roadmap content for an AI agent.
5. Consider adding a "last reviewed" date: A front matter field like lastReviewed: 2026-03-05 would help internal teams know when the content was last validated.

Files Reviewed

• docs/_layouts/default.html -- 3 lines added. Clean conditional for noindex/nofollow meta tag. No issues.
• docs/articles/Unlisted/AgentZero-Upcoming-Features.md -- 85 lines added (new file). Well-structured internal reference page with terminology and front matter issues that should be corrected before merge.

---

This review covers only the proposed changes in the diff. Unchanged portions of existing files were not scored or critiqued.

[OSBotify]

🚀 Deployed to staging by https://github.com/twisterdotcom in version: 9.3.34-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.34-2 🚀

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