Conversations

lnk-<name> instructions [--json]

For an adapter whose contract says prompt: prints the system prompt its harness sends its model now, exactly, from what configure last kept and the agent's Home and own folder as they are; with --json, {"system", "sections": [{"name", "owner", "changes", "from", "bytes", "max", "cut"?}]}, each section of it in order. Runs in its home, Home and the own folder's instructions, skills and memory/ (the agent's notes) read, nothing else of the agent's, with no network. Read by lnk agent show --instructions.

lnk-<name> conversation <thread>

For an adapter whose contract says chats: prints conversation <thread> (telegram:42) as a person reads it, from its events wherever its harness keeps them (Link harness: link_store_contract::store::copy, what conversation.md holds). Runs as instructions does, the programs of the store drivers the agent's conversations are kept by read too. Read by lnk agent chat show.

lnk-<name> conversations move <way>

For the same adapters: moves each of the agent's conversations kept another way than <way> (its spec's [storage] conversations now: log, compact or a store driver's name) to that way, and prints each it moved. The agent is stopped. Runs as conversation does, its conversations written as its harness writes them. Read by lnk agent chat convert.

Typed Link conversations

A harness's contract may additionally advertise conversation_history and conversation_fork, false unless present. The types are generated from the remote spec.

• lnk-<name> conversations list --json: RemoteConversations, the agent's link: threads and whether it can fork them.
• lnk-<name> conversation <thread> --json: RemoteConversation, the user and assistant text with original sequence numbers and times.
• lnk-<name> conversations fork <thread> --before <seq>: RemoteConversation for a fresh thread, containing the immutable events before that owner's message, with its tool restrictions.

lnk agent chat list --json, lnk agent chat show <thread> --json and lnk agent chat fork <thread> --before <seq> run those commands inside the agent's confinement, with its store drivers. A harness lacking the capability is refused explicitly.