Ellie Help
Ellie Help Home What's new Getting started9 Work with Ellie4 Write and organise content7 Keep your docs up to date1 Publish and brand3 Walkthrough videos2 Changelog2 Measure and improve1 API reference1 Workspace and billing6 Connect AI tools1
Security and data3
Troubleshooting1
Powered by Ellie Docs
Security and data/What code Ellie reads and what it never reads

What code Ellie reads and what it never reads

Updated 19 Nov 2026

On this page

This article explains what repository code Ellie reads for a project, what she skips, how secrets are masked, and what is kept or removed. It is for teams reviewing how Ellie accesses connected GitHub repositories.

How Ellie gets access to your repositories

Ellie reads repositories through the Ellie Docs GitHub App. You install it on your GitHub account or organisation and grant only the repositories you choose.

In Workspace → Settings → GitHub, Ellie says: 'Ellie reads your repos through the Ellie Docs GitHub App — read-only, and only the repos you grant.'

The GitHub tab describing how Ellie reads your repositories through the GitHub App

The App's exact permissions are shown on GitHub's install screen, so check them there.

Ellie's own code only reads repositories. It lists the repositories you granted, checks a branch's latest commit, downloads a repository archive, fetches a file or folder listing, and compares two commits. It never commits, pushes, or changes anything in your repositories.

Access tokens are short-lived and created per GitHub App installation. Ellie never asks for your GitHub password. Continue with GitHub is a separate sign-in feature. Ellie also receives GitHub push notifications for repositories you connected so she knows when to re-check your docs. Website-only projects read no code at all.

What code Ellie reads

Ellie reads code from the repositories connected to a project.

For analysis, Ellie reads these source files when they are within the analysis limits:

  • .ts
  • .tsx
  • .js
  • .jsx
  • .vue
  • .svelte
  • .py
  • .rb
  • .go
  • .java
  • .cs
  • .php

Ellie also reads these project files during analysis:

  • package.json
  • pnpm-workspace.yaml
  • go.mod
  • requirements.txt
  • Gemfile
  • CHANGELOG.md
  • README.md

To understand the layout of a repository, Ellie also builds a list of file names across the repository. This is names only, not file contents.

During analysis, files over 100 KB are skipped and Ellie reads at most 500 files per repository.

If you want to control what Ellie scans for a project, see Exclude files from scanning.

During analysis, Ellie also skips files and folders whose names start with a dot, and these folders:

  • node_modules
  • dist
  • build
  • .next
  • coverage
  • __pycache__
  • vendor

When you chat with Ellie or she checks an article against your code, she can search any non-credential file in the analysed copy, with any extension, up to 400 KB each. She skips hidden folders, but she may read other non-credential dotfiles such as .eslintrc.

What Ellie does not open

Credential-shaped files are never opened. That includes names matching:

  • .env*
  • *.pem
  • *.key
  • id_rsa
  • id_ed25519
  • id_ecdsa
  • *.p12
  • *.pfx
  • *.keystore
  • *.jks
  • *.tfstate
  • .npmrc
  • .pypirc
  • .netrc
  • any file name containing credentials

This applies during analysis and when Ellie searches or reads code in chat or while checking articles.

Names of non-hidden credential-shaped files such as server.pem, id_rsa, or aws-credentials.json can appear in the file list Ellie uses to map your repository. Their contents are never read, searched, or shown.

How secrets are masked

Ellie masks the secrets she can recognise with ••• before text is sent to an AI model or saved.

This masking covers:

  • private-key blocks
  • quoted values assigned to names containing secret, token, password, api key, private key, client secret, connection string, access key, auth token, or bearer
  • KEY=value lines in env-style files
  • values that look like AWS keys, OpenAI-style keys, GitHub tokens, Slack tokens, JWTs, or URLs containing user:password@

References such as process.env.API_KEY are kept. Ellie masks literal values, not references to settings, so she can document which settings exist without seeing their values.

Masking is pattern-based and cannot catch every secret, so secrets should still be kept out of source code.

When Ellie shows lines from code while answering questions, she also masks values after words such as secret, token, password, and api key on each line. Analysis and article writing use Azure OpenAI models.

What Ellie keeps, and for how long

When Ellie analyses a repository, the repository archive is downloaded, unpacked in temporary storage, read, and that copy is then discarded.

What Ellie stores is:

  • the repository name
  • the commit id analysed, for the latest two commits per repository
  • derived material, including the feature map, short code excerpts and summaries with secrets masked, verified code facts with the quotes that prove them, your product profile, and the articles

When Ellie later needs to check a claim against code during writing, review, or chat, she downloads that commit again from GitHub.

That copy may stay in a size-limited cache on Ellie's servers, up to 2 GiB per worker, with the oldest-used copies evicted first. The cache can hold the whole unpacked commit, including files Ellie does not open. If GitHub can no longer serve that commit, Ellie cannot consult it.

Screenshot runs and logins

In test-copy mode, Ellie clones your repository on the tracked branch into a temporary cloud sandbox to run your app. If there is a companion backend repository, Ellie clones that too. She uses a short-lived GitHub token in the clone URL inside the sandbox, where your app's code runs. The sandbox closes when the run ends and expires on its own after 15 minutes.

In test-copy mode, Ellie generates her own throwaway account with a random email address and password inside the sandbox copy. You do not supply credentials.

In live-app mode, you supply an app URL and an email address and password for each role. They are saved with the project, not shown back in the dashboard, and used only to sign in for screenshot and crawl runs. Ellie is instructed to browse read-only and typing into form fields is blocked. Deleting the project deletes them.

What deletion removes

In Project → Settings → Danger zone → Delete this project, Ellie says: 'Removes the project and everything generated for it — articles, screenshots, revisions, onboarding history. This cannot be undone.'

You type the project name, then click Delete forever.

When you delete a project, the project's records are removed. Its stored screenshots, crawl captures, uploaded images, changelog images, branding images, walkthrough video working files, and any older stored repository archives or database dumps are also removed. A cached copy of your code on Ellie's servers is not removed at that moment and is evicted automatically.

Good to know

  • Does Ellie read every file in a connected repository? No. For analysis, Ellie reads only certain file types and named project files, skips files over 100 KB, reads at most 500 files per repository, skips files and folders whose names start with a dot, skips specific build and dependency folders, and never opens credential-shaped files. In chat and article checks, she can search any non-credential file in the analysed copy up to 400 KB each, skips hidden folders, and may read other non-credential dotfiles.
  • Does Ellie have write access to my repositories? Ellie's own code only reads repository data for the repositories you grant through the GitHub App. It lists repositories, checks the latest commit, downloads archives, fetches files, compares commits, and never writes.
  • Does Ellie mask secrets before using AI models? Yes. Ellie masks the secrets she can recognise with ••• before text is sent to an AI model or saved, but masking is pattern-based and cannot catch every secret.
  • What happens if a commit is no longer available on GitHub? Ellie downloads commits again from GitHub when she needs to check them later. If GitHub can no longer serve a commit, Ellie cannot consult it.
  • What is deleted with a project? Deleting a project removes the project's records and generated material, including stored screenshots, crawl captures, uploaded images, changelog images, branding images, walkthrough video working files, and any older stored repository archives or database dumps. A cached copy of your code on Ellie's servers is evicted automatically rather than removed at that moment.
On this page