feat(#1969): ship claude settings via /etc/claude-code/managed-settings.json
This commit is contained in:
parent
70d1cdc859
commit
b231ed2392
6 changed files with 49 additions and 65 deletions
|
|
@ -1066,6 +1066,16 @@ in
|
|||
environment.etc."hyperhive/claude-plugins-auto-update.json".text =
|
||||
builtins.toJSON config.hyperhive.claudePluginsAutoUpdate;
|
||||
|
||||
# Hive-enforced claude settings. claude-code auto-discovers managed
|
||||
# settings at this canonical Linux path (precedence #1, read-only,
|
||||
# un-overridable by user/project/CLI) — so the harness no longer
|
||||
# passes `--settings` or copies the blob per turn. effortLevel is
|
||||
# deliberately NOT shipped here: effort is controlled live via the
|
||||
# `--effort` CLI flag (HIVE_DEFAULT_EFFORT / the per-agent UI slider),
|
||||
# which managed scope would otherwise override and lock.
|
||||
environment.etc."claude-code/managed-settings.json".source =
|
||||
"${pkgs.hyperhive-assets}/share/hyperhive/prompts/claude-settings.json";
|
||||
|
||||
# Merged frontend static tree. Base = `${frontend.dist}/agent/`,
|
||||
# then each `extraFiles` entry is laid on top at its `target`
|
||||
# path. The runCommand derivation aborts on overwrite so a
|
||||
|
|
|
|||
Loading…
Reference in a new issue