Save a contact someone shared with you (a Contact card) as a local peer. agent-talk does NOT auto-import — review staged cards and import only ones from a peer you trust. `<user>` is this session's user directory (absolute path; from init).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Importing adds a peer to your address book — a trust action. Do not blanket-import. Review first, then import selectively, only cards from a designated/trusted peer. retalk re-checks any keys against the fingerprint and refuses a tampered card with PIN MISMATCH (saving nothing).
Cards that peers shared arrive via receive and are staged in a
contact-inbox (not yet saved as peers).
Review what's staged (imports nothing):
retalk import --inbox --list --json --dir "<user>/identity"
Import just the one you trust (optionally rename):
retalk import --inbox <staged-name-or-id> --dir "<user>/identity"
retalk import --inbox <staged-name-or-id> --as <nickname> --dir "<user>/identity"
Import a card handed to you directly (JSON argument or stdin):
retalk import '<card json>' --dir "<user>/identity"
Avoid retalk import --inbox with no name (it imports all staged cards)
unless you've reviewed them. A keyless card imports as unverified (verified on
first contact).
Always prepare a ready-to-paste reply that confirms your own fingerprint, and send it back over a channel the relay doesn't control (Slack, email, in person) — every time someone shares a contact with you. The relay is untrusted, so an out-of-band fingerprint is what lets the other side pin your keys and trust it's really you; sharing only over the relay leaves that half open.
retalk id --invite-message --as <name-they-save-you-as> --dir "<user>/identity"
(Or just your card: retalk id --card --dir "<user>/identity".) For a peer who's
already set up, the part that matters is your fingerprint + "add me as <name>" so
they can verify/pin you. Do this even after you've imported them.
<user>= this session's user directory (absolute path; resolved at init).
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.
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.
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.