bug: Algorithm component hardcodes ElevenLabs voice_id instead of using template variable

[jlacour-git]

Problem

The Algorithm component (Components/Algorithm/v0.2.25.md) hardcodes an ElevenLabs voice_id (gJx1vCzNCD1EQHT212Ls) in all phase announcement curl commands:

🔊 `curl -s -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message": "Entering the Observe phase", "voice_id": "gJx1vCzNCD1EQHT212Ls"}'`

This ID is provider-specific and breaks silently when the user changes their voice server or voice provider. The > /dev/null 2>&1 in the template hides the error, so the user doesn't know phase announcements stopped working.

Impact

• Anyone who changes daidentity.voiceId in settings.json gets silent failures on all Algorithm phase voice announcements
• The error is invisible because stdout/stderr are redirected to /dev/null
• Other identity values (name, fullName, displayName) already use template variables — voiceId is the only one that doesn't

Proposed Fix

1. Add {DAIDENTITY.VOICEID} to CreateDynamicCore.ts:

// In loadVariables():
"{DAIDENTITY.VOICEID}": settings.daidentity?.voiceId || "1",

2. Use it in the Algorithm component:

🔊 `curl -s -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message": "Entering the Observe phase", "voice_id": "{DAIDENTITY.VOICEID}"}'`

After rebuild, {DAIDENTITY.VOICEID} resolves from settings.json just like {DAIDENTITY.NAME} already does.

Current Template Variables (for reference)

Variable	Source	Status
{DAIDENTITY.NAME}	settings.daidentity.name	✅ Exists
{DAIDENTITY.FULLNAME}	settings.daidentity.fullName	✅ Exists
{DAIDENTITY.DISPLAYNAME}	settings.daidentity.displayName	✅ Exists
{PRINCIPAL.NAME}	settings.principal.name	✅ Exists
{PRINCIPAL.TIMEZONE}	settings.principal.timezone	✅ Exists
{DAIDENTITY.VOICEID}	settings.daidentity.voiceId	❌ Missing

Related

• feat: Local patch tracking and update-safe SYSTEM file management #650 — Local patch tracking (includes stale SKILL.md detection via settings.json mtime)
• The LoadContext.hook.ts rebuild-on-settings-change fix (suggested in feat: Local patch tracking and update-safe SYSTEM file management #650 comment) would ensure SKILL.md stays current after voice_id changes

[Mutdogus]

We've fixed this in our local setup. The root cause is exactly as described — hardcoded voice_id that breaks silently for anyone using a different voice provider or ID.

What We Did

1. Template Variable in CreateDynamicCore.ts

Added {DAIDENTITY.VOICEID} to the template variable resolution, just like {DAIDENTITY.NAME} and {DAIDENTITY.DISPLAYNAME} already work:

"{DAIDENTITY.VOICEID}": settings.daidentity?.voiceId || "",

2. Hooks Read Voice Config Dynamically

Rather than hardcoding the voice_id in Algorithm phase curl commands, our hooks use the getIdentity() helper from lib/identity.ts which reads settings.json at runtime:

const identity = getIdentity();
await fetch('http://localhost:8888/notify', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    message: voiceContent,
    voice_id: identity.mainDAVoiceID,  // from settings.json
    voice_enabled: true,
  }),
});

This means changing daidentity.voiceId in settings.json immediately takes effect across all hooks without rebuilding anything.

3. Multi-Backend Support

We also extended the VoiceServer to support multiple TTS backends (not just ElevenLabs), selectable via settings.json. The voice_id template variable approach works regardless of which backend is active.

Happy to submit a PR for the template variable fix — it's a clean, minimal change to CreateDynamicCore.ts that unblocks anyone using a custom voice configuration.

[jlacour-git]

Update: Problem persists in v3.0 (Algorithm v1.3.0–v1.5.0)

The original issue reported the hardcoded voice_id in v0.2.25. With the v3.0 release, the Algorithm was rewritten (v1.3.0, v1.4.0, v1.5.0) but the same problem was reintroduced — this time with a different hardcoded ElevenLabs ID (fTtv3eikoepIosk8dTZ5).

All 7 phase voice curls in each version contain:

"voice_id": "fTtv3eikoepIosk8dTZ5"

Current state in v3.0

• RebuildPAI.ts already has the template variable mapping: "{DAIDENTITY.ALGORITHMVOICEID}": settings.daidentity?.algorithmVoiceID || ""
• But the Algorithm component templates (v1.3.0.md, v1.4.0.md, v1.5.0.md) don't use it — they hardcode the ElevenLabs ID instead

Error for non-ElevenLabs users

Anyone using a different TTS backend (e.g., Kokoro) gets this on every phase announcement:

{
  "status": "error",
  "message": "Invalid voice_id: fTtv3eikoepIosk8dTZ5. Available voices: marrvin, marlin, daniel"
}

Fix

Replace the hardcoded ID in v1.3.0.md, v1.4.0.md, and v1.5.0.md (7 occurrences each) with:

"voice_id": "{DAIDENTITY.ALGORITHMVOICEID}"

Users then set algorithmVoiceID in settings.json under daidentity. The build resolves it just like {DAIDENTITY.NAME} already works. The older v0.2.31 had this working correctly — it regressed in the v1.x rewrite.

[kaimagnus]

Thanks for reporting this! Fixed in the v3.0 release. The hardcoded voice_id: "fTtv3eikoepIosk8dTZ5" has been removed from all 7 phase announcement curls in the Algorithm component.

The curls now omit voice_id entirely:

curl -s -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message": "Entering the PAI Algorithm Observe phase"}'

When no voice_id is provided, the VoiceServer automatically uses the default voice configured in settings.json (daidentity.voices.main). This lets each user's system use their own configured voice without needing to modify the Algorithm template.