Project scopes
Each project can have its own skills, MCP servers and settings, apart from the global ones your agents use everywhere. Switch to a project to see and change its setup.
What each scope shows
Section titled “What each scope shows”The scope picker sits near the bottom of the sidebar, just above Settings. It has Global, each registered project and Add Project…, and All scopes once you’ve registered a project. HarnessKit remembers your choice between launches.
- Global. What your agents use everywhere: the files in their home folders.
- A project. That project’s own files, inside its folder.
- All scopes. Everything at once.
Pages follow the scope in different ways:
- Agents, Extensions and Audit show only what is in the current scope.
- Kits shows, in a project, only the Kits installed there. In Global and All scopes it shows your whole library.
- Marketplace puts a check mark on each agent that already has a skill in the current scope. In All scopes, any scope counts until you pick one to install into.
- Overview doesn’t follow the scope. It is the dashboard for the whole machine, so its numbers stay the same.
What counts as a project
Section titled “What counts as a project”A folder counts as a project when it holds a project file or folder of any supported agent, such as a .claude or .codex folder or an .mcp.json file. An AGENTS.md or CLAUDE.md on its own isn’t enough.
Add one in Settings → Project Paths. Add Project… in the scope picker opens Settings, where Project Paths is the second section.
- Paste a path, or browse. Paste a folder’s path and click Add. In the desktop app you can browse to it instead.
- A folder of projects. If the folder isn’t a project itself, HarnessKit looks inside it and lists the projects it finds. Tick the ones you want and click Add Selected.
- Scanning. HarnessKit scans a new project for its extensions and files, and adds it to the scope picker.
- Missing. A project whose folder was moved or deleted shows as Missing.
- Removing. Removing a project takes it off HarnessKit’s list and leaves its files alone. If it was the current scope, the app switches to Global.
See Settings.
Installing into a project
Section titled “Installing into a project”Where an install goes depends on where you start it:
- Install to Agent and Install to agents. On the Extensions page, an Install to scope picker starts on the current scope. You can pick another project, or Global, without switching. In All scopes you have to pick one.
- Marketplace, Install from Git and Install from Local. These install into the current scope. In All scopes, you pick one first.
- Kits. A Kit installs only into a project, never into Global. See Kits.
Some agents can’t take some kinds of extension at project level. In an extension’s Install to Agent, such an agent is greyed out with (N/A), and hovering over it says why. The Marketplace and the Git and local install dialogs grey it out too. Install to agents skips it and lists it as not supported at this scope.