/**
 * Detached launch for `monomind mcp start --daemon` (issue #267).
 *
 * `--daemon` used to be read, forwarded to MCPServerOptions.daemonize and then
 * ignored by every code path that could have acted on it: the server was
 * started in the foreground process, so `-d` blocked the terminal and the
 * server died with whatever eventually killed that blocked invocation.
 *
 * Backgrounding is done the only way that actually outlives the parent: re-exec
 * the CLI as a `detached` child with its stdio pointed at a log file instead of
 * the terminal, unref it, and let the child publish its own PID through the
 * same PID file `mcp status`/`mcp stop` read.
 */
export interface McpDaemonOptions {
    transport: 'stdio' | 'http' | 'websocket';
    host: string;
    port: number;
    /** Comma-separated tool list, or 'all'. */
    tools: string;
    /** CLI entrypoint to re-exec. Defaults to the running one. */
    cliEntry?: string;
}
export interface McpDaemonHandle {
    /** PID of the detached server process, as published in the PID file. */
    pid: number;
    /** Where the daemon's stdout/stderr were redirected. */
    logFile: string;
}
export declare function launchMcpDaemon(options: McpDaemonOptions): Promise<McpDaemonHandle>;
//# sourceMappingURL=mcp-daemon.d.ts.map