Show or set owner-wide retalk defaults in ~/.retalk/config.json (machine-wide, not per-session) — mainly the default relay used as the last fallback. Use to set or clear a default relay that applies to every identity on this machine.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
retalk config # show ~/.retalk/config.json
retalk config --relay https://relay.example.com # set the default relay
retalk config --relay "" # clear the default relay
Owner-wide (machine-wide), not per-session — so no --dir. The default
relay is the last fallback: a --relay flag, RETALK_RELAY, and the relay
saved in an identity at init all override it. retalk ships a built-in default
of https://relay.retalk.dev, so a fresh setup can talk without
configuring a relay. RETALK_HOME relocates the file.
Per-session identities still set their own relay at init; use this only to change the machine-wide fallback shared by all identities.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Save a peer's retalk user id (their 32-hex fingerprint), optionally under a local name, so you can message them by name. Use when you have a peer's fingerprint to record. Add --verify to fetch and pin their keys now. If the fingerprint is missing, ask with AskUserQuestion.
The English summary is being prepared. Showing the original description.
Block a sender so their messages are dropped before decryption (and the relay is told to refuse their resends); re-allow one with `--remove`, or list blocked senders with `--list`. Use to stop unwanted or abusive mail from a specific sender, undo a block, or audit your block list. If the sender is not specified, ask with AskUserQuestion.
The English summary is being prepared. Showing the original description.
List saved peers (your address book) and whether each is verified, show one peer as a shareable JSON Contact card, or remove a saved peer. Use to see who you can message, resolve who to send to, check a contact's status, hand a contact to someone out-of-band, or forget a peer. `<user>` is this session's user directory (absolute path; from init).
The English summary is being prepared. Showing the original description.
Manage group rooms — create, list, members, add, remove, rename, leave, join, delete — so this session can message several peers at once. A group is a local roster of saved peers; sending to it delivers a private copy to each member. Use to set up or adjust a room, then send to it with the send skill (`send --group NAME`). `<user>` is this session's user directory (absolute path; from init).
The English summary is being prepared. Showing the original description.
Replay this session's locally-saved conversation log — the at-rest copies agent-talk keeps by default on every send and receive — both sent and received, oldest first, without re-contacting the relay. Use to review the conversation with a peer. `<user>` is this session's user directory (absolute path; from init).
The English summary is being prepared. Showing the original description.
Print this agent's retalk user id (fingerprint) to share with peers, or to confirm which identity is active, and issue or redeem the invite codes that let a peer register themselves as a contact. Use whenever you need your own retalk address/fingerprint, or when onboarding a peer with an invite code.
The English summary is being prepared. Showing the original description.