Source: https://seerepo.com/docs/first-load
Markdown source: https://seerepo.com/docs/first-load.md
Description: What you see the first time SeeRepo reads a repo, and what you can do while it plays.

# Your first load

The first time SeeRepo reads a repo, you watch it happen. Your map comes first, in under a minute for a medium repo and in a few minutes for a very big one, and the details keep arriving after: the whole reading takes about half a minute for a small project and up
to a minute and a half for a big one. Nothing you do can break it, and you can leave it at any moment.

## What you see

1. **Three empty folders.** Health, Journey and Structure. They fill as the engine reads.
2. **The reading.** On the left, the files it found, each with the part of your product it belongs to, and the
   ones it isn't sure about. In the middle, what it learned about your repo, one finding at a time: lines of
   code and their language, commits, your stack, and how much of it an AI agent co-wrote.
3. **Your modules.** Each module is an area of your product as the people who use it see it: sign in and
   account, pricing and payments, the editor. Your files fly into them, and the map that connects them appears.
4. **The tour.** A stop in Journey, with your history, and another in Health, with what's worth fixing.
5. **The last frame.** Your folders, an image of your map ready to share, and a way into the map. A folder with nothing in it yet, like a Wiki not written yet, comes later. On a phone you see the image and the dock with all five; when you leave, the folders.

## While it plays

- **Skip the tour** (or press Esc) takes you to your folders. It shows once the reading starts. Your map keeps
  drawing all the same.
- **Touch the map** to take over: the tour ends there and the camera stays where you left it.
- With **reduce motion** on, the camera cuts instead of flying, and there's no confetti.
- From your second repo on, you get a shorter version.

## Good to know

- Your map is written in the language you picked when you connected the repo.
- If SeeRepo finds no code it can read in your repo, you still get its history in the film and in Journey, without a
  map.
- If your repo is in a language SeeRepo doesn't read with cables yet, you get a map without cables, and you're on that
  language's waitlist.
- With a plan, after the first load new things arrive by themselves: when you push, what changed comes to its
  folder.
- Your free repo is read once, whole. If many are being read that day, yours waits in line: you can close the
  page, we'll write to you when your film is ready, and you'll watch it when you come back. While it waits there's
  nothing to skip yet: **Skip the tour** shows once the reading starts. When you come back, the Structure folder
  says how your repo was drawn, since it already happened.
- If the reading fails before your map is ready, the film stops there. SeeRepo tries again by itself, up to three
  tries in all: the page says so, and the film starts over when it does. If the last try fails too, the project says
  the read failed, with **Read it again**.
- A repo with no commits yet has nothing to read: its empty folders appear, the film ends, and the project says
  "This repo has no changes yet. SeeRepo reads it at your first push." Push your first commit and SeeRepo draws
  its map: with the page open, you watch it happen.
- When someone you invited opens the repo for the first time, they watch its film too, with the repo's name
  where you read "your".