OpenHome / Product & developer experience

Three review lenses

I grouped findings into three lenses; a finding may appear in more than one.

Where it happens and why it matters

The product surface (audio, conversation, user interface or developer workflow) says where an experience occurs. These three lenses describe how it affects people and product credibility.

Counts overlap because one finding may fit multiple lenses. They do not represent severity or confidence. See each entry’s priority, status and evidence class in the full findings index.

User experience / developer experience

77 entries · a cross-cutting view, with no severity or confidence implied.

Three issue highlights

X01 · P1 · open

Existing connection invokes Ability after acknowledged disable; fresh connection respects disable

Existing connection invokes Ability after acknowledged disable; fresh connection respects disable; September 21 retest read enabled=false before retrigger and after calculation 42 in the existing session. Fresh-session trigger did not return the fixture greeting. Shared web-demo follow-up observed two new invocations after disable, returning 42 and 17; a fresh demo session did not show fixture execution. Follow-up linked the shared-session initialization credential to the distinct user account U, resolving the earlier client-side identity ambiguity.

Evidence: hosted observation

X02 · P1 · open

Explicit no-send instructions fail across Gmail turns and a real email is delivered

Existing marketplace Gmail sent an email after a conversation-wide no-send instruction and a second turn requesting wording only and repeating do not send. Recipient Gmail independently verified sender, subject and Inbox delivery. Earlier single-turn negative cases entered Gmail without observed delivery; synthetic persistent-write and calculation cases remain separate evidence.

Evidence: hosted observation

All linked findings

Polish

31 entries · a cross-cutting view, with no severity or confidence implied.

Three issue highlights

W34 · P2 · open

New Agent response exposes raw Markdown markers

A supplied screenshot of a new Agent shows literal heading markers, asterisks and list separators in the visible reply. This makes the answer harder to scan and can expose formatting syntax as content. The screenshot establishes this response only, not prevalence or cause.

Evidence: user screenshot and report

W35 · P1 · open

Markdown-heavy replies are reported as difficult to understand in speech

Gabriel supplied three audio examples and reports that the speech output does not turn Markdown-heavy reply text into comprehensible spoken language. The set includes one approximately 55-second clip and two clips of approximately 8 and 7 seconds. These user-supplied examples warrant a core conversation-quality investigation; this pass did not independently replay or transcribe them.

Evidence: user supplied audio and report

W36 · P2 · open

One supplied long speech sample reportedly starts with a distorted voice

Gabriel reports a severely distorted voice at the beginning of the approximately 55-second Markdown-to-speech example. Keep this onset-quality symptom distinct from the broader Markdown intelligibility concern until the initial audio segment and later speech are compared.

Evidence: user supplied audio and report

All linked findings

Documentation mismatch

37 entries · a cross-cutting view, with no severity or confidence implied.

Three issue highlights

D17 · P2 · open

Local validator accepts constructs rejected by hosted validation

The public validator accepted the SDK fixture; hosted upload rejected inspect and getattr with HTTP 400. This is validator parity friction, not evidence those constructs should be allowed or that SDK methods fail. Fixture updated to use explicit documented calls.

Evidence: offline validation and hosted rejection

Y15 · P1 · open

CLI marketing routes new users to the archived product

Live CLI announcement recommends npm client plus JSON/MCP/session-token features. The supported current CLI is the separate Python client; do not transfer either implementation’s feature claims to the other.

Evidence: documentation conflict

All linked findings