### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement The new Projects (beta) are built around cloud threads working from github.com repos. "Work locally" exists, but it's an opt-in exception routed through Remote Control: every local thread pops an "Allow Claude to work

[FEATURE] [Projects] Local-first projects: let a non-GitHub local folder be the project's primary context

Status Open

Maintainer reply None cached

Activity 0 comments · opened Oct 3, 2026

Preflight Checklist

[x] I have searched existing requests and this feature hasn't been requested yet
[x] This is a single feature request (not multiple features)

Problem Statement

The new Projects (beta) are built around cloud threads working from github.com repos. "Work locally" exists, but it's an opt-in exception routed through Remote Control: every local thread pops an "Allow Claude to work in a folder on your device" card, and the picker lists every folder from Settings → Claude Code, not just the one this project is about.

Not everything I work on is a GitHub repo. Several of my projects are local folders (Roblox ScriptSync dirs, a FiveM server, local tooling that can't be pushed). For those, there's no way to say "this project IS this folder." The project can't be created around a local folder, cloud threads can't see it, and the local path keeps re-asking.

Related: #99156 (first-class local thread type) and #98385 (default local folder approval lost on Remote Control restart). This request is different: it's about creating a project around a local folder in the first place, instead of GitHub repos + an opt-in "Work locally" path.

Proposed Solution

In the New project dialog, let me pick a local folder as the project's primary context, the same way I pick a project folder for a desktop Code session today, with no GitHub repo required.

Once a project has a local folder:

Threads for that project run in that folder by default (via Remote Control under the hood is fine), with no "Allow Claude to work in a folder" card per thread.
The folder picker, when it does appear, is scoped to the project's folder(s), not the global Remote Control list from Settings → Claude Code.
"Set as default folder" persists per project and survives app restarts (#98385).
Worktree toggle stays available for git folders.
Project settings → Environment shows "Local folder: C:\...\my-project" alongside the existing GitHub repos section.

Cloud threads should still be available on the same project for tasks that don't need the machine.

Alternative Solutions

Add the folder as a GitHub repo: not possible for non-git / can't-push projects.
Upload the folder to the project Library: it's a copy, 100-file / 200 MB cap, and threads can't run tools against it.
Regular desktop Code sessions: works, but loses the coordinator, Overview pane, and shared instructions/memory that make Projects useful.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I'm building a self-hosted game server dashboard in C:\Users\brand\Documents\self-hosted-game-labs. It's local because it talks to Pencil (local design tool) and local Docker containers. I created a Project for it, but every thread Claude starts asks me to allow a folder, shows six unrelated folders, and after an app restart the default is gone. I want: create project → point it at that folder → send tasks → threads just run there.

Additional Context

Claude Desktop on Windows 11, Projects beta, folders connected via Settings → Claude Code → "Use this computer from your phone and claude.ai." Screenshot of the per-thread folder card attached.

View original on GitHub ↗