Repository navigation
Cleared CLI 0.2.2
Fixes payments check --customer pagination: --limit and --cursor can now be
combined with the required invoice/customer selector. Exactly one selector remains required.
Healthy hybrid invoice reads, including normal dueAt reconciliation, now report complete
results for invoice lists, customer payment checks, and dashboard latest invoices. Explicit
degradation, failure notes, unconfirmed IDs, unavailable reads, and bounded chain fallback
retain their existing partial/error handling. This change corrects CLI classification; it
does not repair API indexer synchronization metadata.
Ordinary CLI process tests now use a clean environment and synthetic authentication to
avoid reading a developer's credentials or inheriting API origins and proxy settings.
Dedicated native Keychain and Secret Service tests retain their explicit native-store coverage.
Included from 0.2.1
Fixes OAuth loopback login handling of empty TCP/preconnect connections and validated
unrelated plain GET requests. These harmless connections no longer end login before a valid
callback arrives. Each connection's header read is bounded by a three-second budget and the
original login deadline; malformed callbacks, incorrect Host/state, and OAuth parameters on
alternate paths remain fatal.
The empty-connection failure was reproduced in a production-process regression test. The
cause of the first intermittent live login failure remains unproven; this patch does not
claim that browser preconnect traffic caused that incident.
Browser OAuth login with PKCE, scoped consent, session refresh, redacted authentication
status, logout, and API-key authentication remain available.
OAuth credentials use macOS Keychain or Linux Secret Service. An unavailable secure store
fails closed with SECURE_STORE_UNAVAILABLE; there is no plaintext-file fallback.
Headless environments can continue to use an explicitly supplied API key.
OAuth requires a compatible deployed Cleared API and consent web page with OAuth enabled.
Invoice issue/cancel additionally require an active server signer; browser login does not
activate one. Existing API compatibility requirements for chain-aware protocol metadata and
coverage-aware dashboard statistics still apply.
Customer management, invoice issue/cancel/read, payment checks and links, dashboard,
protocol information, structured JSON output, and explicit mutation recovery remain supported.
See the bundled terms/notices and public README for configuration and supported targets.
macOS downloads are unsigned and unnotarized.