GitHub, read-only.

For engineers, the real history of a codebase is in its pull requests, issues and commits, not its README. Firstweek connects read-only to the repositories you choose.

What Firstweek reads from GitHub

What shows up in the onboarding artifact

GitHub activity anchors the role and current-state parts of the artifact: what is being worked on, recent architectural decisions, and who owns which part of the codebase.

Read-only, and the raw content is never stored

Every connection, GitHub included, is read-only: Firstweek never writes to, changes or deletes anything in your tools. GitHub content is processed in memory and never stored. Only AI-generated summaries persist. A citation can quote up to 200 characters of a summary, and an admin can turn that off.

GitHub has no read-only permission for private repositories, so its consent screen asks for full access to them. Firstweek only reads.

Full detail: the security page covers data handling end to end, and the subprocessors list shows exactly which GitHub data is processed.

Run Firstweek on your next real hire. 30 days. Then we talk about whether it's worth keeping.