Use the chat engine list for bot and schedule engine names #258

Bots duplicate current engine labels from the chat catalog, while schedules already use that catalog but own separate legacy labels. Share current and legacy display labels without adding legacy IDs to picker options.

Where to start

1. Make frontend/components/bots/types.ts engineLabel use ENGINES from frontend/components/chat/types.ts instead of its own ENGINE_LABELS map
2. Move the legacy-id labels from schedules-data.ts next to ENGINES so every page shows the same name for old rows
3. Add a small test that every id in ENGINE_IDS gets the same label from all callers

Code to look at:

• frontend/components/bots/types.ts:64
• frontend/components/bots/types.ts:73
• frontend/app/agent/schedules/schedules-data.ts:11
• frontend/components/chat/types.ts:89

Open PR #136 also edits schedules-data.ts; expect a small merge.

Done when

• Only one engine-name map remains in frontend
• Bots, schedules and chat show the same label for every engine id, legacy ones included
• cd frontend && bun run test passes

Free to try

Sign up free at app.useagent.org. New accounts get free model credits (GLM or Claude Opus, up to a limit) and free cloud sandbox time, enough to finish this task without paying or adding a key.

Send it a small task in plain words and watch it work. You'll see the screens this issue is about. The link in the sign-up email works for 24 hours. Not there? Check spam.

Stuck? Comment here with a screenshot and we'll help.

Keep private details out of here

This page is public. Don't post your real email, phone number, address, payment details, API keys, or screenshots that show any of them. Send anything private, including how you'd like to be paid, to [email protected] with a link to your comment here.

Claim it

Comment /take and the issue is assigned to you. First come, first served.

Rules

• Use the app while you work, and put before and after screenshots or a short recording in your pull request. For backend or docs work, show the result end to end.
• One change per pull request. Run the checks in CONTRIBUTING.md.
• AI help is fine, blind AI output is not. You must understand, run and explain every line you submit.
• Untested or generated pull requests, and pull requests on an issue someone else claimed, are closed without a reply and don't count for Hacktoberfest.