Access

Dispatch on arguments

Parse $ARGUMENTS (space-separated). If empty or unrecognized, show status.

No args -- status

1. Read ~/.claude/channels/xmpp/access.json (handle missing file).
2. Show: policy, allowFrom count and list, delivery config (ackMessage, textChunkLimit, chunkMode).

allow <jid>

1. Read access.json (create default if missing).
2. Normalize <jid> to lowercase.
3. Add to allowFrom (dedupe -- skip if already present).
4. Write back.
5. Confirm: who was added. Note: takes effect immediately, no restart needed.

remove <jid>

1. Read, filter allowFrom to exclude <jid> (case-insensitive match), write.
2. Confirm: who was removed.

policy <mode>

1. Validate <mode> is one of allowlist, disabled.
2. Read (create default if missing), set policy, write.
3. Confirm with explanation:
   • allowlist: only JIDs in allowFrom can reach Claude
   • disabled: all inbound messages are silently dropped

set <key> <value>

Delivery/UX config. Supported keys:

• ackMessage: string -- text to send on receipt. Empty string "" disables. Example: received or an emoji.
• textChunkLimit: number -- max chars per outbound chunk. Default 4000.
• chunkMode: length | newline -- split strategy. newline prefers paragraph boundaries; length does hard cuts.

Validate types:

• ackMessage: any string is valid
• textChunkLimit: must be a positive number
• chunkMode: must be length or newline

Read, set the key, write, confirm.

Implementation notes

• Always Read the file before Write -- the server may be running and reading it. Don't clobber with stale data.
• Pretty-print the JSON (2-space indent) so it's hand-editable.
• The channels dir might not exist if the server hasn't run yet -- handle ENOENT gracefully and create defaults.
• JIDs are bare JIDs (e.g. [email protected]), not full JIDs with resources.
• JID comparison is case-insensitive per RFC 7622. Store lowercase.
• No pairing flow (unlike Telegram) -- JIDs are known upfront. The user adds them directly with allow <jid>.
• Changes take effect immediately -- the server re-reads access.json on every inbound message. No restart needed.