A "Hermes agent" assistant model talks to a Hermes Agent gateway's
OpenAI-compatible API server (streamed /v1/chat/completions), with Hermes URL
and key settings under Assistant. Hermes keeps the conversation: each
assistant session maps to one X-Hermes-Session-Id and only the latest user
message is sent. Faceclaw's own tools are not offered to it, and its reasoning
stream is not shown on the glasses. See notes/hermes-assistant.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- "Whisper server (self-hosted)" transcription provider for OpenAI-compatible
Whisper servers (vLLM, speaches, LocalAI) over plain HTTP batch requests,
with URL, model, language and key settings (Voice). Pause-ended spans are
one request each, finalized in audio order, with provisional text while a
span is open. See notes/whisper-server.md.
- Transcribe (and other continuous capture) works on iOS with a cloud or
Whisper-server provider; push-to-talk shares a running capture.
- Transcribe saves each session's audio as transcribe-<time>.wav in Downloads
(setting "Save Transcribe audio", on by default), written as it is captured
so a crash leaves a playable file; a saved transcript uses the same stamp.
- Calculator stops continuous listening when its window closes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Implements the Even R1 ring's health-sync protocol, reverse-engineered from
Bluetooth HCI snoop captures of Even's own app and confirmed field-by-field
against that app's CSV export. Answers the open question in issue #22, and in
notes/apps.txt, about where interpretation happens: it happens ON THE RING.
Sleep arrives already classified into stages; the phone does no inference.
RingProtocol.java: 15-byte header, 2-byte command id, CRC-32C (non-reflected)
over the frame body, fragment reassembly, and decoders for all five record
types -- heart rate, HRV, SpO2, sleep and steps. Hourly types share the shape
[hour_index][avg][max][min]. Steps are 10-minute buckets counted from the
record's anchor. RingProtocolSelfTest.java covers the codec against captured
bytes.
Three traps are documented in the code because each one costs days and a
reviewer "tidying" any of them would silently break the sync:
1. The 00:08 handshake frame is the ONE request whose payload carries no
nonce -- it is exactly 3f 01 01. Measured across 46 real writes with zero
exceptions: the 3-byte form is always answered, the 5-byte form never is.
Prepending a nonce makes the ring discard the frame and then ignore every
subsequent request on that connection.
2. The ring holds only one health type's response in flight. Requesting the
next type before the previous type's DATA arrives silently drops it, and a
lost race appears to discard that backlog PERMANENTLY rather than delaying
it. requestRingHealth() is therefore response-paced, not sleep-paced, and
ACKs each page as it lands.
3. HEALTH_COMMANDS mirrors the order Even's app uses. Whether the ring cares
is untested, and matching is the cheap way not to find out the hard way.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Phase 3 of the voice-assistant design: assistant.backend=external routes
utterances over a dial-out websocket to faceclaw-agent-bridge (an OpenClaw
plugin on the user's machine). The phone serves its ToolRegistry as MCP on
the same socket, with proactive gating and rate limiting enforced locally.
New Assistant settings section with backend/bridge settings.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XCdkQyB3RUVPTuEmhxVEdp