# Project folders for coding work

Nock uses project folders as the working location for coding tasks and builds. Mention a project by name when you want to continue existing work; ask for something new when you want a separate project folder.

The **Current project** card in **Settings → Agent → Projects** shows where the next build step and worker commands run. Code search and language tools follow that project. The **Code search** line shows whether the folder is indexing or ready; see [Code search and language tools](/nock/code-intelligence) for the index, its scope, and Rebuild control.

## Start a new project

Ask Nock for a complete new thing—such as an app, site, or tool—or say “new project” or “from scratch.” Nock creates a folder for that project and uses it for the work. If the proposed folder name is already taken, it chooses another name rather than merging unrelated work.

An edit to part of an existing project—such as adding a page or changing a setting—belongs in that existing project. Say its name explicitly if the right folder is not obvious.

## Find an existing project

You can say “my portfolio site,” “the shop project,” or give a full folder path. Nock considers recently used projects, folders open in supported editors or terminals, its Nock Projects folder, and other project folders it can locate. If more than one match is plausible, be more specific and check the selected folder on the task before proceeding.

After Nock restarts, it remembers the last project but does not automatically put every new request there. Name the project when you want to return to it; otherwise a request for a new build can create a separate project folder.

## Allow a folder

Folders inside **Nock Projects** do not need an extra folder-access choice. For another project folder, Nock may ask **Let Nock work in (that folder)?** Choose **Allow once** for this task, **Always for this folder** when you want to remember access, or **Decline** if it is not the right project.

Nock does not use an entire home folder, disk root, or other broad system location as a project. Choose the specific project inside it instead. Before you allow an external folder, check that it is the intended checkout and that other tasks are not editing the same files.

## Move a task to another project

You can ask Nock or a worker to switch projects mid-conversation. After it switches, new commands and file operations use the selected project. Read the task's project name before sending instructions that could modify files.

Claude Code and Codex tasks follow the same project-selection rules. A coding task may need the same folder access confirmation before it starts. See [Coding agents](/nock/coding-agents) and [Coding task troubleshooting](/nock/coding-troubleshooting).

## Avoid editing conflicts

Do not start two implementation tasks that may change the same files at the same time. The task card and Agents panel show the project and worktree where a coding chat is working. A separate worktree gives a task its own checkout when you explicitly ask for one. For project-based chat discovery, see [Agents panel](/nock/agents-panel).