/**
 * The Claude Agent SDK loads every filesystem settings source it can find when
 * `settingSources` is omitted, and the harness bridge omits it. A local turn
 * therefore inherits the user's `~/.claude` setup — hooks, plugins, and every
 * globally configured MCP server — and Claude Code blocks on all of it before
 * the model takes its first step. Because a turn relaunches Claude Code, that
 * is paid per message, not per session: on one machine it was 14 seconds of a
 * 22 second turn, most of it a SessionStart hook running a global npm install
 * and a skills sync.
 *
 * Pointing Claude Code at a directory Ask owns keeps a turn's cost to what the
 * turn needs. Project settings and CLAUDE.md resolve from the working
 * directory rather than here, so anything the repo commits still applies.
 *
 * The directory persists between runs: Claude Code keeps its own state and
 * session transcripts under it, and a fresh one each turn would pay first-run
 * costs again.
 *
 * Set `CLAUDE_CONFIG_DIR` to share a config with the `claude` CLI instead —
 * that reinstates the user's hooks and MCP servers, and their startup cost.
 * Nothing is written into a directory named that way: it is the user's, and
 * the settings file in it is theirs to own.
 */
export declare function askClaudeConfigDir(): string;
//# sourceMappingURL=claudeConfig.d.ts.map