Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

whisper-1 is being retired (constants.ts)

Closed Beginner friendly
#7,905 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@wamg7193-wq is already working on this.

Since Oct 8, 2026.

  • #7920 by @wamg7193-wq — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
ai

Research direction

Start at packages/global/core/ai/constants.ts:76 and trace how the default speech-to-text model is selected and used. Confirm whether whisper-1 is the system default, then update the relevant default to gpt-transcribe and run the existing checks for this AI configuration. Done means the default no longer relies on the retiring model.

Written by the indexing model from the issue text.

Description

Hi, quick heads-up in case this isn't already on your radar.

OpenAI is shutting down whisper-1 on February 26, 2027.

It looks like FastGPT still uses it, where it's the system default speech-to-text model. It's still there on the default branch as of October 1:

packages/global/core/ai/constants.ts:76

OpenAI's replacement is gpt-transcribe.

There's still time, but the provider sets the date and it won't move.

How I found it: I maintain DocsWatcher, an open source scanner that checks code against the deprecation notices providers publish. I ran it over the 50 most-starred repos tagged openai. Most of what it turns up is model names sitting in lists and price tables, which don't break anything, so I set those aside and read every hit in real code myself before opening anything. This one looked like a real call to me, but you know your code and I don't, so if I've got it wrong just say so and I'll close this.

Nothing to adopt here. I just thought you'd want to know.

Dominant language
TypeScript
Stars
29.8k
Forks
7.3k
Avg merge
1d 3h
Merged PRs (30d)
171

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from labring/FastGPT

All issues in labring/FastGPT

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.