Skip to content

[Due for payment 2026-08-25] Update default custom agent prompt to read as a personal copilot instruction, not a workspace rule #97297

Closed

Description

@yuwenmemon

Problem

The default prompt shown when building a custom agent (Settings > Agents > New agent > Build custom agent) reads like a workspace-scoped approval rule rather than an instruction for a personal copilot agent:

Reject expenses that are for gambling, movies, or other obvious non-business reasons.

Remind the user to always include a receipt image that makes the tip clear.

Approve the report if it's very similar to previous reports from the same user.

Reject reports with more than $500 in travel expenses.

That copy fits a RuleBot-style workspace agent (approve/reject language, policy-wide fields like travel expense caps). Custom agents created from this flow are personal copilots — they act on the user's behalf across any expense, regardless of workspace — so the default prompt should model a personal instruction instead of a workspace rule.

Raised in Slack. From that thread:

This is more the agent where it's like "For all La Boulangerie expenses, set the description to SFO" - an instruction that's more specific to you as a user rather than a workspace agent.

Solution

Replace the addAgentPage.defaultPrompt copy in src/languages/en.ts with a personal-copilot-style instruction (e.g. auto-tagging or describing expenses from a specific merchant), rather than an approve/reject workspace rule. Update the other locale files to match once the new copy is finalized.

Context

  • The default prompt is used as the fallback in AddAgentPage.tsx whenever the "Build custom agent" option is chosen (i.e. no template is selected).
  • This is separate from Add an agent-template picker modal before new agent creation / Add agent template picker structure, which added a template-picker modal in front of the Add Agent flow. That PR renamed this page's title to "Build custom agent" but did not change the defaultPrompt string itself — the custom/build-your-own path still falls back to the same copy above. So this issue isn't blocked by, or already covered by, that work.
Issue OwnerCurrent Issue Owner: @yuwenmemon

Activity

  1. self-assigned this
    on Jul 29, 2026
  2. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    Triggered auto assignment to @ryanschaffer (Waiting for copy), see https://stackoverflow.com/c/expensify/questions/7025/ for more details.

  3. melvin-bot commented on Aug 3, 2026

    @melvin-bot

    @ryanschaffer, @yuwenmemon Huh... This is 4 days overdue. Who can take care of this?

  4. melvin-bot commented on Aug 5, 2026

    @melvin-bot

    @ryanschaffer, @yuwenmemon Still overdue 6 days?! Let's take care of this!

  5. melvin-bot commented on Aug 7, 2026

    @melvin-bot

    @ryanschaffer, @yuwenmemon Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  6. melvin-bot commented on Aug 11, 2026

    @melvin-bot

    @ryanschaffer, @yuwenmemon 12 days overdue now... This issue's end is nigh!

  7. yuwenmemon commented on Aug 12, 2026

    @yuwenmemon
    ContributorAuthor

    @MelvinBot can you come up with a default prompt in Expensify's writing style? It should still be a proper AI prompt, primarily though.

  8. MelvinBot commented on Aug 12, 2026

    @MelvinBot
    Contributor

    Here's a default prompt that reads as a personal copilot instruction (acts on your expenses, not a workspace approve/reject rule) while still being a real, usable AI prompt. It leans on the merchant auto-tag/describe pattern from the Slack thread and shows a bit of range (categorize, describe, tag, flag):

    Categorize all expenses from Starbucks and other coffee shops as Meals.

    For every Uber and Lyft ride, set the description to "Client travel."

    Tag anything I buy at the Apple Store as Equipment.

    Flag any expense that's missing a receipt so I can add one before I submit.

    Why this works as the default:

    • First person ("I"/"my"), acts on any expense — models a personal instruction, not a workspace policy.
    • Shows the useful verbs a copilot can do: categorize, set a description, tag, and flag/remind, so people see the range without a template.
    • Expensify voice: concise, concrete, action-driven, no approve/reject or policy-cap language.
    Exact string for addAgentPage.defaultPrompt
    defaultPrompt:
        'Categorize all expenses from Starbucks and other coffee shops as Meals.\n\nFor every Uber and Lyft ride, set the description to "Client travel."\n\nTag anything I buy at the Apple Store as Equipment.\n\nFlag any expense that\'s missing a receipt so I can add one before I submit.',

    Replaces the current copy in src/languages/en.ts:3038. Note: "Client travel." uses straight ASCII quotes in the English string content today, so I kept them; the per-locale files should use each locale's typographic quotes when translated.

    Want me to open a draft PR applying this to en.ts and updating the other locale files to match? Reply @MelvinBot implement this and I'll take it from here (or drop in your own tweaks to the copy first).

  9. 1 remaining item

  10. yuwenmemon commented on Aug 12, 2026

    @yuwenmemon
    ContributorAuthor

    @ryanschaffer FYI, the current draft in the PR is:

    Categorize all expenses from coffee shops as Meals.

    For every rideshare trip, set the description to "Client travel."

    Tag anything I buy at the electronics store as Equipment.

    Flag any expense that's missing a receipt so I can add one before I submit

  11. ryanschaffer commented on Aug 12, 2026

    @ryanschaffer
    Contributor

    The example prompt above sounds great to me

  12. changed the title [-]Update default custom agent prompt to read as a personal copilot instruction, not a workspace rule[/-] [+][Due for payment 2026-08-25] Update default custom agent prompt to read as a personal copilot instruction, not a workspace rule[/+] on Aug 18, 2026
  13. melvin-bot commented on Aug 18, 2026

    @melvin-bot

    @yuwenmemon

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-08-25. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  14. ryanschaffer commented on Aug 20, 2026

    @ryanschaffer
    Contributor

    Waiting

  15. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    @yuwenmemon Whoops! This issue is 2 days overdue. Let's get this updated quick!

  16. yuwenmemon commented on Aug 24, 2026

    @yuwenmemon
    ContributorAuthor

    This is done

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

Metadata

Metadata

Labels

DailyKSv2ImprovementItem broken or needs improvement.Waiting for copyUser facing verbiage needs polishing

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions