Skip to content

[No QA] Update documentation for AI Agents - #94752

Merged
VictoriaExpensify merged 9 commits into
mainfrom
helpsite-agent-clarify-abilities
Jun 27, 2026
Merged

[No QA] Update documentation for AI Agents#94752
VictoriaExpensify merged 9 commits into
mainfrom
helpsite-agent-clarify-abilities

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown

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: 2807836bd8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread docs/articles/new-expensify/ai-agents/Create-and-Use-Agents.md Outdated
@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR rebrands "Custom Agents" to "Agents" across the AI Agents article (title, H1, all section headings, body copy, FAQ, frontmatter, and the filename Create-and-Use-Custom-Agents.md to Create-and-Use-Agents.md). It also adds clarifying content about agent account isolation (agents operate from their own account and cannot act on your behalf), two "Coming soon" callouts about delegated Copilot access, and two new FAQ entries. The changes are well-written and consistent, and they preserve the article's existing strong structure.

Scores Summary

  • Readability: 9/10 - Clear, concise prose. New paragraphs explaining account isolation and the "Coming soon" callouts are easy to scan and benefit-focused. Sentences flow well and steps remain intact.
  • AI Readiness: 8/10 - Frontmatter (title, description, keywords, internalScope) is retained and updated to match the new terminology. Headings stay task-based, hierarchy is one H1 and H2s only, and feature names are spelled out. Minor risk: dropping "Custom" narrows keyword/search coverage, and the rename introduces a broken inbound cross-link (see Key Findings) that hurts retrieval/navigation.
  • Style Compliance: 9/10 - UI labels (Account, Agents, Beta, Edit, Chat) stay bold and exact; navigation phrasing ("In the navigation tabs (on the left on web, on the bottom on mobile)") matches conventions; FAQ entries use question-form headings per the FAQ exemption. New "Can an Agent make mistakes?" and "Can I add an Agent as a Copilot on my own account?" entries are compliant.

Key Findings

  • Broken inbound cross-link: This PR renames the file but docs/articles/new-expensify/concierge-ai/What-Concierge-Can-Do.md (line 161) still links to /articles/new-expensify/ai-agents/Create-and-Use-Custom-Agents and still says "Custom Agents." That link will 404 after this merges and should be updated in this PR.
  • Terminology consistency is excellent - every "Custom Agent(s)" occurrence was updated, including title, description, internalScope, and all FAQ headings. No stragglers in the changed file.
  • Strong additions: the account-isolation paragraph and the two "Coming soon" callouts set accurate expectations and are clearly written.
  • Headings remain fully task-based/question-based and the single H1 structure is preserved.

Recommendations

  • Priority: Update the inbound link and surrounding text in What-Concierge-Can-Do.md to point to /articles/new-expensify/ai-agents/Create-and-Use-Agents and use "Agents" terminology, so no broken link ships.
  • Consider keeping "custom agents" in the keywords array to preserve search coverage for users who still use the older term.
  • Verify the redirects file has an entry mapping the old slug to the new one so external/bookmarked links to the renamed page do not break.

Files Reviewed

  • docs/articles/new-expensify/ai-agents/Create-and-Use-Agents.md (renamed from Create-and-Use-Custom-Agents.md) - High quality; compliant rebrand with strong new content. Address the inbound-link/redirect items above.

Note: Detailed line-by-line feedback has been provided as inline comments.

@stephanieelliott
stephanieelliott requested a review from a team as a code owner June 27, 2026 01:52
@melvin-bot
melvin-bot Bot requested review from marcochavezf and removed request for a team June 27, 2026 01:53
@melvin-bot

melvin-bot Bot commented Jun 27, 2026

Copy link
Copy Markdown

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

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 marcochavezf June 27, 2026 01:53
@github-actions github-actions Bot changed the title Update documentation for AI Agents [No QA] Update documentation for AI Agents Jun 27, 2026
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

Copy link
Copy Markdown
Contributor

@VictoriaExpensify
VictoriaExpensify merged commit cc98ee1 into main Jun 27, 2026
14 checks passed
@VictoriaExpensify
VictoriaExpensify deleted the helpsite-agent-clarify-abilities branch June 27, 2026 03:47
OSBotify pushed a commit that referenced this pull request Jun 29, 2026
…ties

[No QA] Update documentation for AI Agents

(cherry picked from commit cc98ee1)

(cherry-picked to staging by mountiny)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Jun 29, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.21-8 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.21-9 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.22-1 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.24-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.4.24-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.4.24-0 🚀

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

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

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants