2.1.0 - ENV path inconsistent

[sti0]

Installer installs to $PAI_DIR/.env: https://github.com/danielmiessler/Personal_AI_Infrastructure/blob/main/Bundles/Official/install.ts#L98
Voice server loads from home dir: https://github.com/danielmiessler/Personal_AI_Infrastructure/blob/main/Packs/pai-voice-system/src/voice/server.ts#L29
Hooks read from $PAI_DIR and fall back to .config/pai: https://github.com/danielmiessler/Personal_AI_Infrastructure/blob/main/Packs/pai-voice-system/src/hooks/stop-hook-voice.ts#L36

[virtualian]

Additional Instance: VoiceServer manage.sh

During pai-voice-system installation, encountered another manifestation of this issue:

Problem: manage.sh starts the voice server but doesn't source .env, so the server runs without ELEVENLABS_API_KEY even though it's defined in $PAI_DIR/.env.

Workaround applied:

# Added to manage.sh after SCRIPT_DIR definition
PAI_DIR="${PAI_DIR:-$HOME/.claude}"

if [ -f "$PAI_DIR/.env" ]; then
    set -a
    source "$PAI_DIR/.env"
    set +a
fi

Related issues filed:

• Bug: pai-voice-system voice-personalities.json path mismatch #393 - voice-personalities.json path mismatch
• Bug: pai-voice-system server.ts doesn't resolve voice_id from personality config #394 - voice_id resolution bug
• Architecture: VoiceServer location in ~/.claude/ conflates config with runtime #395 - VoiceServer location architectural concern

The broader issue is that there's no consistent convention for where .env lives and how scripts should load it. Each pack/script handles it differently (or not at all).

[kaimagnus]

Thanks for flagging this! The ENV path inconsistencies were addressed in the v3.0 restructure (now released). v3.0 standardizes environment variable handling with $PAI_DIR throughout. Please upgrade to v3.0.