Skip to content

[Due for payment 2026-08-07] Add an agent-template picker modal before new agent creation #94394

Closed

Description

@melvin-bot

Problem

When creating a new custom agent, users are dropped straight into the "build your own" flow with a blank slate. There's no guidance or inspiration, which makes it harder for users to get started and discover what agents can do.

Proposed solution

Add a modal in front of the new agent creation flow that offers:

  • A list of common/suggested agents (templates) the user can pick from to get started quickly.
  • A "build your own" option that leads to the current custom creation flow.

Context

Came out of feedback on the new custom agent creation flow — the goal is a more guided, polished onboarding so users immediately see what's possible.

Reported in Slack.

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Jun 25, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @dubielzyk-expensify (Design), see these Stack Overflow questions for more details.

  2. dubielzyk-expensify commented on Jun 26, 2026

    @dubielzyk-expensify
    Contributor

    Re-assigning this to Shawn and Danny (they can battle) as I'm out for two weeks. I did do some preliminary mocks for this here though:

    Image

    Figma

  3. shawnborton commented on Jun 26, 2026

    @shawnborton
    Contributor

    I like that! Here is a quick riff on my end:

    Image

    Do we have a list of the default agents we're planning to build? cc @marcaaron @puneetlath @yuwenmemon so we can fill this mock in with real data

  4. dannymcclain commented on Jun 26, 2026

    @dannymcclain
    Contributor

    I like that riff Shawn. Big green button for custom and explicit add buttons for the templates—nice 👍

  5. yuwenmemon commented on Jun 26, 2026

    @yuwenmemon
    Contributor

    This is for Personal agents, so I think we should wait until it has copilot ability with this issue: https://github.com/Expensify/Expensify/issues/650657

    And then have the agents be more "helpers" rather than rule enforcers, watching out for things.

  6. shawnborton commented on Jun 27, 2026

    @shawnborton
    Contributor

    Sounds good. Do you have an idea of what they will be?

  7. quinthar commented on Jun 30, 2026

    @quinthar
    Contributor

    Copilot access is done!

  8. dannymcclain commented on Jun 30, 2026

    @dannymcclain
    Contributor

    Not overdue. Also looks like there's a question in Slack about pre-defined prompts.

  9. 42 remaining items

  10. mallenexpensify commented on Aug 11, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @shubham1206agra due $250 via NewDot
    Contributor+: @gijoe0295 due $250 via NewDot

    cc @yuwenmemon in case you disagree about the regressions not being caused by the work on their PR

    ^ Test case created. Thx

  11. MelvinBot commented on Aug 11, 2026

    @MelvinBot
    Contributor

    The auto-generated Payment Summary only pulls people who are assignees on the issue, and gijoe0295 was never assigned here — so the automation couldn't include them.

    shubham1206agra asked to have them added as reviewer on Aug 5 (comment), but that assignment was never actually made. The issue's assignment history only ever shows the design/eng folks plus shubham1206agra (assigned 2026-07-03) on the contributor side — gijoe0295 is not in it. When the summary generated on Aug 6, the only payable assignee it found was shubham1206agra.

    You've already corrected it manually by posting the full Payment Summary with both shubham1206agra (Contributor) and gijoe0295 (Contributor+). To avoid this next time, add the C+ reviewer as an issue assignee when they're brought on so the automation picks them up.

  12. allgandalf commented on Aug 11, 2026

    @allgandalf
    Contributor

    @MelvinBot why wasn't @gijoe0295 mentioned in the payment summary? cc @allgandalf

    We're working to fix this i think in some of the many issuessss ????~~~~!!!!!!! rightttt ???

  13. allgandalf commented on Aug 11, 2026

    @allgandalf
    Contributor
  14. MelvinBot commented on Aug 11, 2026

    @MelvinBot
    Contributor

    The gap here isn't really the summary generator misbehaving — it keys off the issue's assignees, and gijoe0295 was never added as one (the assignment shubham1206agra requested on Aug 5 was never actually made). So the automation had nobody to list on the reviewer side beyond shubham1206agra.

    I didn't find an open issue specifically tracking "payment summary omits the C+ when they aren't assigned." If you want the tooling to be more forgiving (e.g. cross-check the linked PR's reviewers, not just issue assignees), that'd be worth a dedicated issue — happy to draft one if you point me at where it should live. Otherwise the practical fix is just assigning the C+ reviewer to the issue when they come on board so the summary picks them up automatically.

  15. added and removed on Aug 11, 2026
  16. JmillsExpensify commented on Aug 11, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @gijoe0295

  17. added and removed on Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions