[DOCS] Projects beta: what do local threads (Remote Control) load, and do they use worktrees?

Summary

I run many local Claude Code sessions in the desktop app, each in its own git worktree of one repository, with hooks and rules in ~/.claude. Before moving new work into the Projects beta as local threads (Remote Control), I'd like the docs to answer six questions. The Projects page (/docs/en/claude-projects, "Run a thread on your own computer") says a local thread "works with the files, tools, MCP servers, and Claude Code settings on that machine", but it doesn't say which of those it loads.

Questions

1. Hooks. Does a local project thread run the hooks in ~/.claude/settings.json and the connected folder's .claude/settings.json (SessionStart, PreToolUse, Stop, and so on), exactly as a session I start myself would? Does that change when the project has several repositories? The cloud-thread table says repository hooks "don't apply" in multi-repository projects.
2. Instructions. Does it load ~/.claude/CLAUDE.md, the ~/.claude/rules/ folder, the repository's CLAUDE.md, and auto memory (~/.claude/projects/<path>/memory/)? The page says project memory files are not loaded. Project memory is tracked in #97464; this question is about the machine's own files.
3. Worktrees. Does a local thread run directly in the connected folder, or does it make its own git worktree? claude remote-control --spawn worktree exists for the terminal server. Is there an equivalent for folders connected in the desktop app (Settings > Claude Code)? Without one, two local threads in the same folder can overwrite each other's edits.
4. Permission mode. The page says local threads run in auto mode. Can a project, or the connected folder, set a different starting mode (for example Manual), the way claude remote-control --permission-mode does?
5. Existing local sessions. The page says a session started on my machine can't be added to a project. Is "Move to project" for local sessions planned? A local session could then join a project without starting over.
6. Accounts. A project belongs to one account. If I sign the desktop app into a different Claude account, do local threads keep running, and can a project be moved to another account I own?

Why it matters

My safety checks live in local hooks and rules. They are what stop a session from writing in the wrong folder or merging unchecked work. Knowing which of them apply to local project threads decides whether I can use Projects for local work at all.

Related

• #95988 (Projects should be able to run local Claude Code runs)
• #97464 (local threads can't read or write project memory)
• #96775 (auto-mode check blocks approved work in Projects)

Environment

macOS, Claude desktop app (Code tab), Max plan, Projects public beta.