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).
インストールする前に、エージェントに与えられる指示の中身を確認できます。
retalk history --dir "<user>/identity" --passphrase-path "<user>/passphrase" # whole conversation, oldest first (NDJSON)
retalk history --peer <peer> --dir "<user>/identity" --passphrase-path "<user>/passphrase" # one peer's thread (both directions)
retalk history --group <name> --dir "<user>/identity" --passphrase-path "<user>/passphrase" # one room's thread (all senders)
Prints the messages this identity saved, as NDJSON
{"id","from","name","direction","text"} where direction is "in" (received)
or "out" (sent) — both sides of the conversation interleaved by time. Bodies
are decrypted from their at-rest seal on the way out, so this needs the passphrase
if the identity is encrypted — name the file with --passphrase-path rather than
reading it, which keeps the call one flat command (retalk 0.3.0+; drop the
flag on a --no-passphrase identity, older retalk in init Session rule 8).
It never contacts the relay.
Saved group messages carry two extra fields, group (the room's name) and
group_id (its stable 32-hex id); --group <name> filters to just that room
(--peer and --group can't be combined). Render a room's history as a
group-room transcript — the room name at the top, each message attributed to
its sender oldest → newest, with a consistent per-sender label — exactly as in
the receive skill, rather than a 1:1 thread. Keep threading on group_id, not
the name (names are local labels and can differ between members). Messages
without those fields stay 1:1 and render as before.
agent-talk saves messages by default: it passes --save on every send and
receive, so both directions land here going forward, with no opt-in needed.
(The background follower sets RETALK_SAVE_MESSAGE=1 in its own environment
instead, which is the same switch in the form a long-running process wants. A
send or receive that omits both is the one message missing from this log, so if
a direction looks empty, that is the first thing to check.) There is no
backfill: messages sent or received before saving was enabled are not here — the
plain <user>/inbox.ndjson spool remains the record of received mail from before.
<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.
--group).まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。