/** Register the Skill-gated pi-control-chrome browser tool surface in DSH. */
import type { Context } from '@deepseek-ai/cordis';
import z from '@deepseek-ai/schemastery';
import type { SettingsNamespace } from '@deepseek-ai/dsh-settings';
import type { Config as ControlChromeConfig } from './types.js';
export type { BrowserElementTarget, BrowserResult, BrowserTarget, BrowserTargetRoute, BrowserWaitState, ResolvedConfig, ScreenshotResult } from './types.js';
export interface Config extends ControlChromeConfig {
}
export { BrowserBridgeClient, resolveConfig } from './bridge.js';
export { BROWSER_TOOL_NAMES, browserToolCatalog } from './tools.js';
export { BROWSER_SKILL_CONTENT, BROWSER_SKILL_DESCRIPTION, BROWSER_SKILL_NAME } from './skill.js';
/** Cordis plugin name used by Loader diagnostics. */
export declare const name = "tool-control-chrome";
/** The DSH registry consumed by the model-facing browser tools. */
export declare const inject: string[];
/** Settings namespace carrying the local Bridge connection configuration. */
export declare const CONTROL_CHROME_SETTINGS_NAMESPACE: SettingsNamespace;
/** Cordis configuration schema for the local browser Bridge. */
export declare const Config: z<Config>;
/**
 * Install settings-backed browser tools. With `lazyTools: true` (the default),
 * the complete browser catalog is registered in the current Agent only after
 * the `pi-control-chrome` Skill succeeds. The Bridge remains lazy until a
 * browser operation runs. Human `/chrome` commands remain available without
 * model Skill activation.
 *
 * @param ctx - DSH context providing the model tool registry and settings.
 * @param config - initial local Bridge settings.
 */
export declare function apply(ctx: Context, config: Config): void;
//# sourceMappingURL=index.d.ts.map