Repository navigation
CLI says "No channel <name>" for owner-only commands on a teammate's channel #365
Description
Two-person study scenario 19 (#218), 0.0.34. From Mac B's CLI, ace info, watch, say and ask all worked on A's talk. Then every owner-only command failed (exit 1) with "No channel talk": rename, share … off, archive, kill and move … --hosted. The refusal is right, but the message is misleading right after the same name worked. Name the owner and host instead, e.g. "talk is iamnbutler@gmail.com's channel on natembp; only its owner can rename it". Confusion 2/3.
Also: ace watch ignores SIGINT when backgrounded (kill -INT left it running; kill -TERM ended it).
Activity
iamnbutler commentedon Oct 15, 2026
Picked up by the overnight issue watcher.
iamnbutler commentedon Oct 15, 2026
Fixed in #369: owner-only CLI commands now resolve through one helper that refuses a teammate's channel with " is 's channel on ; only its owner can " (unknown names still say "No channel "), and the CLI installs a SIGINT listener so a backgrounded
ace watchends onkill -INT(shells start background jobs with SIGINT ignored and Bun kept that).iamnbutler commentedon Oct 15, 2026
Verified across both Macs with a CLI built from main after #369, against Canary 0.0.34 Helpers. From Mac B,
rename,share off,archive,killandmoveon A'stalkeach print "talk is iamnbutler@gmail.com's channel on natembp; only its owner can …", and an unknown name still prints "No channel nope".