Bill default voice ID expires December 31, 2026

Open Beginner friendly
#2,848 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ai, tooling

Research direction

Read LifeOS/install/agents/Astra.md line 6 and listen to the suggested Wyatt voice to compare it with the current Bill voice. If it is a suitable replacement, update the default voice ID and verify the value. Done when Astra uses the chosen valid voice ID; the issue does not name a test to run.

Written by the indexing model from the issue text.

Description

LifeOS/install/agents/Astra.md line 6 uses pqHfZKP75CvOlQylNhV4, the ElevenLabs Bill default voice. https://github.com/danielmiessler/LifeOS/blob/f6ab5e0228bfb356c82edbf52b69344dbd585486/LifeOS/install/agents/Astra.md#L6

ElevenLabs says all default voices expire on December 31, 2026. They are also limited to accounts created before March 2026, so anyone with a newer account may already be unable to use this ID. Source https://elevenlabs.io/docs/help-center/product/voices/my-voices/what-are-default-voices

ElevenLabs suggests Wyatt (Seasoned Mentor) as the replacement, voice ID FrS6cKLB1wg4WYgPa9GW. It says the swaps are not exact matches, so it is worth a listen before changing the default.

If you want more options, I keep a table of every expiring ID next to its replacement ID at https://voicefieldguide.com/elevenlabs-default-voices#voice-ids. Disclosure: some of the other voices on that page are mine.

Dominant language
TypeScript
Stars
19.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

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 danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.