A project is a site or a repository you work on. Everything else hangs off it: tasks, flows, captures, brand kit and settings are all scoped to one.
Why scoping matters
Without it, a task list is a single pile across every client and side project you have, and the browser extension has no way to know which of them the page in front of it belongs to. With it, opening a site in the browser shows you that site's tasks.
Connecting imports everything
Connect GitHub or Search Console and everything you have becomes a project — repositories with their language, stars and last push, verified domains as sites. You delete what you don't want; undoing an import is one click, a missed import is invisible. The list groups by organisation, largest first, with domain-only sites under their own heading.
Private repositories import too — for your eyes only. They never appear on your public pages beyond a counted-never-named total. If the sync looks incomplete, the coverage card above the list says exactly which half is missing — private scope not granted, an organisation blocking third-party apps — and carries the fix as buttons: grant access, include private repositories, resync. An organisation with private membership and an unapproved app disappears from GitHub's answers entirely, without an error; the card covers that case too.
Every project has a page
Click a project's name and you get the whole of it: the site's own image as a hero, an eight-week activity chart (captures in, tasks created, flow runs walked), the open tasks and who they are for — you or your agent — every flow with its last run's verdict, a contact sheet of recent captures, and the latest audit your editor pushed.
Analyse the repository reads what a stranger meets — README, description, website, topics, licence, whether your domain serves an Open Graph image — and files each miss as a task on the project, owned by whoever can fix it: your coding agent for code, you for the settings GitHub keeps behind admin pages. Re-running never duplicates and never resurrects a finding you closed.
A project that knows its domain but not its code (a Search Console import) has a one-field form to link the repository: owner/name, refused by name if another project already carries it. One repository, one project.
Switching
The project switcher is in the left panel. Picking a project takes you to its page, and narrows tasks and flows everywhere behind it. "All projects" widens back to the account view.
One sync, both stories
The same gesture that lists your repositories refreshes your developer profile — public figures, activity, organisations, your GitHub avatar. You never maintain two synchronisations.
Projects here versus projects on the marketplace
The marketplace also has projects — client work with a price and a delivery date. They are a different thing, on a different route. These are your technical projects; those are jobs somebody is being paid for.