Runtime 0.8.12
Share selected sessions
Package selected sessions, sanitize and read the report, then send an encrypted bundle. Receiving runs checks before it imports anything.
Review before sending
Use a conversation id from the sessions API. Bundle writes a raw archive; sanitize writes a separate best-effort scrubbed copy and a local report. Read the bundle and report before sharing: unusual secrets and private prose can survive. Never send reports, mapping files or local review files.
$ rh memory bundle --session <conversation-id> --out raw.json$ rh memory sanitize raw.json --out sanitized.jsonCloud sharing uses device sign-in. Node account sign-in also uses the cloud’s device-code flow in 0.8.4. Approve the device code in your browser, then upload the sanitized bundle:
$ rh share login$ rh memory share sanitized.jsonThe CLI prints a share code. Send that privately to the recipient. Drops are age-encrypted, expire after seven days, permit one download and have a 64 MiB maximum. The CLI handles signing and encryption. Keep the code private.
$ rh share status$ rh share logoutReceive and review
$ rh memory receive <share-code> --dry-runA dry run writes no sessions; retain the same machine’s inbox for the import because the server download is single-use.
$ rh memory receive <share-code>Sanitized bundles are scanned for secrets and prompt injection. Findings import nothing, print a held: report and exit 3; ciphertext stays in the inbox. Review each finding and rerun with --session 1=skip or --session 1=hold-spans, repeating for each flagged session. --all=hold-spans replaces flagged spans. An import decision for secrets additionally needs force; do not bypass a report you have not reviewed. Raw ingest requires force and bypasses these checks. Prefer sanitized bundles. Command-line reference and Operations reference cover the decision flags and trust rules.
Cloud and team policy
Cloud features are on by default. To disable cloud sign-in, reporting, cloud update checks and the cloud drop box for a hub, add this to its config and restart it:
cloud:
disabled: trueUpdates then use GitHub. telemetry.disabled: true separately disables reporting everywhere. A configured telemetry.url can still send to your own collector with the cloud disabled. This policy belongs to the hub config; it does not restrict unrelated programs or a shell user’s separate config.
With cloud disabled and no allowlist, sharing is off. To permit only a team host, set memory.share.allowed_servers and memory.share.server.url to your chosen host. Team gateways have drops off by default: an operator must enable gateway.drops.enabled, configure TLS and provision a users-file token (prefer scope drops:write). Team servers do not offer device login. See Operations reference before operating one.
Need a hand?
Check the troubleshooting guide or ask with a redacted report.