DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to collect Aider chat logs from all your project folders with AI Data Extractor

Find every Aider transcript across your project directories and export them to JSONL.

Who it is forA developer who uses the terminal tool Aider across many repositories and keeps its transcripts scattered in project folders.

The problemAider has no central session store, so each project holds its own .aider.chat.history.md file.

The outcomeOne aider_conversations JSONL file with the transcripts from every project you point the tool at.

What you need first

  • Python 3.9 or newer installed on the machine that holds the chat history
  • The AI coding tools installed under your own user account, with local chat history present
  • Permission to read and store your own local data, and a secure place to keep the output
  • For the fine-tuning case: the Hugging Face datasets library and a tokenizer for your target model

Steps

  1. Run python extract.py --sources aider --search-path ~/client-work --search-path /mnt/data/repos after changing the paths to your own project folders.
  2. Open the new aider_conversations_*.jsonl file in extracted_data/ to confirm the transcripts are there.
  3. Keep the output private, since Aider transcripts often contain full project file contents.

Prompt for your agent

Using the repo jatechan/ai-data-extractor, run the aider source with --search-path set to <project folder>, and report how many project transcripts were found and written. Verify that each output line includes a messages array and a project_path value that matches one of the searched folders.

Caveat. The default search covers only the home directory and a few common folder names up to 5 levels deep, so projects stored elsewhere must be passed with --search-path.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page