Projects

A project collects the issues you capture for one app or repo. nitpin keeps a list of your projects; exactly one is active at a time — that’s where new captures land.

Creating a project

From the app (menu bar › New Project…, or the Cockpit’s project menu), name the project after the app or repo you’re testing and pick where it lives:

• In nitpin — start capturing now, link code later. The project is stored under nitpin’s own folder on your machine. Perfect when you just want to start pinning.
• In this repo — store issues with the code. Creates a .nitpin/ folder inside the repo you choose and wires up your coding agent there (this is the same thing nitpin init does from a terminal). Issues are committed alongside the code, so they travel with it.
• Clone from Git — paste a repository URL; nitpin clones it and creates (or adopts) its project in one step. See Sync Issues with Git.

From a terminal, the equivalents are:

nitpin init              # a .nitpin/ store in the current repo
nitpin init --path DIR   # store the project elsewhere, leaving a pointer in the repo
nitpin clone URL         # clone a repo and open its project

Switching and opening

• The menu-bar popover header shows the active project; click the chevron to switch. The Cockpit’s rail title opens the same switcher, plus Open… for browsing to a project folder on disk.
• From a terminal, nitpin open activates the project for the current directory and raises the Cockpit; nitpin projects lists everything nitpin knows about.

Linking a repo to an existing project

If your project lives “in nitpin” but you want captures to be fixable from a particular repo, link them:

cd path/to/repo
nitpin link              # pick from your known projects
nitpin link my-app       # or name one directly

Linking writes a small nitpin.yaml pointer in the repo so agents and CLI commands run there resolve to the right project. nitpin unlink removes the pointer again.

The link is also how a project gains a Source — the code folder shown in Project Settings, used by fixes, Tune, and git sync.

Project settings

Each project carries its own workflow settings — how agents work (parallel worktrees or one at a time), where fixes land (main or a review branch), what happens when an agent hits ambiguity, auto-triage, and more. They’re all in the Cockpit under Project Settings…, and machine-wide defaults for new projects live in Settings › Projects. The full list is in the Settings reference.

Where projects live

New “in nitpin” projects are stored under a default folder you can change in Settings › General › New projects. In-repo projects live in their repo’s .nitpin/ directory. Either way, a project is just a folder of plain files — see Where Your Data Lives.