/**
 * Subagent config directory management.
 *
 * Each subagent gets an isolated config directory under
 * <PI_CODING_AGENT_DIR>/tmp/subagents/<parentSessionId>/<agentId>/
 *
 * Contains dynamically-constructed settings.json, copied auth.json and
 * models.json from the parent config, and a sessions/ subdirectory.
 *
 * settings.json is NOT copied from the parent — it's built from child-specific
 * overrides + provider config extracted from the parent. This keeps extension
 * enablement granular per-subagent.
 */
export interface SubagentConfigOptions {
    model?: string;
    thinking?: string;
    maxTurns?: number;
    tools?: string[];
}
/**
 * Create the config directory for a subagent.
 *
 * Returns the config directory path.
 */
export declare function createSubagentConfig(parentId: string, agentId: string, options: SubagentConfigOptions): {
    configDir: string;
    sessionDir: string;
};
/**
 * Remove the config directory for a subagent.
 */
export declare function destroySubagentConfig(parentId: string, agentId: string): void;
/**
 * Remove the entire subagents directory for a parent session.
 */
export declare function destroyParentConfigs(parentId: string): void;
/**
 * Apply pi's child-specific settings overrides onto an existing `settings.json`
 * in `configDir`, used by the CONFIG-DIR OVERRIDE (layer) path: the synth dir
 * already carries the deep-merged base ⊕ overlay settings, and this layers the
 * per-spawn child overrides (auto-trust + model/thinking/maxTurns) on top.
 *
 * The no-override path (`createSubagentConfig`) builds settings from scratch and
 * is intentionally left byte-for-byte unchanged.
 */
export declare function applyPiChildSettingsOverride(configDir: string, options: SubagentConfigOptions): void;
//# sourceMappingURL=subagent-config.d.ts.map