/**
 * A question answered alongside a running turn, without disturbing it.
 *
 * "Which model am I on?", "what does this function do?", "did the migration land?" — asked while a
 * long build is in flight. Answering it in the agent's own conversation would both interrupt the
 * build and pollute the history the agent is reasoning over, so the question runs in a separate,
 * isolated session that shares nothing but the workspace.
 *
 * The allowlist is deliberately smaller than the general read-risk class: `remember` mutates
 * KONECK's memory and `plan` mutates the session, and both are classified read-ish for ordinary
 * agent ergonomics. A side question must leave the workspace and the session exactly as it found
 * them, and an unknown or MCP tool is consequential until somebody has classified it.
 *
 * Enforced at the engine's approval boundary rather than requested in the prompt, because a prompt
 * is a preference and an approval callback is a rule.
 */
import type { AgentConfig } from './types.js';
export declare function asideAllowsTool(tool: string): boolean;
/** How many turns a side question gets. Enough to look something up, not to go on a journey. */
export declare const ASIDE_MAX_TURNS = 3;
export interface AsideAnswer {
    question: string;
    answer: string;
    ms: number;
    /** Tools it used getting there, so the answer can be trusted or doubted. */
    tools: string[];
}
/**
 * Runs one side question.
 *
 * Never throws: a side question failing must not be able to take down whatever it was asked
 * alongside, so a failure comes back as the answer text.
 */
export declare function askAside(question: string, config: AgentConfig): Promise<AsideAnswer>;
//# sourceMappingURL=aside.d.ts.map