Keep the decisions from a coding session.
A coding session often explains why the final diff looks the way it does. Memrain can import supported Codex rollouts and Claude coding-session logs so the recorded discussion remains available to later retrieval.
Illustrative request
Save this completed coding session so the next review can recover the decisions behind it.
The transcript tooling parses the supported log and stores conversation pages after credential screening. A successful upload may only mean the job was queued; check import status before relying on the content.
Illustrative scenario, not a live product result.Choose a local import or a remote push
An ingest command can process files where the database is reachable. A laptop can instead push an eligible session log to a deployed Memrain server. The remote path uses a protected token file, checks allowed log locations and submits accepted content to an ingestion job.
Configure capture explicitly
The guide includes optional session-end hooks for coding work in Claude and Codex. Nothing installs itself. The hook definitions use explicit executable paths and a controlled working directory; follow the documented setup rather than copying a shortened command. Client hook limits can interrupt uploads, so failures need inspection and a manual retry.
- Manual import for selected sessions
- Optional hooks configured and trusted by you
- Status checks for queued or failed imports
Preserve useful conversation, report format drift
The importer handles supported log structures and filters recognized harness traffic. Missing user turns or unfamiliar content can produce a reported refusal instead of a misleading partial conversation. Importing logs is separate from connecting the assistant to Memrain's live MCP tools.
Keep the context. Move the work forward.
Connect your knowledge to the AI you already use. Find your starting point and make the next conversation count.