/**
 * `pxpipe warp -- <agent-command>`
 *
 * Runs the agent behind a CONNECT proxy that decrypts api.anthropic.com and
 * re-points only /v1/messages at the local pxpipe proxy. The agent never sees a
 * custom ANTHROPIC_BASE_URL, so the client-side "firstParty" checks that hide
 * /remote-control (and disable claude.ai connectors) still pass, while pxpipe
 * gets the one path it transforms.
 *
 * Compare the manual equivalent, which needs two extra tools and a CA trusted
 * process-wide:
 *
 *   mitmdump --map-remote '|^https://api\.anthropic\.com/v1/messages|http://127.0.0.1:47821/v1/messages'
 *   HTTPS_PROXY=http://127.0.0.1:8080 NODE_EXTRA_CA_CERTS=~/.mitmproxy/mitmproxy-ca-cert.pem claude
 */
export interface WarpRuntimeOptions {
    /** Port the pxpipe proxy is already serving on: where matches are sent. */
    port: number;
    /**
     * Extra PATTERN=TARGET rules, in priority order ahead of the default
     * Anthropic rule. Agents that reach their provider over a base URL rather
     * than api.anthropic.com (codex, opencode) need one rule each.
     */
    routes?: readonly string[];
}
export interface WarpRuntime {
    /** Bind the child's proxy port, then spawn the child. */
    launch: (command: string[]) => void;
}
export declare function createWarpRuntime(options: WarpRuntimeOptions): WarpRuntime;
//# sourceMappingURL=index.d.ts.map