Reconcile this identity with the relay — republish keys, replenish one-time keys, rotate the fallback, and resend unacknowledged mail. Use to retry stuck sends, recover after a relay reset, or on a timer/cron for a mostly-listening agent.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
retalk sync --dir "<user>/identity" --passphrase-path "<user>/passphrase"
# -> {"unclaimed","republished","replenished","fallback_rotated","resent"}
send runs this first and receive never resends, so use sync to retry stuck
outgoing mail without a new send (good for cron). Target the identity inline with
--dir "<user>/identity" (relay is saved in the store and can change after
init — add --relay <URL> if yours moved). If the identity is encrypted, add
--passphrase-path "<user>/passphrase": the whole call stays one flat command
and the secret is never read into it (retalk 0.3.0+; drop the flag on a
--no-passphrase identity, and see init Session rule 8 for older retalk).
Cron, where the same rule matters most because nobody is watching:
*/5 * * * * retalk sync --dir "<user>/identity" --passphrase-path "<user>/passphrase"
<user>= this session's user directory — an absolute path resolved at init (e.g.~/.agent-talk/users/alice(global) or<project>/.agent-talk/users/alice(local)). Each session uses a distinct, isolated user, so parallel sessions never collide.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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).
中文简介正在准备中。当前显示原文说明。
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).
中文简介正在准备中。当前显示原文说明。
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).
中文简介正在准备中。当前显示原文说明。