claude settings: extract to prompts/claude-settings.json (formatted)

This commit is contained in:
müde 2026-05-15 18:09:05 +02:00
parent 71bf8bf47e
commit cf8f1e64b1
2 changed files with 14 additions and 9 deletions

View file

@ -0,0 +1,5 @@
{
"autoCompactEnabled": false,
"autoMemoryEnabled": false,
"effortLevel": "medium"
}

View file

@ -17,15 +17,15 @@ use crate::events::{Bus, LiveEvent};
use crate::login::{self, LoginState}; use crate::login::{self, LoginState};
use crate::mcp; use crate::mcp;
/// Inline `--settings` JSON applied to every claude invocation. We turn off /// `--settings` JSON applied to every claude invocation. Lives as a
/// claude's in-session auto-compaction and its cross-session auto-memory /// properly-formatted file in `prompts/claude-settings.json` so it's easy
/// because hyperhive owns those concerns: compaction is operator/harness- /// to read and edit; we ship it via `include_str!`. We turn off claude's
/// driven (`/compact` on overflow), notes persistence is a hyperhive /// in-session auto-compaction and its cross-session auto-memory because
/// concern (planned, not yet wired). Unknown keys are silently ignored by /// hyperhive owns those concerns (`/compact` on overflow, notes
/// claude-code; if the key names ever rename, we'll spot it because /// persistence under `/state`). Unknown keys are silently ignored by
/// auto-compact will start firing mid-turn again. /// claude-code; if a key gets renamed we'll spot it because the
const CLAUDE_SETTINGS: &str = /// corresponding behavior will start firing mid-turn again.
r#"{"autoCompactEnabled":false,"autoMemoryEnabled":false,"effortLevel":"medium"}"#; const CLAUDE_SETTINGS: &str = include_str!("../prompts/claude-settings.json");
/// Regex-ish marker claude-code emits when context overflows. Same string /// Regex-ish marker claude-code emits when context overflows. Same string
/// bitburner-agent watches for. Empirically reliable across claude-code /// bitburner-agent watches for. Empirically reliable across claude-code