Personal instructions should have one source of truth across local and cloud sessions

### The need

I want to write my personal instructions once — commit message style, branch naming, "always ask before pushing" — and have them apply wherever I use Claude Code. Today there is no way to do that.

### Why the current options don't cover it

**`~/.claude/CLAUDE.md`** works locally, but cloud sessions never load it. The [carry-over table](https://code.claude.com/docs/en/cloud-environments#what-carries-over-from-your-setup) lists it as unavailable: "lives on your machine, not in the repo."

**The repo's `CLAUDE.md`** loads in both local and cloud sessions, but it is per-repo and shared with the team. Personal preferences don't belong in a file my teammates read, and I would have to repeat them in every repository I work in.

**Org-wide `claudeMd`** through [server-managed settings](https://code.claude.com/docs/en/server-managed-settings) does reach both surfaces from one place — but it requires Team or Enterprise plus the Owner role, and it applies to everyone in the organization. It solves the delivery problem for admins and leaves individuals with nothing.

The remaining workaround is to keep a canonical file somewhere and re-fetch it with a setup script in each cloud environment. That works, but it is a second copy to maintain, it has to be repeated per environment, and edits only take effect when the environment cache rebuilds.

### Two mechanisms already work the way I'm asking for

1. **Skills.** The same carry-over table notes that "cloud sessions automatically load skills you enable on claude.ai" — an account-scoped, user-level setting that already reaches cloud sessions.
2. **`claudeMd`.** Organization-wide CLAUDE.md content already ships from Anthropic's servers and lands in both local and cloud sessions.

So both halves exist: account-scoped user settings that sync to the cloud, and CLAUDE.md content delivered over the network. What's missing is the intersection — the user-level version of instructions.

### What I'd like

Either shape would solve it:

- **Sync `~/.claude/CLAUDE.md` to the account**, so cloud sessions load the file I already maintain locally. Preferred, because it adds no new place to write things and no second copy to keep in step.
- **Or a personal instructions field in claude.ai settings** that loads in every Claude Code session, at the same precedence as `~/.claude/CLAUDE.md`, with project `CLAUDE.md` still winning on conflicts.

Opt-in either way, since some people won't want local files leaving their machine.

### Relation to #47885

That issue was closed as not planned. I'm filing this because the framing there was narrower — a settings box for `claude.ai/code` web sessions specifically. The underlying gap is broader: no user-level instruction source reaches cloud sessions at all, on any surface that runs them. Skill sync and org-level `claudeMd` have both shipped since, which makes the same request considerably cheaper to satisfy now.

Start by reading the cloud-environments carry-over table and server-managed settings documentation linked in the issue, then compare the existing skills and org-level claudeMd mechanisms. Done means an opt-in, account-scoped personal instruction source reaches both local and cloud Claude Code sessions without requiring per-repository copies, while project instructions retain precedence on conflicts.

Escrito por el modelo de indexación a partir del texto del issue.