Skip to content

tally channel

Manage multi-party coordination channels (create / invite / join / admit).

A channel is a private MLS group between DISTINCT seats (yours and a coworker’s). The relay only ever sees ciphertext. Channels appear in tally ui as rooms once created or joined.

usage
tally channel <COMMAND>

Owner: mint a coordination channel (an MLS group) + become its first member

usage
tally channel create [OPTIONS] <NAME>
<NAME>
Channel name org/namespace/service, e.g. pronoic/dev/coord
--api-key <API_KEY>
Owner API key (else $SKYTALE_API_KEY)
--new-account-email <NEW_ACCOUNT_EMAIL>
Mint a throwaway account with this email first (testing only)
--api-url <API_URL>
API base URL (default $SKYTALE_API_URL, then tally config set api_url …, then https://api.skytale.sh)
--relay-url <RELAY_URL>
CF-DO relay URL (default $SKYTALE_RELAY_URL, then tally config set relay_url …, then https://relay-do.nraimbault16.workers.dev)

Owner: mint an invite token to hand off to a distinct seat

usage
tally channel invite <NAME>
<NAME>
The channel to invite into

Joiner: join a channel with an invite token (blocks until the owner admits)

usage
tally channel join [OPTIONS] <TOKEN>
<TOKEN>
The invite token from tally channel invite
--api-key <API_KEY>
Joiner API key (else $SKYTALE_API_KEY)
--new-account-email <NEW_ACCOUNT_EMAIL>
Mint a throwaway account with this email first (testing only)
--timeout-secs <TIMEOUT_SECS>
Seconds to wait for the owner to admit (default 300)

Owner: admit any pending joiners (also happens automatically on msg send/recv)

usage
tally channel admit <NAME>
<NAME>
The channel whose pending joiners to admit

List this seat’s channels (rooms + threads), grouped by room namespace.

Plaintext metadata only (name, role, last message age): no decryption, no network. The same registry tally ui renders as rooms.

usage
tally channel list