Therapist v0.1.2 — guided setup fix
Pre-releaseTherapist v0.1.2 — guided setup fix
This patch fixes the next guided-setup failure exposed after the macOS terminal correction in
v0.1.1. Therapist passed newly constructed Choice objects as defaults for yes/no prompts.
Questionary requires the default object to be present in the choices, so setup raised ValueError
when it reached the Telegram question.
All yes/no menus now share one helper that reuses the selected object from its actual choice list.
The macOS pseudoterminal fix from v0.1.1 remains included.
Install or update
macOS or Linux:
curl -LsSf https://raw.githubusercontent.com/matteodante/therapist/main/install.sh | shWindows PowerShell:
powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/matteodante/therapist/main/install.ps1 | iex"For a reproducible installation pinned to this patch, replace main with v0.1.2 in either URL.
Re-running the installer preserves encrypted application data and the shared model cache.
Scope and safety
Therapist remains an experimental, single-adult-user, self-hosted AI agent for reflection. It is not
therapy, diagnosis, medical advice, emergency care, clinical validation, or human monitoring.
Supported alpha conversation uses the CLI or one private allowlisted Telegram bot with a personal
ChatGPT Plus/Pro account through experimental Codex OAuth.
Local archives, memory, credentials, and semantic indexes remain encrypted on the host. ChatGPT
receives the content and selected context required for inference; Telegram also receives transported
messages when enabled. There is no hosted Therapist service or product telemetry.
Verification
- A regression test constructs the real Questionary prompts through the supported setup path.
- Every yes/no default is checked by Questionary against its actual choice list.
- macOS CI retains the real
prompt_toolkitpseudoterminal smoke test. - The full deterministic suite, CI, CodeQL, dependency audit, packaging checks, CycloneDX SBOM,
checksums, and build/SBOM attestations run on the release commit.
The experimental Codex backend and all limitations documented for prior alphas remain. Use synthetic
data in public issues and private vulnerability reporting for security reports.