Skip to content
Second Brain Link

All downloads

Sources · Personal source · export guide

Export your GitHub data into a private AI brain

A developer’s working history is on GitHub, not LinkedIn. The account export turns it into a voice layer of repositories, a map of your technical interests, and a network of the people you build with.

tar.gz JSONexport link by email (hours)zero network calls in the build

What a GitHub export holds — and what the brain makes of it

GitHub’s account export is a tar.gz of JSON: repositories with descriptions and issue and pull-request activity counts, the languages you write in, the repositories you starred, who you follow and who follows you, and your organization memberships. The brain builder writes repositories into the voice layer (what you build is what you say), languages and stars into interests, followers and following into people notes, and organizations into organization notes — so an open-source maintainer you follow who also appears in your LinkedIn connections becomes one person.

For a job hunt this is the export that lets the brain answer "what have I actually shipped" with specifics, and for a technical sales pipeline it is the warm-tie map of who you have worked alongside in the open.

Get the export

How to export your GitHub data

The exact clicks, as they are today. Platforms move menus; the engine’s source docs are updated when they do.

  1. 01

    github.com → Settings → Account → Export account data → Start export

  2. 02

    Download from the email link (arrives within hours)

  3. 03

    Extract the tar.gz before importing

  4. 04

    Drop the archive on GitHub in Studio’s Sources — or tell Claude Code or Codex “build my brain from this”. The source is detected by itself, even inside a combined archive.

Second Brain Studio — Sources — one export and its files on the John Carter demo brain (light)
Studio › Sources the files one export was built from — a newer export is dropped here

Then, next month

An export is a snapshot. Drop a newer one and press Update: your edits and _notes/ are kept, and the update report says what changed.

How Update works

Then ask it

What you can ask a brain built from GitHub

Examples, not promises: the answer is whatever your notes hold, and every answer cites the notes it came from. The more exports you add, the more these questions cross sources.

  • Which languages have I actually shipped code in, by repository?
  • Who do I follow on GitHub that I also know from work?
  • Which organizations am I a member of, and who else in my network is there?
  • Which starred repositories match the topics I write about?

limitCode itself is not read — the brain keeps repository metadata and activity counts, not file contents; extract the tar.gz before importing.

Good to know

The honest answers.

Does it read my code? No. The export carries repository metadata and activity counts; file contents are not part of it and the brain never clones anything.

What about private repositories? The brain keeps whatever the export lists — name, description and counts per repository — and nothing more. Nothing is uploaded; the build runs on your machine.

Start

Your GitHub export already exists. Turn it into a brain.

Free and open source. Start with John’s demo brain while your export arrives.

Download for MacApple silicon (M1–M4)

Second Brain Studio · Mac (Apple silicon and Intel), Windows and Linux · free · MIT

Just looking? Open Studio in your browser — two demo brains, nothing to install