You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-08-07] Add an agent-template picker modal before new agent creation #94394
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.
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.
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 shubham1206agrarequested 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.
Activity
melvin-bot commentedon Jun 25, 2026
Triggered auto assignment to @dubielzyk-expensify (
Design), see these Stack Overflow questions for more details.dubielzyk-expensify commentedon Jun 26, 2026
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:
Figma
shawnborton commentedon Jun 26, 2026
I like that! Here is a quick riff on my end:
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
dannymcclain commentedon Jun 26, 2026
I like that riff Shawn. Big green button for custom and explicit add buttons for the templates—nice 👍
yuwenmemon commentedon Jun 26, 2026
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.
shawnborton commentedon Jun 27, 2026
Sounds good. Do you have an idea of what they will be?
quinthar commentedon Jun 30, 2026
Copilot access is done!
dannymcclain commentedon Jun 30, 2026
Not overdue. Also looks like there's a question in Slack about pre-defined prompts.
42 remaining items
mallenexpensify commentedon Aug 11, 2026
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
MelvinBot commentedon Aug 11, 2026
The auto-generated Payment Summary only pulls people who are assignees on the issue, and
gijoe0295was never assigned here — so the automation couldn't include them.shubham1206agraasked 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 plusshubham1206agra(assigned 2026-07-03) on the contributor side —gijoe0295is not in it. When the summary generated on Aug 6, the only payable assignee it found wasshubham1206agra.You've already corrected it manually by posting the full Payment Summary with both
shubham1206agra(Contributor) andgijoe0295(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.allgandalf commentedon Aug 11, 2026
We're working to fix this i think in some of the many issuessss ????~~~~!!!!!!! rightttt ???
allgandalf commentedon Aug 11, 2026
Yeah we areee https://github.com/Expensify/Expensify/issues/661235, should be fixed soon
MelvinBot commentedon Aug 11, 2026
The gap here isn't really the summary generator misbehaving — it keys off the issue's assignees, and
gijoe0295was never added as one (the assignmentshubham1206agrarequested on Aug 5 was never actually made). So the automation had nobody to list on the reviewer side beyondshubham1206agra.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.
JmillsExpensify commentedon Aug 11, 2026
$250 approved for @gijoe0295