[FEATURE] Projects (beta): persistently load the attached repo (CLAUDE.md, skills, hooks) into the coordinator session

Problem

In a Claude Project with a GitHub repository attached, thread sessions load the repo's CLAUDE.md, skills and hooks. The project's coordinator session (the one watching the project chat) does not. It can attach the repo to itself mid-session, but only for that session. When the coordinator is replaced (for an upgrade or an age limit, which happens routinely and invisibly), the new one starts without the repo.

The only way to make a new coordinator re-attach is a line in project memory asking it to. That is a prose instruction with no enforcement, and the coordinator can't have hooks of its own to make it fire. In my experience, prose rules like that don't fire reliably.

What this costs me:

1. Thread briefs miss the repo's rules. A coordinator without CLAUDE.md writes briefs that can frame or route work in ways the repo explicitly rules out.
2. Repo skills don't start from the project chat. When I ask the coordinator to run a repo skill, the thread it starts doesn't reliably load the skill, so I open the thread and type the slash command myself.
3. The other workaround doesn't scale. Copying CLAUDE.md into project memory creates a second copy of a long, frequently changing file, which drifts.

The net effect is that I can't stay in the project chat and work through the coordinator. This is the main gap stopping me from moving my day-to-day work from the Claude Code CLI to Projects.

Proposed

• A project setting such as "load this repo into the coordinator" that attaches the repo for every coordinator, replacements included, before its first turn.
• Load the repo's hooks along with CLAUDE.md and the skills, so the rules there can be enforced and not just read.
• When a request matches a repo skill, start the thread with that skill invoked, the same as typing its slash command.
• Optionally, control over what the coordinator loads (for example, the skill list without the full CLAUDE.md), since everything loaded costs context on every message.

Related

• #97924 covers thread sessions not reading AGENTS.md / CLAUDE.md before writing code. This request is about the coordinator.
• #29423 (closed) was the same gap for subagents.
• #97565 asks which hooks, rules and CLAUDE.md files local project threads load. This request is the same question for the coordinator, which today loads none of them.

Environment: Claude Projects (beta), cloud threads and Remote Control threads, claude.ai web and desktop app.