mrlnlms

Multi Ai Session Data Extractor

Name: Multi Ai Session Data Extractor
Author: mrlnlms

Data community

SOURCE https://github.com/mrlnlms/multi-ai-session-data-extractor

Description

Capture and preserve your own AI conversations locally before they vanish — 10 platforms, unified parquet schema, deletion-resilient.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

multi-ai-session-data-extractor

[![tests](https://github.com/mrlnlms/multi-ai-session-data-extractor/actions/workflows/test.yml/badge.svg)](https://github.com/mrlnlms/multi-ai-session-data-extractor/actions/workflows/test.yml) [![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

Capture, preserve, and explore your own sessions across AI platforms (ChatGPT, Claude.ai, Gemini, NotebookLM, Qwen, DeepSeek, Perplexity, Grok, Kimi) plus command-line tools (Claude Code, Codex, Gemini CLI, Antigravity CLI). Data is preserved locally in canonical format (parquet), even if you delete it from the server.

The repository contains the code, documentation, and DVC pointers; personal data, browser profiles, and private operating notes stay outside Git. This makes it possible to rebuild a working machine without publishing the archive itself.

**This tool is for personal use, with your own accounts.** It uses the platforms' internal APIs authenticated with cookies from your own login (access you already have). It is not a tool for scraping data from other users or for bypassing terms of use — and should not be used that way.

![Streamlit dashboard showing all sources with status, total counts, and cross-platform views](docs/img/quickstart-01-hero.png)

The problem

AI platforms have limited official exports, often broken, with no guarantee of retention. You have no way of knowing whether an old conversation will be accessible 6 months from now, or whether a new feature will disappear taking data with it.

This project solves that by capturing everything locally:

Conversations, projects, knowledge files, artifacts (canvas, deep research reports, slide decks)
Generated images (DALL-E, Nano Banana), user uploads, mind maps
Voice messages (transcripts), thinking blocks (reasoning), tool calls
Chats deleted on the server — preser