/**
 * Argument checks for the agent-browser bridge.
 *
 * agent-browser reads its own options anywhere in argv, and forwards `--args`
 * to the Chromium it launches. Both are reachable from MCP tool input, so
 * caller text must never be able to add an option, and launch flags are
 * limited to a fixed list of plain switches.
 */
/** Chromium launch switches a caller may request. Exact matches only; none takes a value. */
export declare const ALLOWED_LAUNCH_ARGS: ReadonlySet<string>;
/** Returns an error when a launch-flag list contains anything outside the allowlist. */
export declare function launchArgsError(value: unknown): string | null;
/**
 * Returns an error when argv contains an option the tools did not mean to
 * pass — for example a selector or typed text of "--executable-path".
 */
export declare function commandArgvError(args: readonly string[]): string | null;
/**
 * Returns an error when a navigation target is not a web page. The browser
 * tools return page text to the caller, so a `file:` URL (or `view-source:`,
 * `chrome:`, `data:` and the like) would read local files or browser state
 * that `http_fetch` never serves. Only http(s) URLs, `about:blank`, and
 * scheme-less targets such as `example.com/path` or `localhost:3000` (which
 * agent-browser opens over http(s)) are accepted.
 */
export declare function browserUrlError(value: unknown): string | null;
//# sourceMappingURL=browser-argv.d.ts.map