Skip to content
quoxcli

Find what Quox cannot see

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

What can't Quox see?

Which sources are reporting, which went quiet, and where the plan and the evidence disagree.

What you get: the difference between “all clear” and “nothing reported”. A quiet dashboard can mean nothing happened, or that something stopped telling you. This tells you which.

Ask Quox

Section titled “Ask Quox”

Ask what it cannot see, in your own words:

quox · talking to Quox

What can't LUCID see right now? How many of its sources are live, out of how many it expects?

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 7ms

◐ LUCID │ situation ✔ LUCID │ situation │ 0 silent, 1 failing, 0 unwired · 1.3s

⛓ AEE │ envelope opened · stream_success

LUCID has 32 of its 33 expected sources live, and the missing one is InboxQ.

Why InboxQ is dark: one mailbox is connected, but background sync is switched off, so it
has never synced in the background. LUCID can't tell you whether any mail needs you.
Its "nothing new in messages" line therefore only means it can't see any, not that your
inbox is clear.

What else it reported: no silent, unwired or stale feeds. The only gap is InboxQ.

Fix: turn on Background sync in the InboxQ settings. The API call is  PUT 
/api/v1/inboxq/settings {"syncEnabled":true} . To sync once by hand, run  quox mail sync
<accountId> . I haven't changed anything.

12.8s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.0, 16 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 16 Oct 2026 · test report mvb36m

Quox read LUCID’s own account of its sources: how many are live, which are not connected, and what each gap hides. A quiet “nothing needs you” is only as wide as what LUCID can see, and it says so.

Do it yourself

Section titled “Do it yourself”
lucid blind 
quox lucid blindSOURCESSOURCE        STATE        LAST HEARD  NOTEinboxq        never heard              expected, has never reportedapprovals     live         23s agobuild         live         22s agocontainers    live         17s agoruns          live         10s agosecurity      live         10s agosites         live         20s ago DOESN'T ADD UP (4)1. 100 streams say in progress but nothing is moving   Claimed   100 streams are IN_PROGRESS   Observed  Untouched for 7 days or more; no open session and no commit in the last 7 days mentions them   Why       The plan says work is happening; the evidence says it is not, so the plan may be wrong.   Settle    Resume them, or move them to blocked or planned.
From a real run on our own install. Trimmed to a few sources and one finding.
  • silent: the source used to report and stopped. Something may be broken.
  • never heard: the source is expected but has never reported, usually because it is not set up yet.
  • Doesn’t add up: places where what is claimed and what is observed disagree, with the evidence and how to settle it.

What just happened

Section titled “What just happened”

LUCID compared what it expects to hear from with what it actually heard, and checked claims (like a plan’s status) against evidence (like recent work). That is how a missing signal shows up as a finding instead of as silence.

Check it yourself

Section titled “Check it yourself”

quox lucid feeds lists the feeds the same way. quox lucid ask "why is inboxq silent?" asks LUCID about any of it in plain words.

Undo

Section titled “Undo”

Nothing to undo: this only reads.

Next

Section titled “Next”