Found while reviewing #37.
ccx log <project> filters by project name. When the name matches
nothing, the output is indistinguishable from a genuinely empty window:
$ ccx log zzz-no-such-project --scope today
ccx log · Today · America/Los_Angeles
2026-08-19 00:00 to 2026-08-20 00:00 · source log files 0 · records 0
No log records in this scope.
Same shape appears when a session id is passed by mistake
(ccx log 736a7bac --kind prompt), which is an easy slip since
view, trace, and related all take a session there.
Expected: a one-line warning on stderr — ccx: no project matches "zzz-no-such-project" — and, when the argument looks like a session
id, a pointer to the command that does take one. Same class as the
friction fixed in 0fcfa62 ("session lookup recovery, honest
timestamps, one-line warnings"); this path was missed.
Found while reviewing #37.
ccx log <project>filters by project name. When the name matchesnothing, the output is indistinguishable from a genuinely empty window:
Same shape appears when a session id is passed by mistake
(
ccx log 736a7bac --kind prompt), which is an easy slip sinceview,trace, andrelatedall take a session there.Expected: a one-line warning on stderr —
ccx: no project matches "zzz-no-such-project"— and, when the argument looks like a sessionid, a pointer to the command that does take one. Same class as the
friction fixed in 0fcfa62 ("session lookup recovery, honest
timestamps, one-line warnings"); this path was missed.