Config: support a user-level config layer or fall back to the primary worktree's config.local.yaml
Maintainers usually reply within 1 day
@Shivang9983 is already working on this.
Since Oct 1, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Read the ce-config-layers rule and docs/guides/configuration.md to trace the current resolution order; then review docs/brainstorms/2026-03-25-config-storage-redesign-requirements.md for existing user-level requirements. Implement one of the two proposed approaches, preserve repo-file precedence and keep docs_root repo-only. Done when personal preferences work across linked worktrees and the relevant configuration documentation describes the behavior.
Written by the indexing model from the issue text.
Description
Problem
.compound-engineering/config.local.yaml is resolved from git rev-parse --show-toplevel only (the ce-config-layers rule and docs/guides/configuration.md). There is no user-level layer, and a linked worktree does not see the primary checkout's file.
Personal, non-secret preferences such as plan_model, brainstorm_model, cross_model_peer, and cross_model_review_mode describe the user, not the checkout. Because config.local.yaml is normally gitignored, every new worktree starts without it. Anyone who works in many worktrees (one per branch or agent) must re-create the file each time, or the settings silently do not apply.
docs/brainstorms/2026-03-25-config-storage-redesign-requirements.md describes user-level defaults and a user_state_dir (~/.compound-engineering), but the shipped resolution reads only the two repo files.
Current workaround
A post-checkout git hook that symlinks a shared file (~/.claude/ce-config.local.yaml) into each checkout's .compound-engineering/config.local.yaml. It works, but it is per-repo, untracked, and invisible to /ce-setup diagnostics.
Proposal
Either of these would remove the need for the workaround. The first is preferred.
- User-level layer. Add
~/.compound-engineering/config.yaml(honoring$XDG_CONFIG_HOME/compound-engineering/config.yaml) as the lowest-precedence layer. Resolution order:<repo>/.compound-engineering/config.local.yaml, then<repo>/.compound-engineering/config.yaml, then the user-level file, then the skill default.docs_rootstays repo-only. - Primary-worktree fallback. When the current checkout is a linked worktree and has no
config.local.yaml, read the one in the primary worktree (the parent ofgit rev-parse --git-common-dir).
Related: /ce-setup could report which layer supplied each active key.
Notes
- Existing precedence is unchanged. A repo
config.local.yamlorconfig.yamlvalue still wins over the user-level file. - Keys that are inherently repo-specific (
docs_root,sweep_state_path,feedback_sources) should stay repo-only. The user-level file would accept only personal preference keys.
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 80/100
EveryInc/compound-engineering-plugin#2084 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2083 ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
hurttlocker/o8#6535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
snapotter-hq/SnapOtter#4856 ·
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day