OpenHome / Product & developer experience
← All priorities
Priority 05

Give CLI users dependable outcomes and recovery

Local creation, upload, acknowledgement and completed results are not consistently distinguished.

Recommended next move

Make outcomes inspectable, render final text accurately and give failures a recovery path.

What I observed

The reviewed CLI paths did not consistently distinguish local creation from upload, acknowledgement from completed results, or no response from command success. In particular, the shipped README describes create as auto-pushing, while a no-trigger run creates only a local scaffold, prints that it was not pushed and exits 0; this is a documentation and automation-contract ambiguity, not evidence of hidden data loss or a failed authenticated upload. A comparative gap versus mature coding CLIs is the lack of root build/readiness/authentication diagnostics. Offline probes showed an early acknowledgement being treated as the answer and an exception path bypassing cleanup. A separate terminal-rendering probe reproduced leftover characters when a shorter streamed line replaced a longer one, and omission of differing final text.

Why it matters

Developers and automation need to know what actually completed and what to do next. Ambiguous success and corrupted display text make a functioning workflow difficult to trust or troubleshoot.

Recommended behavior

Report local-created, uploaded, committed and executed outcomes separately. Provide inspectable build, account context and loaded revision without revealing credentials. Distinguish acknowledgements from terminal invocation results. Give timeouts and failures useful exit codes and recovery instructions. Render streamed and final text accurately, and restore normal conversation after exceptions.

Acceptance

Test local-only and upload-requested commands separately. Confirm exit status and structured output describe the requested operation. Exercise a multi-output Ability, timeout, cancellation and exception. Verify final results are not replaced by early acknowledgements; shorter streamed updates leave no stale characters, and final corrections are displayed. Verify a subsequent normal conversation still works after failure.

Evidence limits: C01 is a comparative agent-readiness observation, not a broken advertised feature. C04 is a documentation and automation-contract ambiguity: the interactive message discloses the local-only result, and no customer-work loss or hidden upload failure was demonstrated. Offline completion and cleanup probes do not establish a permanent hosted hang. The rendering mechanism was reproduced; it does not conclusively explain the user’s original duplicate greeting. Findings concern the reviewed CLI build, not every release. Evidence references: C01, C03–C04, C06, X04, X07, L03.