This article explains what you see in onboarding while Ellie reads your code on Understand, and what you can check on the confirmation screen before moving on. It is for anyone setting up a project on the GitHub path and wanting to confirm that Ellie has understood the product correctly.
Step 1: Wait while Ellie reads your code
Understand is the fourth of six steps on the GitHub path: Start, Connect, Your docs, Understand, App access, Write docs.
This step exists only on the GitHub path. A project started from your website has no Understand step and no confirmation screen.
The page heading is Reading your codebase…. It includes a progress bar and this note: Ellie is mapping your routes, features and user-facing screens. This usually takes 2–10 minutes, longer for big or multi-repo products.
You do not need to do anything on this step. When reading finishes, the page moves on by itself about a second later. You can also close the tab and come back to the same address.

If your project has one repository
Ellie works through these status lines:
- Cloning your repository
- Detecting features…, which then becomes Found N features
- Understanding what your product is for…
A green tick means done, a spinner means in progress, and a grey circle means waiting.
If your project has several repositories
Ellie shows one line per repository as it reads them. Each line starts as Reading owner/repo… and then becomes Read owner/repo — N features (stack) when finished, if the stack is known.
After that, Ellie shows:
- Detecting how your repos connect…, which then becomes Worked out how your repos connect
- Understanding what your product is for…
Step 2: If reading fails, retry from the Understand step
If analysis fails, the heading changes to Something went wrong. A red alert explains the reason and says: Retry, and if it keeps failing reply to any Ellie Docs email and we’ll take a look.
The Retry button is on this step only. It restarts the analysis.
The failure reasons are:
- This step took too long, so we stopped it.
- This step was interrupted on our side.
- Ellie couldn’t access that repository — check the Ellie Docs GitHub App has access to it.
- Ellie couldn’t finish reading your code.
Step 3: Review the confirmation screen
When analysis finishes, Ellie takes you to the confirmation step headed Here's what I understood — is this right?
The note under the heading says: This steers every article Ellie writes, so it's worth a ten-second check.

This screen shows:
- Ellie's description of your product, or No description drafted yet.
- a chip for each type of reader Ellie identified, if any were found
If your project has several repositories
You also see a box called How your repos fit together.
It includes:
- one chip per repo in the format name · Role
- the primary user-facing repo highlighted
- Ellie's notes on how the repos connect
Repo roles can be:
- Web app
- Backend API
- Browser extension
- Mobile app
- Background worker
- Marketing site
- Shared library
- Repo
Step 4: Confirm or edit the product description
If the summary looks right, select That's right → to continue to App access.
Confirming here does not write any articles yet. The next step, App access, decides how screenshots are taken, and articles are written only after you continue from there.
If you want to change the text first, select Edit details.

This switches the screen to two editable fields:
- What is your product?
- Tone notes (optional)
The main button then becomes Save and continue →.
Your edits are saved only if you changed the text. While you are editing, the persona chips and repo map are hidden.
You cannot edit personas or repo roles on this screen.
Good to know
Where can I edit this later?
You can edit product details later in Project → Settings → Product. That area includes the product description, company description, product type, and Guidance for Ellie (optional).
Repo roles and which repo is primary are in Project → Settings → Repositories.
What if the confirmation screen does not load?
There is no error message or Retry button on the confirmation screen itself. If the profile cannot be loaded, it stays on a loading spinner. Refreshing the page reloads it.
Where is the low-confidence warning?
It is not on the confirmation screen. It appears on Project → Overview as a yellow alert headed Ellie may have missed your product's main surface.
The alert says: The last analysis mostly found internal tooling or config (<reasons>). Check the Features page — if the list doesn't look like your product, re-run the analysis after a push, or reply to any Ellie Docs email and a human will take a look.
What limits affect this step?
When Ellie analyses a repository she reads up to 500 source files and skips files over 100 KB, so very large repos can be only partly read. For the full file rules, see What code Ellie reads and what it never reads.
When does Ellie analyse the code again?
Re-analysis happens automatically after pushes to the tracked branch, grouped over about 10 minutes. You can also start it from Project → Overview using Analyse repo or Re-analyse repo, and Check latest push.
Does each analysis count towards plan limits?
Yes. Each analysis counts towards your plan's monthly update allowance when limits are enforced. Free allows 5 per project per month and then stops. Paid plans are not blocked.