Skip to main content
Sessions keep your Agent conversations available for review. Open an Agent’s Sessions for its history, or Console > Sessions to look across Agents. Connected Agents upload history from their computer after setup; Cloud Agents show their history through Clawdi.

​
Find a conversation

  1. Open Console > Sessions.
  2. Search for words from the conversation and narrow the results by Agent or activity.
  3. Open a result to read the matching messages.
  4. Within a Session, use search and the next/previous controls to find another match.
Hermes Sessions list with synthetic conversation titles and dates. An Agent’s Sessions page keeps its conversation history together. View full-size image Search covers visible messages and summaries. Private reasoning and tool payloads are excluded.

​
Share the useful part

Open a Session and choose the smallest amount of content your recipient needs:
  • Share at the top: the current conversation.
  • Share conversation to here on a message: the conversation up to that point.
  • Share response on an Agent response: just that response.
Create the link, then open it in a signed-out window to check what the recipient will see. New links are snapshots; later messages stay outside that snapshot.
Anyone with an active link can read the shared content. Check for private information before sharing. Project membership and Session links are separate.

​
Turn off access

Open Sessions > Shared Session links, or the Session’s Share dialog, to review and turn off active links. Older Live links can include later uploads, so review those too. Files someone already downloaded remain independent copies.

​
Missing a conversation?

For a Connected Agent, check that its computer is online and background sync is running. For a Cloud Agent, check the Agent’s status in Clawdi. The advanced steps below cover sync checks and exporting a private copy.

​
Sync a Connected Agent Session

Connected Agent setup installs the background daemon by default. Check it before doing a manual backfill:
Preview the upload, then upload the Session metadata and content available to your CLI:
Replace codex with claude_code, hermes, openclaw, pi, or opencode when appropriate. Omitting --project uses the current directory for a normal push; use clawdi push --help before widening a backfill with --all.
The command reports new, updated, or unchanged Sessions. They appear under Sessions in the dashboard and on the relevant Agent page.
For a Cloud Agent, open that Agent’s Sessions section or the global Sessions page. Do not run local push for a remote runtime; use the status shown on the Cloud Agent page. See Cloud Agents.

​
Review and find a Session

Open Sessions in the dashboard. Search visible user and assistant messages, summaries, folders, or Session IDs, then narrow results with Agent and activity filters. Results show matching context; opening a message match takes you to that message.Within a Session, use transcript search and its next/previous controls to move between highlighted matches. Read messages and Agent activity in chronological order or jump to the latest messages. Private reasoning and tool payloads are excluded from search.To find and read uploaded Sessions from the CLI:
Use the Cloud Session ID returned by search. session list lists local Sessions; search and read use the uploaded Cloud copy.If a row exists but its messages do not, rerun the focused push. Metadata can arrive before a content upload succeeds, and the next push retries content that is not in sync.

​
Mirror synced Sessions onto another computer

For a Connected Agent installation on the destination computer:
pull writes a Clawdi-managed local mirror. It does not insert downloaded conversations into the Agent software’s native Session history or make them resumable there.
Use clawdi config paths to inspect the local paths for your installed CLI version instead of relying on a hard-coded directory.

​
Share one Session

Choose the smallest amount of conversation the recipient needs:Create the link, copy it, and open it in a signed-out window to verify the intended content. Each new link is a snapshot: later messages are not added. Sharing includes visible conversation content, excluding private reasoning, system messages, and tool payloads.
Anyone with an active link can read its shared content. Review visible messages for sensitive text, file paths, and quoted secrets before sharing. Session sharing is independent from Project sharing.

​
Share from the CLI

Read the uploaded Session before publishing a link:
The second command asks for confirmation. For a deliberate non-interactive publication, add --yes. To limit the snapshot, use a message’s position from the read output:
Positions identify messages in the uploaded Session; do not substitute a row number counted in the browser. --response must select an Agent response. Use either --through or --response, or omit both for the current whole conversation. Review the returned link before sending it to anyone.Sharing requires account-level authorization. An Agent-bound or restricted key cannot create public links on the account’s behalf.Open Sessions > Shared Session links to review, copy, open, or turn off active links across Sessions. You can also manage a Session’s links in its Share dialog.Older Live links can include later uploads. New Snapshot links retain only their chosen content. Turn off an older live link if you no longer want future uploads to be accessible through it; creating a snapshot does not turn off other links.From the CLI:
Use the ID and kind from the listing. For an older live link, add --legacy and use that link’s listed ID, not the original Session ID. Listing is paged; advance --page to review the remaining active links.

​
Export as Markdown or JSON

To export your uploaded Session without making it public:
These commands write the export to standard output and do not create a share link. Review the local file before distributing it.For an existing public link, open its shared page and use More options to copy its Markdown or JSON URL. You can also append .md or .json to the exact share URL:
A snapshot link’s share ID is distinct from the original Session ID. Copy the returned link rather than constructing it from a Session ID. Both formats respect the link’s selected content and access state.
Turning off a link cannot recall a file someone already downloaded or copied. Treat exports as independent copies.
Run clawdi session --help, clawdi push --help, and clawdi pull --help for the filters available in your CLI version. See the Clawdi CLI for dry-run and JSON conventions.
Last modified on September 10, 2026