Understand projects
A project is a folder you work in. It may contain a Git repository, but it does not have to. The same project can be connected on several computers, each with its own local folder.
A project is not a tool source
Section titled “A project is not a tool source”A project is where you use tools. A tool source is a repository you import to find tools. They are separate roles: adding a source in Tool Builder does not tell Code Config where your project lives.
The interface calls connecting a project folder Map project. This links the project to a folder on one computer; it is not the same as scanning a repository for tools.
When to connect a project
Section titled “When to connect a project”You can launch locally in a folder that is not connected to your account. Connecting it is useful when you want to set a default toolkit, reuse the project from the launcher, or request a launch from the web app.
A launch from the web app needs a project connected to a computer, because the browser cannot choose a local folder for that computer.
What is stored
Section titled “What is stored”The web app tracks the project, the repository associated with it, and the connected computers. Readable local folder locations stay on their computer. Connecting a project does not upload its ordinary files.
Adding a GitHub repository as a tool source is a separate decision. That repository is read through the access you approve for it, and the tool list is built from what is found there. Tool files you wrote yourself reach the service through the Community sharing step you start yourself, which is not part of connecting a project.
Code Config writes the supported toolkit configuration for your chosen app. The coding-app guide explains whether that is in a launch folder or, for Cursor setup, in the project itself.