Skip to main content
A Session is conversation history produced by an Agent. The object has the same meaning for Connected Agents and Cloud Agents, while collection and sync steps differ by run path. See Core concepts.

​
Sync a Connected Agent Session

Connected Agent setup installs the background daemon by default. Check it before doing a manual backfill:
Preview the exact scope, then upload supported Session metadata and content:
Replace codex with claude_code, hermes, or openclaw 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 the Cloud Agent overview.

​
Review and find a Session

Open Sessions in the dashboard. Search by summary, folder, or Session ID, then use the available Agent and activity filters. Select a Session to read its uploaded messages and metadata. 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

  1. Open the Session detail page in the dashboard.
  2. Choose Share and turn on Public access.
  3. Copy the canonical link.
  4. Open the link in a signed-out window to verify the intended content is visible.
Anyone with an active link can read the Session. Review messages, file paths, prompts, tool output, and other sensitive context before enabling Public access. Session sharing is independent from Project sharing.
To revoke anonymous access, return to Share and turn off Public access. The stable URL still exists, but it no longer serves the Session anonymously.

​
Export as Markdown or JSON

While Public access is on, the Share panel shows Markdown and JSON format links. Copy the format you need, or append .md or .json to the canonical public Session URL:
Markdown is convenient for reading or Agent ingestion; JSON preserves a structured message export. Disable Public access when the recipient no longer needs the URL.
Revoking the URL cannot recall a file that someone already downloaded or copied. Treat exported files as independent copies and share them through an appropriate secure channel.
Run clawdi session --help, clawdi push --help, and clawdi pull --help for the exact filters available in your CLI version. See the CLI guide for dry-run and JSON conventions.
Last modified on August 2, 2026