Skip to content

[No QA] Docs updates for E/A#96773 Agent rule change log in #admins room #97398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MelvinBot wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −0
Open

[No QA] Docs updates for E/A#96773 Agent rule change log in #admins room #97398

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/articles/new-expensify/ai-agents/Create-Agent-Rules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,19 @@ Deleting an Agent rule stops RuleBot from enforcing that rule on future report a

---

## How to review Agent rule changes in the #admins room

Whenever an Agent rule is added, updated, or deleted, Expensify records a system message in your workspace's **#admins** room so admins have a visible history of the change.

@github-actions github-actions Bot Jul 30, 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.

Terminology consistency: Use the exact role term "Workspace Admins" rather than the informal "admins" (and "admin team" on the sentence below). HELPSITE_NAMING_CONVENTIONS.md (Deterministic Writing) and the article's own usage of Workspace Admins call for consistent, exact role terminology.


- **Added** and **updated** messages show the rule's title and its full prompt.
- **Deleted** messages show the rule's title.
Comment on lines +112 to +113

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Qualify the claim that change logs always show a title

When server-side title generation fails, these messages do not show a rule title: AgentRuleChangeLogUtils.ts explicitly treats the generated title as best-effort, add/update fall back to prompt-only messages, and delete falls back to the generic “removed an agent rule.” Documenting titles as unconditional therefore gives admins an inaccurate expectation for this supported scenario; clarify that the title appears only when available.

Useful? React with 👍 / 👎.


Because the **#admins** room is visible only to Workspace Admins, this history stays private to your admin team. To review it, open your workspace's **#admins** room and find the relevant system message.

@github-actions github-actions Bot Jul 30, 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.

Prohibited/vague navigation phrasing: "find the relevant system message" is a vague locate-phrase similar to the prohibited "Find the setting" (HELPSITE_NAMING_CONVENTIONS.md, Prohibited Language). This heading is "How to review Agent rule changes," so give explicit, deterministic navigation for opening the room instead — e.g. reference the exact navigation to reach the #admins room (per the Navigation Instruction Standards) and describe the exact system message the reader is looking for.


Learn more about the [#admins room](/articles/new-expensify/chat/Expensify-Chat-Rooms-for-Admins).

---

# FAQ

## Can Agent rules make mistakes?
Expand Down
Loading