Founder tasting feedback on Patch A (#470), 2026-07-02.
On pi.ai neither the in-chat voice dropdown (PiVoiceMenu) nor Pi's Voice settings grid (PiVoiceSettings) shows the "More voices" row, so there is no discoverable path from Pi to the extension's voice catalog.
Why: the door only renders when the shortlist actually hides voices (curated.hiddenCount > 0 in VoiceSelector.populateVoices). Pi's SayPi catalog is 3 voices, under the cap of 5, so nothing is hidden and the door never appears. PiVoiceSettings is uncapped, so same outcome.
Intent has shifted: the door is a navigation affordance to the settings catalog, not just an overflow indicator. It should render on these surfaces regardless of whether the cap hid anything (Claude's menu already shows it because its catalog exceeds the cap).
Work:
- Render the door on capped surfaces even when
hiddenCount === 0.
- Add the door to PiVoiceSettings' grid too (uncapped surface).
- Keep the idempotency guarantee (no duplicate doors on repeated populates).
Part of the #471 feedback batch.
Founder tasting feedback on Patch A (#470), 2026-07-02.
On pi.ai neither the in-chat voice dropdown (PiVoiceMenu) nor Pi's Voice settings grid (PiVoiceSettings) shows the "More voices" row, so there is no discoverable path from Pi to the extension's voice catalog.
Why: the door only renders when the shortlist actually hides voices (
curated.hiddenCount > 0inVoiceSelector.populateVoices). Pi's SayPi catalog is 3 voices, under the cap of 5, so nothing is hidden and the door never appears. PiVoiceSettings is uncapped, so same outcome.Intent has shifted: the door is a navigation affordance to the settings catalog, not just an overflow indicator. It should render on these surfaces regardless of whether the cap hid anything (Claude's menu already shows it because its catalog exceeds the cap).
Work:
hiddenCount === 0.Part of the #471 feedback batch.