/**
 * Claude Code CLI **localSettings** management.
 *
 * The CLI reads configuration from (highest to lowest precedence)
 * `policySettings → flagSettings → localSettings → userSettings`. Writing
 * `<profile>/.claude/settings.local.json` (localSettings) is the only
 * supported way to point the CLI at a non-default `autoMemoryDirectory`
 * without either
 *   (a) polluting the user's global `~/.claude/settings.json`, or
 *   (b) committing settings to `.claude/settings.json` (which the CLI
 *       explicitly ignores for `autoMemoryDirectory` — a supply-chain
 *       hardening measure per its Zod schema).
 *
 * We keep the write surface minimal: managed fields are merged in, all
 * other fields the operator may have added manually are preserved.
 */
/**
 * Ensure `<profile>/.claude/settings.local.json` tells the CLI to store
 * auto-memory under `<profile>/claude-auto-memory/`. No-op when the file
 * already contains the correct value.
 *
 * Safe to call on every agent boot; write is skipped unless the resolved
 * value actually changes.
 *
 * @returns `true` when the managed field is in place (either already
 *   matched, or was written successfully). `false` only when a write was
 *   attempted and the `fs.writeFile`/`mkdir` call threw — callers use
 *   this to decide whether to retry on the next CLI spawn.
 */
export declare function seedClaudeAutoMemorySetting(): boolean;
//# sourceMappingURL=claude-settings.d.ts.map