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