Releases: spaceamoeba-t/tapq
Release list
v0.5.0-beta.2 — live voice loop
TapQ's voice path becomes a live conversation loop. The earbud IMU yields a wearer-speech signal — jaw- and skull-borne vibration only the wearer can produce — with the calibration, capture, and replay tooling to study it, and the cloud voice backend gained the transport to use it live.
Highlights
--voice-backend openai-realtimenow actually hears (microphone pump) and speaks (backend audio playback), over conversation-scoped sessions with sticky fail-through to the on-device Apple stack.--wearer-gate— IMU wearer attribution for voice commands: bystander speech is rejected, and every degraded state fails open. Default off.--imu-turn-control— speech-end endpointing and barge-in over the agent's audio. Default off.--voice-freeform— free-form spoken answers to selections and multi-option stop questions, with mandatory read-back confirmation. Tool approvals stay strictly binary.- Wire protocol v4 adds
free_text; the broker accepts v3 and v4, so installed hook shims keep working — reinstall them (tapq integration claude|codex install) to receive free-form answers.
Every IMU-driven feature ships default-off with provisional thresholds until the capture study lands. The flagless default path is byte-identical to 0.4.0-beta.1 apart from the voice-negation fix.
Note: ignore the stray v0.5.0-beta.1 tag — it points at a commit that never landed on main and the repository's tag rules make it immutable; this release supersedes it.
Full details in CHANGELOG.md.
TapQ 0.4.0-beta.1
TapQ 0.4.0-beta.1 is a source-only prerelease focused on broader Codex integration and more reliable voice capture when AirPods routes change.
Highlights
- Expanded the Codex adapter with hands-free single-choice
request_user_input, native approvals forBash,apply_patch, and MCP connector calls, completion and final-question handling, opt-in root-turn steering, and compatibility diagnostics. - Kept unsupported Codex requests fail-open so the native Codex selector or approval flow remains authoritative.
- Protected MCP argument privacy: connector values may reach the local on-device reasoner, but are not spoken, diagnosed, cloud-sent, or persisted in reasoner review logs.
- Reworked voice capture to survive Bluetooth route and media-service changes. An unavailable route disables voice for that interaction window and is retried with fresh state on the next window.
- Generic English voice selection now prefers a downloaded premium or enhanced Samantha while preserving explicit voice identifiers and regional language choices.
- Restructured the documentation and added signed, source-only release safeguards.
Upgrade note
Existing Codex users must rerun:
tapq integration codex installThen open /hooks in Codex and review and trust all four TapQ registrations.
Compatibility
- Full hands-free runtime: macOS 14 or newer.
- Linux: portable core and management CLI only; no live AirPods runtime.
- Codex lifecycle-hook contract floor:
0.142.5. - Structured questions, MCP approvals, and steering contracts target Codex CLI
0.146.0. In0.146.0, Plan mode is the reliablerequest_user_inputsurface; default-mode availability depends on the Codex feature state. - Automated Codex qualification runs the real hook process against a local broker, but is not an authenticated model-level end-to-end test. Hosted Codex Cloud tasks are outside this integration.
- Wire protocol remains version 3 and is compatible with 0.3.0-era hooks and brokers, though reinstalling the Codex hooks is required to activate the expanded coverage.
- Distribution: source only. This Release contains GitHub-generated source archives and no prebuilt, signed, or notarized application binaries.
See the 0.4.0-beta.1 changelog for complete details.
TapQ 0.3.0
Historical source-only release corresponding to the TapQ 0.3.0 milestone dated 2026-07-29. No signed or prebuilt binaries were published. See the 0.3.0 changelog.
TapQ 0.2.0
Historical source-only release corresponding to the TapQ 0.2.0 milestone merged on 2026-07-27. No signed or prebuilt binaries were published. See the 0.2.0 changelog.